Skip to content
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

aws_cloudwatch_event_rule "Provider produced inconsistent result after apply" #18151

Closed
richardgavel opened this issue Mar 18, 2021 · 3 comments
Labels
bug Addresses a defect in current functionality. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.

Comments

@richardgavel
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

TF: 0.12.30
AWS: 2.70.0

Affected Resource(s)

aws_cloudwatch_event_rule

Expected Behavior

Resource created

Actual Behavior

Very intermittent

Error: Provider produced inconsistent result after apply

When applying changes to
aws_cloudwatch_event_rule.datalake_runaggregationsjob_rule, provider
"registry.terraform.io/-/aws" produced an unexpected new value for was
present, but now absent

Important Factoids

This seems like an eventual consistency issue like has been seen with other resources.

  • #0000
@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. bug Addresses a defect in current functionality. labels Mar 18, 2021
@bill-rich
Copy link
Contributor

Hi @richardgavel!

In order to help reproduce this issue, can you please provide an example configuration?

@bill-rich bill-rich added service/cloudwatch Issues and PRs that pertain to the cloudwatch service. waiting-response Maintainers are waiting on response from community or contributor. labels Mar 19, 2021
@breathingdust
Copy link
Member

Closing due to lack of response.

@breathingdust breathingdust removed needs-triage Waiting for first response or review from a maintainer. waiting-response Maintainers are waiting on response from community or contributor. labels Sep 8, 2021
@github-actions
Copy link

github-actions bot commented Jun 9, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/cloudwatch Issues and PRs that pertain to the cloudwatch service.
Projects
None yet
Development

No branches or pull requests

3 participants