Added NGINXaaS for Azure doc on how to change from basic to standard plan #1359
Conversation
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
arussellf5
force-pushed
the
nginxaas-migrate-to-standard-plan
branch
from
c73b4b3 to
00fd888
Compare
…plan This will help users who have outgrown their basic plan deployment and wish to recreate their deployment on the standard plan. Also moved the existing standard -> standard v2 migration doc. This was always out of place within the "Getting Started" section of our docs. We plan to use the "Change pricing plan" section to include more details about changing from basic to standard plans. There may be further docs here about migrating from standard v2 to v3.
arussellf5
force-pushed
the
nginxaas-migrate-to-standard-plan
branch
from
00fd888 to
21c11db
Compare
| 1. Decompress the template archive. | ||
| 1. Open the `template.json` file and verify that the data in the template is correct. | ||
| 1. In the `resources` section, change `sku.name` to `standardv2_Monthly`. This recreates the deployment as a standard plan deployment. | ||
| 1. Delete the original basic plan deployment. |
There was a problem hiding this comment.
Is it necessary to do this step first? Won't the new deployment have a new IP address? I would think they'd want to change the DNS mapping first (which we can't be specific about) and then when they know it's rerouting traffic, they can delete the original basic plan deployment.
There was a problem hiding this comment.
If they care that much about preserving existing traffic, then they can refer to the recreate deployment guide (which I reference in this page). My intention was to give users a quick and easy way to recreate the deployment. The order of the step is intentional. If they wish to preserve the backing resources, such as the deployment's frontend IP address, there would be conflicts if they did not delete the original deployment first. FYI this PR is now merged, so I'll need to open a new PR with any emendations we wish to make.
7 participants
This will help users who have outgrown their basic plan deployment and wish to recreate their deployment on the standard plan.
I also grouped all the migration and plan change docs together. The existing migration doc was always out of place within the "Getting Started" section of our docs. We plan to use the "Change pricing plan" section to include more details about changing from basic to standard plans. There may be further docs here about migrating from standard v2 to v3.