Chris Smith

Closing this out and moving the relevant details into the parent ticket: https://github.com/sourcegraph/self-serve-cody/issues/631. I'll break down the remaining steps there.

We probably would want to do the same thing for `CodySubscriptionPage.tsx`, since that too will go through several waves of changes as we progressively roll out the PLG experience.

Here are a couple of issues that came up _today_ as we take a closer look at this particular page. - https://github.com/sourcegraph/accounts.sourcegraph.com/issues/442 - https://github.com/sourcegraph/accounts.sourcegraph.com/issues/444

So the behavior you are seeing is generally by design. In order to pick up the packages managed by `pipenv`, any commands need to be in a processed launched by...

Yes, sorry about that. The root issue is that the `pulumi/login` command downloads the "latest" version of the CLI by default. You can set the `version` parameter to fix this...

Thanks for taking look @kenfdev! Yes, filing an issue for each of those areas would be reasonable. As far as addressing them, a few notes: > PULUMI_ACCESS_TOKEN is not explained...

> About the executor, do you have a recommendation for a default executor? Looks like the slack's orb is using cibuilds/base:latest. TBH I don't know enough to have a strong...

> adding a default executor without a job doesn't make much sense. IIUC, the executor defined in the orb shines when it is used inside its job. Yeah, you are...

Perhaps there is a 4th option? Could we provide an overlay that provides an interface similar to an atomic update? e.g. "set this policy IFF it was equal to value...

One theory that unfortunately didn't work out was if we enabled Website Hosting on the underlying S3 bucket, and provided an "error document" which is a custom file to return...