-
Notifications
You must be signed in to change notification settings - Fork 131
feat(container): vpc integration #3158
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
feat(container): vpc integration #3158
Conversation
c467ee7
to
9a089d8
Compare
9a089d8
to
838226e
Compare
- DENY | ||
X-Request-Id: | ||
- d3b7c8ba-8e96-476b-970e-27ba92704224 | ||
status: 400 Bad Request |
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.
I'm not sure we should merge that. This request does not look ok
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.
I wanted to test the fact that legacy namespaces are not compatible with VPC and that activating the feature in the namespace should recreate it with ForceNew, therefore changing its ID.
I can remove the 2nd step if we prefer not to test whether the error occurs, but only the resource recreation.
No description provided.