This message was deleted.
# pulumi-deploymentss
sparse-intern-71089
10/05/2023, 3:44 PMThis message was deleted.
b
billowy-army-68599
10/05/2023, 3:48 PM
this sounds like a bug, could you open an issue?
d
damp-magazine-59707
10/05/2023, 3:49 PMsure thing
r
red-match-15116
10/05/2023, 3:58 PMThis is definitely unexpected. When you say it hasn’t worked what exactly do you mean?
d
damp-magazine-59707
10/05/2023, 4:08 PMat 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
damp-magazine-59707
10/05/2023, 4:08 PMbut it's possible that the only setting that isn't really getting applied is "Run previews for pull requests"
👀 1
r
red-match-15116
10/05/2023, 4:09 PMthat's a helpful lead, thank you. let me take a look
red-match-15116
10/05/2023, 4:15 PMhm, nothing obviously stands out from a quick look. would appreciate a repro if you can get one!
d
damp-magazine-59707
10/05/2023, 6:06 PMokay, 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:
damp-magazine-59707
10/05/2023, 6:06 PMhowever, i can manually trigger a deployment just fine as an admin user, and after doing so, suddenly the non-admin user can access all of that functionality too
damp-magazine-59707
10/05/2023, 6:06 PMi.e., those things are no longer grayed out as non-admin once an admin runs a preview
damp-magazine-59707
10/05/2023, 6:07 PMi'm guessing the manually-triggered preview has the same effect as the no-op save
damp-magazine-59707
10/05/2023, 6:15 PMthat may have been a fluke, i couldn't reproduce that on two other stacks that i just enabled 😕
l
lemon-agent-27707
10/05/2023, 7:05 PMHey 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:
Copy code
sourceContext: {
git: {
branch: "refs/heads/main",
},
},maind
damp-magazine-59707
10/05/2023, 7:05 PMi bet that's it
damp-magazine-59707
10/05/2023, 7:06 PMwhen i click "save" it appears that no changes were made, but a secret change was made behind the scenes
l
lemon-agent-27707
10/05/2023, 7:21 PMYes apologies. We have a bug open internally to fix that and accept short branch names in addition to the fully qualified ones.
lemon-agent-27707
10/05/2023, 7:22 PMCan you confirm that specifying the full branch fixes the issue you were seeing?
d
damp-magazine-59707
10/06/2023, 2:51 PMconfirmed, that fixed it