Skip to content

Update known-issues.md#10

Open
Khuzaima05 wants to merge 3 commits into
ibm-cloud-docs:masterfrom
Khuzaima05:update_vpc_known_issue
Open

Update known-issues.md#10
Khuzaima05 wants to merge 3 commits into
ibm-cloud-docs:masterfrom
Khuzaima05:update_vpc_known_issue

Conversation

@Khuzaima05
Copy link
Copy Markdown

Thanks for taking the time to contribute to the IBM Cloud docs! After you open your pull request, a maintainer should review it soon.

We don't merge changes directly in this repository because content is not published from here. However, we'll incorporate any changes in our upstream repository so that they're reflected in the docs.

Description

Update known-issues.md

Any other comments?


For reviewers (This section is only for IBMers)

You can't merge pull requests here.

  • If you can incorporate these changes, copy them to your GitHub Enterprise repo. Leave a comment and close the pull request.
  • If you can't accept the changes, leave information about why, and close the pull request.

If you don't have permission to close the request, ask for help in the IBM Cloud #docs Slack channel.

Comment thread known-issues.md Outdated

Avoid changing the `prefix` value after the infrastructure is deployed. Treat the prefix as an immutable identifier for an existing environment.

If a different prefix is required, deploy a new environment instead of modifying the existing one.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deploy a new environment?? Not sure we should say this? If they really wanted the prefix to be changed and didn’t mind doing it in a disruptive way, wouldn’t they just proceed with the destroy / re-create? Perhaps we should say to plan accordingly for a disruptive update?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ocofaigh , I have updated the wording as :

Avoid changing the `prefix` value after the infrastructure is deployed. Treat the `prefix` as an immutable identifier for an existing environment when possible.

If you change the `prefix` after deployment, Terraform can destroy and recreate address prefixes, subnets, and dependent resources. Proceed only if you are prepared for this disruptive update.

@ocofaigh
Copy link
Copy Markdown
Contributor

@Khuzaima05 please create this PR in the internal repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants