-
Notifications
You must be signed in to change notification settings - Fork 53
W-18195573-CHtoCH2-App-Migration #787
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.
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
base: latest
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment
The *Upgrade Application to CloudHub 2.0* page opens. | ||
+ | ||
. The *Application Name* field shows the inherited CloudHub application name by default. If you want to use a different name for your CloudHub 2.0 application, change it by editing the field. | ||
. The *Upgrading From* field shows the name of the CloudHub application the new application is being upgraded from. You can’t edit this field. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a step. There's no user action here.
. The *Deployment Target* field shows the preselected private space for the application deployment based on the upgraded CloudHub VPC. You can’t edit this field. | ||
. For the *Application File*, you can either: | ||
.. Upload your Application File: Download the application asset from the link provided under *Application File*, make all the necessary changes, and reupload it to deploy your new application to the CloudHub 2.0 private space, or | ||
.. Import File from Exchange: Import the CloudHub application you want to upgrade. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "Import File from Exchange" a UI label? If not, this should be "Import file from Exchange:"
Co-authored-by: Beth Joson <[email protected]>
…g-LDS W-18707073-slb traffic switching lds
…ching-LDS W-18689118-dlb slb traffic switching lds
Co-authored-by: Cristian Pose <[email protected]>
…H2-HTTPS-HTTP-LDS
W-18662606 ch2 https http lds
Writer's Quality Checklist
Before merging your PR, did you: