Not sure if this is the right channel but I am get...
# general
c
Not sure if this is the right channel but I am getting a 404 when trying to visit the pulumi dashboard
w
Hey Chris - great to see you here. Did you see this after going through GitHub login flow? If you go straight to https://app.pulumi.com/ does that work?
c
Going directly to the URL gives me the same result. I see the dashboard briefly
Hi Luke, it has been quite a long time
Looks like you guys are doing some really cool stuff
w
cc @square-apartment-28429 for thoughts on the 404. I can't reproduce it from here.
BTW - are you still working on Azure DevOps? We'd love to chat about integrations.
c
Yes I am and that is exactly what I am working on
was just getting around the spending some time with pulumi and Azure Pipelines
I need to make a trip to Seattle in the near future.
I think I foud the issue
I have a GitHub org that I have renamed but Pulumi is still looking for it
w
Great! We'll reach out to chat more on this. @clever-sunset-76585 and @square-apartment-28429 have been doing work on CI integrations and Azure DevOps is high on the list.
I have a GitHub org that I have renamed but Pulumi is still looking for it
Ahh - interesting. We'll look into getting that fixed. Can you see https://app.pulumi.com/chrisrpatterson?
c
I can see that one fine it is this request that is getting the 404 https://api.pulumi.com/api/orgs/vstscipm/programs
w
Got it - that makes sense. We'll get that fixed.
c
Which explains the flash
I can send you the .har if you want over email
w
Wouldn't hurt - though I think we likely have enough info. I'm at luke@pulumi.com.
c
done. Look forward to chatting about integration options
đź‘Ť 1
c
Sorry for missing this thread earlier. You may be able to get back online by visiting https://app.pulumi.com/logout. This will log you out, but hopefully logging in again will get you into a good state. Alternatively, you could visit https://app.pulumi.com/account/github and click “refresh”. Depending on the specific way we are failing, that might be able to correct the data. Regardless, we’ll get this fixed ASAP. Sorry for the inconvenience.