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
boto_asg.present can no longer return a proper value #64015
Comments
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
We're seeing the same thing. We've also noticed that the |
AWS support said:
|
Replace all calls to `get_all_groups` with a boto3 equivalent implementation. This change is being made to address the breakage highlighted in issue saltstack#64015. Note that this port doesn't touch any of the other uses of boto which still appear to be functioning correctly. These should probably be tackled as a matter of priority though.
Replace all calls to `get_all_groups` with a boto3 equivalent implementation. This change is being made to address the breakage highlighted in issue saltstack#64015. Note that this port doesn't touch any of the other uses of boto which still appear to be functioning correctly. These should probably be tackled as a matter of priority though.
I've raised a PR which seeks to circumvent this recent behaviour change within We've tested this within our stack, and it seems to be working as expected. Note that I haven't written a new test suite (presently, I don't think there is one for |
Replace all calls to `get_all_groups` with a boto3 equivalent implementation. This change is being made to address the breakage highlighted in issue saltstack#64015. Note that this port doesn't touch any of the other uses of boto which still appear to be functioning correctly. These should probably be tackled as a matter of priority though.
Description of Issue
when using boto_asg.present, it now results in:
Retrieving vpc_zone_identifiers result in None instead of array.
Salt uses the boto.ec2.autoscale library to get an asg object, then retrieve a list of vpc_zone_identifiers. Now, all of a sudden, this has stopped working and returns "None":
Boto3 still does this successfully:
The automation we use depends on this, and this was working until the end of last week.
This may have something to do with AWS changing things on their end: https://aws.amazon.com/about-aws/whats-new/2023/03/general-availability-amazon-vpc-lattice/
Setup
Provided in the Description
Steps to Reproduce Issue
Versions Report
The text was updated successfully, but these errors were encountered: