-
Notifications
You must be signed in to change notification settings - Fork 343
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
cloudformation_facts module in ansible 2.10 returns StackStatus in stack_description. Previously was stack_status #193
Comments
Files identified in the description:
If these files are inaccurate, please update the |
This regression is unfortunate. To preserve the compatibility with the two versions we need now to expose the two keys in the result. |
@mkyrianov This issue can be resolved by using |
Files identified in the description: If these files are inaccurate, please update the |
The issue is fixed with cloudformation_info module from amazon.aws 3.0.0. Hence closing this issue. |
…or RawMessageDelievery (SQS) (ansible-collections#640) Add support for SQS RawMessageDelievery attribute in subscriptions - issue ansible-collections#193 SUMMARY Added support to configure RawMessageDelievery option when configuring sqs endpoints. It use boto3 set_subscription_attributes() to configure changes. It currently supports only this option, but should be easily extended in the future. Attributes are expected in the form as in the boto3 docs: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.set_subscription_attributes Fixes ansible-collections#193 ISSUE TYPE Feature Pull Request COMPONENT NAME updates sns_topic.py to support new functionality example: - sns_topic: name: '{{ sns_topic_topic_name }}' display_name: My new topic name subscriptions: - endpoint: "{{ sqs_arn }}" protocol: sqs attributes: RawMessageDelivery: true Reviewed-by: Jill R <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Mark Chappell <None>
…or RawMessageDelievery (SQS) (ansible-collections#640) Add support for SQS RawMessageDelievery attribute in subscriptions - issue ansible-collections#193 SUMMARY Added support to configure RawMessageDelievery option when configuring sqs endpoints. It use boto3 set_subscription_attributes() to configure changes. It currently supports only this option, but should be easily extended in the future. Attributes are expected in the form as in the boto3 docs: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.set_subscription_attributes Fixes ansible-collections#193 ISSUE TYPE Feature Pull Request COMPONENT NAME updates sns_topic.py to support new functionality example: - sns_topic: name: '{{ sns_topic_topic_name }}' display_name: My new topic name subscriptions: - endpoint: "{{ sqs_arn }}" protocol: sqs attributes: RawMessageDelivery: true Reviewed-by: Jill R <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Mark Chappell <None>
…or RawMessageDelievery (SQS) (ansible-collections#640) Add support for SQS RawMessageDelievery attribute in subscriptions - issue ansible-collections#193 SUMMARY Added support to configure RawMessageDelievery option when configuring sqs endpoints. It use boto3 set_subscription_attributes() to configure changes. It currently supports only this option, but should be easily extended in the future. Attributes are expected in the form as in the boto3 docs: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sns.html#SNS.Client.set_subscription_attributes Fixes ansible-collections#193 ISSUE TYPE Feature Pull Request COMPONENT NAME updates sns_topic.py to support new functionality example: - sns_topic: name: '{{ sns_topic_topic_name }}' display_name: My new topic name subscriptions: - endpoint: "{{ sqs_arn }}" protocol: sqs attributes: RawMessageDelivery: true Reviewed-by: Jill R <None> Reviewed-by: None <None> Reviewed-by: Alina Buzachis <None> Reviewed-by: Mark Chappell <None>
SUMMARY
cloudformation_facts module in ansible 2.10 returns StackStatus in stack_description. Previously was stack_status
In ansible 2.9:
cfn_stack.ansible_facts.cloudformation[cfn_stack_name].stack_description.stack_status is defined
In ansible 2.10:
cfn_stack.ansible_facts.cloudformation[cfn_stack_name].stack_description.stack_status is not defined
Instead ansible 2.10 has this dict key defined:
cfn_stack.ansible_facts.cloudformation[cfn_stack_name].stack_description.StackStatus
ISSUE TYPE
COMPONENT NAME
cloudformation_facts
ANSIBLE VERSION
CONFIGURATION
OS / ENVIRONMENT
Ubuntu 18.04
STEPS TO REPRODUCE
EXPECTED RESULTS
cfn_stack.ansible_facts.cloudformation[cfn_stack_name].stack_description.stack_status variable is defined and return stack actual status
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: