I'm finally getting around to trying the Bitbucket Integration and PR comments, etc. The integration is now set up fully, my previews ran fine, but no change to my PRs, so I'm investigating. The troubleshooting section here says that the webhooks are workspace-wide: https://www.pulumi.com/docs/integrations/version-control/bitbucket/ But I can find no mention of workspace-level webhooks in Atlassian documentation. The mentioned menu items Workspace Settings > Webhooks doesn't exist. The only webhooks mentioned in Atlassian docs are repository level https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/. I can see my repo's webhooks at Repository Settings > Workflow > Webhooks, and there's no mention of Pulumi in there. Knowing Atlassian, they moved Webhooks to repositories and announced it publicly by posting it to the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard". Any chance of Pulumi updating to accommodate? And in the meantime, can I manually add webhooks to the registry settings? What would they look like?

Did you get anywhere @little-cartoon-10569? I found that the hooks might be API only: https://support.atlassian.com/bitbucket-cloud/kb/how-to-create-workspace-level-webhooks/

Thanks for that, that's helpful. It's a bit of a security oopsie on Atlassian's part, if I can't visually review the webhooks installed on my workspaces.. But at least I can debug with this. I'll update here.

Let me ping someone

Ah. Could it be because the Bitbucket workspace in question is on a standard, non-premium plan? Premium is required for workspace API tokens, and maybe that restriction overflows to webhooks? I have another workspace with the same repo, and it's on premium. I'll try there and report back.

Hey @little-cartoon-10569, under the repository that you are trying to integrate with do you see any webhooks listed? You should be able to use a free org here.

No Pulumi webhooks 😞

Hmm. And you have the deployment settings saved for a corresponding stack that uses that specific repo?

What are "deployment settings" in this context? Sorry, I've been integrating a lot of tools lately and similar terms are cropping up frequently and overlapping with each other in my mind.

No worries! If you navigate to a project -> stack -> settings you should see these deployment settings listed here.

Yea... nah. I don't have most of that.

Interesting, I'll have to see why those are in a state like that.

Ooo, navigated around to a few stacks that I haven't worked with in a bit, and these notifications have appeared:

Thank you. Are you using RBAC features, and do you have the stack read permissions?

I doubt it.. it's one of those old Teams accounts from 2020 with only 3 seats

Hmm, I see. Are you an admin on the org?

Yes

Hey Tenwit, sorry for the delay. Just wanted to update you that we are looking into this issue so that we can quickly get you back on the path of BitBucket integration!

Hi @adorable-solstice-42836 Did you find anything useful? Is it just due to Team Starter, or is there something I've missed and can fix?

Hey Tenwit! Followed up on this and believe I have found the solution and hoping to get a PR merged in shortly that should get you your PR comments working in BitBucket. In terms of the weirdness you encountered, I suspect that's also caused by a weird interaction between Team Starter and the logic gates that control the settings subtabs. That should definitively not happen regardless, so we're investigating that further. One thing I wanted to clarify: there are some stacks for which you cannot see or interact with the "Settings" tab, even though you are an org admin? You should definitely have access to this tab always as an org admin, so we'll investigate that also.

The settings tab can always be found, but it disappears depending on which other tab you're on. Onesec I'll get the conditions right.

Ah okay, strange! Also, can you try setting up the BitBucket integration again and running your Pulumi CI? You should see comments now!

On it, ty!

Sweet! Sorry for the delay, please do let me know of any problems as they arise!