Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
Powered by
#aws
Title
l
little-cartoon-10569
01/14/2021, 11:26 PM
Not sure that it's a bug, but definitely a gotcha: updating an RDS optiongroup and the instance it's associated with in the same
pulumi up
fails.
I've updated my instance's security groups, which are the same for both the instance and the SSRS option group.
Pulumi updated the optiongroup first, which puts the instance in state
Modifying
.
Then it tries to update the security groups on the instance, but RDS only allows that when the instance is in state
Available
.
Once it finishes modifying the SSRS security groups, I'll re-up and I expect it to work fine.
Yep. It has finished, I re-upped, it worked fine.
Interestingly, updating the instance's SGs never put the instance in
Modifying
, so it would have worked fine the other way around...
c
chilly-hairdresser-56259
01/15/2021, 3:50 AM
Was it replacing a SG? Modifying should have no impact to RDS (IE adding a new allow statement etc)
Post