-
Notifications
You must be signed in to change notification settings - Fork 336
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
ec2_metric_alarm "Datapoints To Alarm" flag missing #1085
Comments
Files identified in the description: If these files are inaccurate, please update the |
Hi @LeoSpyke96, would you like to raise a PR for this feature? Thanks. |
* Order imports in the standard order * Use botocore.exceptions.ClientError instead of ClientError for consistency * Use full import path for module_utils (it's used more consistently than relative paths) * Import HAS_BOTO3 from module_utils.ec2 for consistency with our other BOTO3 handling * changelog Co-authored-by: Jill R <[email protected]>
Files identified in the description:
If these files are inaccurate, please update the |
…nsible-collections#1085) s3_lifecycle: reassure that configuration is complete before returning. Get bucket lifecycle configuration a few times to make sure it is stable. It was observed that shortly (~30s) after setting the rules a method get-bucket-lifecycle-configuration returns alternatively new and old rules in a random manner. Similar issue reported for boto3 library: boto/boto3#2491 SUMMARY Fixes ansible-collections#1084 ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_lifecycle Reviewed-by: Mark Chappell <None> Reviewed-by: Lukasz Rubaszewski <None> Reviewed-by: Mark Woolley <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: Joseph Torcasso <None>
…nsible-collections#1085) s3_lifecycle: reassure that configuration is complete before returning. Get bucket lifecycle configuration a few times to make sure it is stable. It was observed that shortly (~30s) after setting the rules a method get-bucket-lifecycle-configuration returns alternatively new and old rules in a random manner. Similar issue reported for boto3 library: boto/boto3#2491 SUMMARY Fixes ansible-collections#1084 ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_lifecycle Reviewed-by: Mark Chappell <None> Reviewed-by: Lukasz Rubaszewski <None> Reviewed-by: Mark Woolley <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: Joseph Torcasso <None>
…nsible-collections#1085) s3_lifecycle: reassure that configuration is complete before returning. Get bucket lifecycle configuration a few times to make sure it is stable. It was observed that shortly (~30s) after setting the rules a method get-bucket-lifecycle-configuration returns alternatively new and old rules in a random manner. Similar issue reported for boto3 library: boto/boto3#2491 SUMMARY Fixes ansible-collections#1084 ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_lifecycle Reviewed-by: Mark Chappell <None> Reviewed-by: Lukasz Rubaszewski <None> Reviewed-by: Mark Woolley <[email protected]> Reviewed-by: Alina Buzachis <None> Reviewed-by: Joseph Torcasso <None>
Any updates on this? |
SUMMARY
Hi everybody, I'm building an automation procedure which adds alarms to my newly created EC2 instances.
There is one important alarm I need, the StatusCheckFailed_System, whose behaviour and triggering conditions I would like to be customizable for my needings.
So, the problem is that as the version 2.9.11 of Ansible that I'm currently using, i cannot find the flag that allows me to set the datapoints to alarm (the aws cli equivalent flag is, obviously,
--datapoints-to-alarm
).What am I doing wrong? Can anyone kindly help me?
Cheers!
ISSUE TYPE
COMPONENT NAME
ec2_metric_alarm
ANSIBLE VERSION
2.9.11
CONFIGURATION
OS / ENVIRONMENT
Ansible AWX 14.1.0 installed on Docker
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: