Hey guys, I'm still pretty new to Pulumi but I've hit the ground running over the past few weeks and have been really happy with it. I'm really interested in setting up hosted deployments on Pulumi Cloud, but no matter what I plug in, I get a 403 error. Has anyone seen this, and if so, how did you fix it?

@fresh-zebra-397 can you take a screenshot?

this is what pops up:

no that’s okay, just needed to track the request on the backend, will get the team to take a look

awesome, thanks a lot!

Pulumi is the best thing since sliced bread, arguably nothing is better hands down. Honestly I don’t even want universal health care anymore just gimme more Pulumi awesomeness.

yeah it's been a nice reprieve not having to constantly look up HCL syntax so I can spin things up; definitely enjoying the ride right now! really want to dig into Cloud more and set up review stacks. really looking forward to seeing that magic.

Yeah, the hard thing is convincing the execs of the world that Terraform is terribad and makes most of us in the industry want to jump off a cliff. Sadly TF has been around a bit longer so they got a head start and they have a pretty strong hype machine they use to glow up their tool. Ive been working to advocate for it in my company so we can purchase the saas its been a difficult journey.

Yeah I'm in this really weird position right now where I get to suggest/recommend the tools and people value my opinion. I'm still getting used to it. I actually initially was going to go with Terraform, but I liked the idea that all our devs know javascript, so if I get hit by a bus tomorrow, it'll be easier for them to understand what's going on.

One additional point I made which may be useful for yourself is that Pulumi is a tool for everyone so even the folks who arent devs can contribute and create their own stacks as it supports the ability to write it in a non programming language too. Not to mention they can also write their terraform code the way they want and have pulumi just eat it and spit out the code they need

right now my company has zero IaC, and almost no CICD, or any other automation. baby steps. they want to do things the right way though which is weird, so I'm taking advantage of that and not rushing to churn shit out haha. so i'll be building it all on my own for a while, and then maybe i can give up some control once we have SOPs and such in place.

Take a look at using Github Enterprise Cloud for CI\CD itll make your lives so much easier and allow you to pivot on cloud providers super easy. The code scanning tools it has are also real nice

we're already started with gitlab. i adore gitlab, and it's working beautiful.

Pulumi has some nice integrations with GHEC too*

the pulumi/github integrations do look amazing though. i'm jealous of that. i'll be manually building similar setups

Yeah, some of that stuff can be offloaded with their SAAS is you can swing getting that into your org

@fresh-zebra-397 if you could screenshot the settings you’re trying to save it would be super helpful. The network tab from your console would also be helpful too. Feel free to DM me that information if it’s sensitive

awesome thanks a lot. i'll be in and out because it's currently 10:40pm where I am and I have a very early flight. Lee said the theory is that the 403 is coming from Gitlab, so I'm going to try to take a look at my gitlab logs and see what's going on. It might be a while before I get to it; possibly not until friday afternoon eastern time

Sorry for the trouble here @fresh-zebra-397 - we did some digging through the logs and it looks like you haven't verified the email address on your Pulumi account. This is blocking you from using deployments, we'll improve the experience here to surface a better error message. If you verify your email, you should be good to go.

@lemon-agent-27707 I'm glad it's an easy fix! The only problem now is that I'm not getting the verification e-mail (I checked my inbox and it looks like I never received an initial one when I created my account either). Maybe it's just delayed though; I'll let you know if I don't receive one in a few more hours.