when managing deployment settings with the

pulumiservice

provider, i find that the changes aren't really "finalized" by the provider -- i have to go in to the console, make no changes, and click "Save deployment configuration." all of the settings are fully populated by the provider, so it certainly appears to have worked, but it doesn't work until I click that save button. has anyone else run into this? Is there a step i'm missing?

this sounds like a bug, could you open an issue?

sure thing

This is definitely unexpected. When you say it hasn’t worked what exactly do you mean?

at a minimum, it doesn't properly interact with github -- it doesn't trigger on new PRs, for instance. i'm working to recreate the situation (without interrupting our existing workflow) so i can see if manually triggered deployments function as expected

that's a helpful lead, thank you. let me take a look

okay, a few more details: i've just enabled deployments for a stack for the first time. the deployment settings page in the console is entirely populated, but all of the stuff in the "Actions" is grayed out if i try to use it as a non-admin user:

Hey Chris, sorry you're having trouble here. Can you share with us the code for deployment settings via the pulumi provider? One thing to note is that you have to use the full branch name. The deployment settings UI hides this, but it actually expands the full value:

sourceContext: {
            git: {
                branch: "refs/heads/main",
            },
        },

If you only supply

main

then pull request events will not work.

i bet that's it

Yes apologies. We have a bug open internally to fix that and accept short branch names in addition to the fully qualified ones.

confirmed, that fixed it