Skip to content
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

How to safely upgrade database cluster version without losing data? #121

Open
snipebin opened this issue Aug 10, 2020 · 1 comment
Open
Labels
kind/question Questions about existing features

Comments

@snipebin
Copy link

Hi, thanks in advance for the support.

Digital ocean explains how we one upgrade cluster versions: https://www.digitalocean.com/docs/databases/postgresql/how-to/upgrade-version/

what's the equivalent for Pulumi?

Here's my definition

new digitalocean.DatabaseCluster(`${stackName}-shared`, {
    engine: "pg",
    nodeCount: config.requireNumber('postgres-cluster-shared-node-count'),
    region: doRegion,
    size: digitalocean.DatabaseSlugs.DB_1VPCU2GB,
    version: "11",
    privateNetworkUuid: vpc.id
  }, { dependsOn: [vpc], protect: true  })

I want to upgrade to version 12.

Do I simply change to version: "12", run pulumi up?

@snipebin snipebin changed the title How to safely upgrade cluster version without losing data? How to safely upgrade database cluster version without losing data? Aug 10, 2020
@lukehoban
Copy link
Member

Do I simply change to version: "12", run pulumi up?

I don't personally know the DigitalOcean API well, but have you tried previewing doing this? The preview should tell you whether it can update in place, or whether the change would require a replacement of the resource (which will then be prevented due to your protect: true.

@infin8x infin8x added kind/question Questions about existing features and removed question labels Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions about existing features
Projects
None yet
Development

No branches or pull requests

3 participants