-
Notifications
You must be signed in to change notification settings - Fork 155
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
Refresh with RDS MariaDB after restoring from DB snapshot deletes instance #2910
Comments
Hi @ffMathy I believe the property |
Identifier was not set, so identifierPrefix was generated automatically by the Pulumi resource name. Switching to aws-native was a workaround. |
@ffMathy I've not been able to reproduce this issue, it's possible that the underlying root cause has been fixed since you originally reported this issue. Here is what I have used to try and reproduce: import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
const vpc = new awsx.ec2.Vpc("Vpc", {
natGateways: { strategy: "Single" },
subnetStrategy: "Auto",
});
const subnetGroup = new aws.rds.SubnetGroup("db-subnet-group", {
subnetIds: vpc.privateSubnetIds,
})
const db = new aws.rds.Instance("db", {
allocatedStorage: 20,
engine: "mariadb",
engineVersion: "10.11",
autoMinorVersionUpgrade: true,
instanceClass: aws.rds.InstanceType.T3_Micro,
manageMasterUserPassword: true,
username: "admin",
dbSubnetGroupName: subnetGroup.name,
}) And I followed your steps:
When I ran the refresh it pulled the new database and did not show a deletion. |
@ffMathy Have you continued to see this behavior? I'm wondering if we should close this issue since it appears to work in the latest version or if there's something else we're missing in our attempts to reproduce it. |
I'm going to close this out with no-repro for now, but happy to re-open if this you're still encountering this problem. |
What happened?
When you perform a
pulumi refresh
on a database created in RDS (a MariaDB instance) after you've restored it from a snapshot, it triggers a deletion.Example
Any Pulumi code that produces a MariaDB database can repro this.
But the following steps are important:
pulumi refresh
. Now it'll detect the database as deleted, although it should pull from the new database instead.Output of
pulumi about
CLI
Version 3.89.0
Go Version go1.21.1
Go Compiler gc
Plugins
NAME VERSION
nodejs unknown
Host
OS debian
Version 12.2
Arch aarch64
This project is written in nodejs: executable='/usr/local/bin/node' version='v18.18.2'
Pulumi locates its logs in /tmp by default
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: