You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an aws.redshift.ResourcePolicy, AWS will accept a policy that doesn't include "Resource" and will set it for us but if it is not in our code, it will trigger an update every deploy.
I got arround it by setting it explicitly in my policy definition.
Sample program
This will trigger an update on every deploy, but is setting everything as expected :
CLI
Version 3.129.0
Go Version go1.22.6
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.49.1
resource awsx 2.14.0
resource docker 4.5.5
language python unknown
Additional context
No response
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:
Thanks, yea, reason I was able to figure it out was that I went into my cloudtrail logs and looked at what the API was sending back as a response. There was probably an other way to find out, but I don't know it.
Describe what happened
When creating an aws.redshift.ResourcePolicy, AWS will accept a policy that doesn't include "Resource" and will set it for us but if it is not in our code, it will trigger an update every deploy.
I got arround it by setting it explicitly in my policy definition.
Sample program
This will trigger an update on every deploy, but is setting everything as expected :
This is what is needed (adding "Resource" explicitly in the policy) to not trigger an update on every deploy :
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
CLI
Version 3.129.0
Go Version go1.22.6
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.49.1
resource awsx 2.14.0
resource docker 4.5.5
language python unknown
Additional context
No response
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: