+1. That's my expectation, also.
On 1 June 2017 at 13:03, Eric Wittmann <eric.wittmann(a)redhat.com> wrote:
I do not believe that there were any database changes between 1.2.8
and
1.30. So I *think* you should be OK if you just upgrade the application
and skip the export/import process (just point the new version to your
existing database). However, I would advise you to clone your database and
give it a try first (on a test system), before doing anything in production.
-Eric
On Wed, May 31, 2017 at 4:45 PM, Celso Agra <celso.agra(a)gmail.com> wrote:
> Hi all,
>
> Sorry about that, but I'm concern to upgrade my apiman to a newest.
> I read about upgrating the application:
http://www.apiman.io/latest/in
> stallation-guide.html#_upgrading_to_a_new_apiman_version
> But I'd like to know if I upgrade from 1.2.8 to 1.3.0 is must needed to
> export and reimport all data from different versions.
>
> Could I just change server and application without change anything in my
> database? just put the new wildfly running the apiman instance. Would be
> possible to do that?
>
> PS.: My APIMan is running with a remote database and remote Keycloak.
>
> Best Regards,
>
> --
> ---
> *Celso Agra*
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user