-
Notifications
You must be signed in to change notification settings - Fork 159
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 RDS cluster not able to update enableHttpEndpoint
property
#2926
Comments
I believe RDS delays some parameter changes until the next maintenance window - this could be related. |
That might be it. I tried changing |
@dennispan To clarify - if you check your resource in AWS console, do you see the value as Also, could you please provide a full code snippet that I could run to reproduce the issue? Thank you! |
Yes the http endpoint are actually enabled. The code snippet is basically what I shared in the issue description. Most other properties are set based on stack configuration. Happy to share more details via email if needed |
I think I can repro it with
then the state contains
Ah, that's good to hear. What is the practical consequence of the issue for you then? |
This does not repro for me anymore and must have been fixed.
|
What happened?
pulumi_aws.rds.Cluster
enable_http_endpoint
property toTrue
pulumi up
pulumi up
againExpected:
No change is anticiated
Actual:
pulumi
preview says there is one update needed, which is to updateenable_http_endpoint
. If we check the resource status,enableHttpEndpoint
isfalse
but it should betrue
at this pointExample
Output of
pulumi about
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: