Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by
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)
#aws
Join Slack