https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
l
Shouldn't need that. In the short term, you could wrap your Parameter construct in logic like this: • if you know if doesn't yet exist, then construct it; else • if you know it does exist, then don't construct it (so Pulumi deletes it); and • if you want to update it, run 
up
twice. If in the short term you can move your Parameter code to a new tiny project that just does this, you'll have the least churn.
c
I am running Up inside of a CI/CD github action
So in your third choice up there do you mean just running the pipeline (pulumi up) twice without changing the logic I have?
I could do the tiny project too, our code might be a little entangled to make that super straightforward
What I ended up doing was just commenting out my entire stack and running pulumi up (delete everything) and then just running the build pipeline on github to recreate everything, and that seems to have worked
Little hacky but will work for now, although I'll have to employ one of those workarounds since we are aiming to deploy this stack this week
l
My suggestion wasn't 3 separate ideas, it's the logic that you're currently implementing manually - comment out the code and run 
up
🙂 I just suggested doing it via an 
if
clause.
c
Thanks, that makes sense. It's a database connection string, so it's not like it will change frequently. I appreciate the quick follow up! Any idea what the timeline for a fix would be? I'll keep an eye on the github issue.
l
Currently scheduled for the 0.75 milestone, 24 July: https://github.com/pulumi/pulumi-aws/milestone/78
4 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by