-
Notifications
You must be signed in to change notification settings - Fork 158
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
Error pushing stack with AppFlow resources #2211
Comments
In case anyone struggles with this issue in the future, I was able to workaround it using ReplaceOnChanges |
Hey @julioxavierr - thank you for opening this issue! I think your intuition is correct, and that this is related to the terraform-provider-aws issue you've linked. Given that, I'm going to transfer this to our |
This error appears to be related to this upstream issue: hashicorp/terraform-provider-aws#25095 |
Hi! I would like to contribute to this issue. Kindly guide |
We're waiting on an upstream fix for this, and it looks like someone may have already started work on that fix. |
I am facing this issue as well Terraform v1.5.7 provider registry.terraform.io/hashicorp/aws v5.26.0 |
The upstream issue hashicorp/terraform-provider-aws#25095 has been resolved as fixed, so I'll close this issue too. Please report a new issue if the problem occurs again. |
What happened?
When updating a stack, even though there are no updates to the flow arguments, it tries to update it and errors.
Steps to reproduce
Sample code
Expected Behavior
Updating a stack (with
pulumi up
) that has a flow configured should not try to update the flow if there are no updates.Actual Behavior
When updating a stack, even though there are no updates to the flow arguments, it tries to update it and fails with the following error:
In the "details", it's possible to notice that it completely removes the "tasks" field from the CloudFormation resources. So my first guess is that there's a building error.
Output of
pulumi about
Additional context
In the "details", it's possible to notice that it completely removes the "tasks" field from the CloudFormation resources. So my first guess is that there's a building error.
It also seems similar to hashicorp/terraform-provider-aws#25095.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: