Skip to content

W-19460112-migrated apps mmp lds #818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Sep 9, 2025
Merged

W-19460112-migrated apps mmp lds #818

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
860bb92
W-19460112-migrated-apps-MMP
luanamulesoft Sep 5, 2025
b4b164d
Update app-migration.adoc
luanamulesoft Sep 9, 2025
91d8030
Merge branch 'W-18195573-CHtoCH2-App-Migration-LDS' into W-19460112-m…
luanamulesoft Sep 9, 2025
bd3ceda
Update app-migration.adoc
luanamulesoft Sep 9, 2025
b986535
Update app-migration.adoc
luanamulesoft Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions cloudhub/modules/ROOT/pages/app-migration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,14 +57,18 @@ The *Host* dropdown list shows only the domains added under the certificates of

=== Considerations and Limitations

The upgrade process doesn’t automatically map some configuration settings to the new CloudHub 2.0 application. Go to your new CloudHub 2.0 application settings to finish the configuration.
The upgrade process doesn’t automatically map some configuration settings to the new CloudHub 2.0 application.

==== Application Properties

The upgrade process doesn't carry over application properties to CloudHub 2.0. Reconfigure these properties manually for a successful upgrade:
* When properties are initially copied during CloudHub 2.0 application configuration, they don't persist unless you edit at least one property or add a new property. Editing a single property, or adding a new one, causes the edited or new property and all other copied properties to persist.

* The upgrade process initially copies your CloudHub app's properties during the CloudHub 2.0 application configuration. These properties don't persist unless you edit at least one property or add a new property. Editing a single property, or adding a new one, causes the edited or new property and all other copied properties to persist.
* The upgrade process copies the protected properties added during CloudHub 1.0 with `****` as their displayed value. Change this displayed value manually to the correct protected value within your CloudHub 2.0 application settings.

==== Managing Migrated Apps via MMP

After migrating applications to CloudHub 2.0, to manage a migrated app using the Mule Maven Plug-in (MMP), copy the public URL configured on Runtime Manager during the migration. If the endpoints specified in the `publicUrl` field of your `pom.xml` file don't match the ones configured in the UI, the Ingress configuration is lost.


== Next Steps After Application Upgrade
Expand Down