Hey team :wave: hitting what looks like a bug in P...
# pulumi-deployments
c
Hey team šŸ‘‹ hitting what looks like a bug in Pulumi Deployments webhook routing. Problem When
DeploymentSettings
are written via the
pulumiservice
provider or direct API calls, GitHub webhook routing is not registered — push-to-deploy and PR preview silently stop working even though the settings look correct in the API response. Manually clicking Save in the UI fixes it immediately. Root cause (confirmed via frontend source) The server only registers webhook routing when
source: console
(browser session). API tokens produce
source: api
, provider produces
source: provider
— neither triggers the routing side effect, despite calling the same
PatchDeploymentSettings
endpoint. • UI Save →
source: console
→ webhook routing āœ… • API token →
source: api
→ webhook routing āŒ •
pulumiservice
provider →
source: provider
→ webhook routing āŒ Impact Any team managing
DeploymentSettings
as IaC loses webhook routing on every
pulumi up
that touches VCS settings. The only workaround is a manual UI Save per stack. Expected
PatchDeploymentSettings
should register webhook routing regardless of
source
. provider:
pulumi-pulumiservice
v1.3.0
Update: I've documented the full details in a GitHub issue here: https://github.com/pulumi/pulumi-cloud-requests/issues/592 . It includes the exact steps to reproduce and the root cause I found regarding the
source
field and the
PatchDeploymentSettings
behavior.
f
Thanks for creating an issue! We are looking into it
This issue should be fixed now. Please let us know if you still run into anything