-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add location specifiers to network resources #2023
Add location specifiers to network resources #2023
Conversation
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
…therwise use the default location (which may not be correct).
e69f46a
to
affbbea
Compare
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.
LGTM
It seems to be good practice to always specify the location.
Do we not have a location specified in the stack configuration? dev.pulumi.yaml
equivalent.
Or, does that not guarantee resources will use that location?
It might be there is future work here to make this more robust.
The "location": "uksouth",
"subscriptionId": <redacted>,
"tenantId": <redacted>,
"version": "2.50.1" These are set during I encountered the problem because I tried to deploy into "ukwest" - found that some resources aren't available there, so ran a teardown and redeploy into "uksouth". This left "ukwest" defined in the state file, which was used whenever "location" wasn't explicitly set on a resource. |
✅ Checklist
Enable foobar integration
rather than515 foobar
).develop
.🚦 Depends on
n/a
Add location specifiers to virtual networks and NSGs as these will otherwise use the default location (which may not be correct).
🌂 Related issues
Closes #2022
🔬 Tests
Tested on previously-broken SRE deployment