-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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/boto describe default vpc #58628
Conversation
I am curious if it wouldn't be better to simply lookup the default vpc if no vpc_id and no vpc_name are specified. |
8bf7549
to
07768cf
Compare
07768cf
to
832096d
Compare
832096d
to
d306d60
Compare
Reworked the PR to modify fewer functions by allowing the calling of |
d306d60
to
fca025d
Compare
Thanks for the PR! Once there's a test for the changes we can merge. A unit test should do the trick. |
fca025d
to
8c4c45e
Compare
I have updated the test case, but while I was doing so I discovered that none of the VPC tests are running. From the code:
All of the following tests are skipped when running
Roughly 1/3rd of the boto tests. |
I suppose it is worth pointing out that a number of individual tests in
|
8c4c45e
to
6d61375
Compare
According to the linked issue (getmoto/moto#1706), this problem should have been resolved in |
6d61375
to
5e7684f
Compare
I have created a new PR to re-enable a large swath of boto unit tests: #58660 |
All AWS accounts are created with a default VPC in the regions to which all instances will be launched onto if no alternate VPC is specified.. These VPC's have no name and as such can not be looked up via the `vpc_name`. This commit makes it such that you do not have to already know the VPC ID in order to apply basic security changes/tweaks/enhancements to the AWS Default VPC.
5e7684f
to
1f845e2
Compare
What does this PR do?
Allow looking up the default AWS VPC which is automatically created at account creation time.
Previous Behavior
Previously the
boto_vpc
module only allowed looking up a VPC via thevpc_id
or thevpc_name
. The default VPC does not have avpc_name
and as such it is not possible to look it up.New Behavior
If neither the
vpc_id
nor thevpc_name
are supplied toboto_vpc.describe()
then it will describe the default VPC.The following functions were modified to make this possible:
_find_vpcs()
describe()
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.