-
Notifications
You must be signed in to change notification settings - Fork 346
fix: use static list of project regions #4692
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
fix: use static list of project regions #4692
Conversation
Pull Request Test Coverage Report for Build 20786460683Details
💛 - Coveralls |
sweatybridge
left a comment
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.
Looks good! just did some minor refactoring
|
I did more testing and found that it doesn't actually work. Reason is we need to parse the let me see if there's another alternative currently settling on a static list of regions to unblock |
|
🤦♂️ Yeah, I completely overlooked |
What kind of change does this PR introduce?
Bug fix #4689
What is the new behavior?
LoadProfile is called before awsRegions are loaded.
Additional context
regionvar is initialized at package scope in projects.go. As regions are scoped to profile now (#4596), at this point the current profile isn't loaded yet so theregion.Allowedis set to empty slice.LoadProfileis called insiderootCmd.PersistentPreRunEwhich runs after flag parsing and flag validation.Marking this as a draft for now to get early feedback from maintainers. Happy to adjust the approach if there's a preferred pattern here.