This message was deleted.
# generals
sparse-intern-71089
07/05/2022, 9:07 PMThis message was deleted.
l
little-cartoon-10569
07/05/2022, 9:25 PMShouldn'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
upc
cool-flower-46371
07/05/2022, 9:43 PMI am running Up inside of a CI/CD github action
cool-flower-46371
07/05/2022, 9:44 PMSo in your third choice up there do you mean just running the pipeline (pulumi up) twice without changing the logic I have?
cool-flower-46371
07/05/2022, 9:44 PMI could do the tiny project too, our code might be a little entangled to make that super straightforward
cool-flower-46371
07/05/2022, 9:53 PMWhat 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
cool-flower-46371
07/05/2022, 9:54 PMLittle 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
little-cartoon-10569
07/06/2022, 12:16 AMMy suggestion wasn't 3 separate ideas, it's the logic that you're currently implementing manually - comment out the code and run
upifc
cool-flower-46371
07/06/2022, 10:31 AMThanks, 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
little-cartoon-10569
07/06/2022, 10:14 PMCurrently scheduled for the 0.75 milestone, 24 July: https://github.com/pulumi/pulumi-aws/milestone/78
5 Views