for production releases we would like to use tags to we can guarantee with deployments and any webhook deployments don't have unintended consequences but as of now it seems like the pulumi side of things appends

refs/heads

to everything that isn't doesnt have that prefixed, so when i use

refs/tags/v1.0.0

pulumi tries to fetch

refs/heads/refs/tags/v1.0.0

. Is there any way around this or any timeline on a fix?

Hey! Looks like you found https://github.com/pulumi/pulumi-cloud-requests/issues/328 which is the issue tracking this.

hi! yes i saw that but its been open since jan 2023 so i am assuming this is not on the radar? this severely deters the use of pulumi deployments imo. I am assuming its a very easy fix and additional check for whatever helper function that is doing the appending.

Definitely appreciate the feedback! The issue has indeed been open for a while but we haven't seen a lot of activity around it and so it hasn't been a top priority. Which isn't to say that it shouldn't be. The work is fairly straightforward, just needs to be prioritized. I'll bring it up in our next iteration's planning (next week)

i would greatly appreciate it, we built out a really good solution that we were planning to write a blog post about but if this doesnt work we would hae to get off pulumi deployments and just do it ourselves. I am sure others at some point would be on the same boat. Thank you for responding!

yup, totally hear you! I'm curious how you're creating deployment settings (api / web ui/ pulumi provider) - if you could add those details to the issue in a comment it'll help me prioritize the right fix to unblock you

we have a pulumi stack with the deployment settings, additionally to trigger various microstack deployments we use nx + some custom code to generate the affected microstacks within a project and then make a call to the pulumi api to trigger the respecting deployment. We pass in the $BRANCH variable which for our development env works fine as we use a main branch, but for production we need to use a tag and additionally our ci job updates the deployment settings for each microstack being deployed prior to each prod deployment to use the correct tag

@rhythmic-pharmacist-98468 thanks for the info! I'm wondering if as a workaround currently you could use the commit hash instead of the tag. https://www.pulumi.com/registry/packages/pulumiservice/api-docs/deploymentsettings/#commit_yaml

ill take a look, thanks for that info! additionally out of curiosity is there currently a way to poll the deployments to see if it succeeded or not ?

> is there currently a way to poll the deployments to see if it succeeded or not yeah, there's a couple ways you could do this. you can either subscribe to webhooks (which is an alternative to polling). Or, you can call the getDeployment endpoint which includes the deployment's status.

thank you for the help @red-match-15116! really appreciate it

no problem, happy to help

hi! @red-match-15116 can you confirm that commit works? we recently updated to use commit but now i cam seeing

Bad Request: at least commit or branch are required

Ah, I see what the issue is. There's a bug in the pulumiservice provider, I'll push up a PR to fix it.

thank you!

PR to fix: https://github.com/pulumi/pulumi-pulumiservice/pull/470

thank you for the quick turnaround! will update as soon as its merged

The fix is out in v0.27.3

so i updated the dependency but now i am seeing this

Huh! That is really surprising. I haven't been able to repro this. You're sure you're passing in the sha in the

commit

property and not the

branch

property?

ah my apologies, i see where the issue is...we have a script to make a api call and while i updated the deployment settings i also needed to update the api call

FWIW you shouldn't need to pass the deployment settings when you make the api call to start a deployment unless you are overriding certain settings. You should just be able to pass the operation you are executing.

oh nice ill make that update then, thanks for the tip!