Aaron Friel
Aaron Friel
We recently shipped `PULUMI_ORGANIZATION` as an env var in Pulumi YAML: https://github.com/pulumi/pulumi-yaml/pull/578/files#diff-104a11712684e520f0affa95e6a053faeb713306a10f69ee99b9729cc9dd1996R134 Likely do not want to conflict with that, so 👍 to Joe's comment.
It would be great if this worked with Pulumi ESC as well, to specify default environments and act as a `direnv` or `dotenv` replacement.
@justinvp did you want to review this?
@glena would that be a breaking API change for remote automation API because it's inferring based on the URL whether to use the GitHub integration implicitly, vs explicitly?
Oh, that makes sense! I thought that was a review comment. The default to "true" here is why I chose not to use that implementation, but plumbing a `--use-github-app` or...
I made this issue so I can close it :) Yes, PRs already build artifacts, we just don't have a way of installing them via the `get.pulumi.com` script
Left open intentionally, will close with a PR that adds a comment describing how to install the CI built release and extending the retention period to 1 week.
Closing as complete - technically possible due to get.pulumi.com updates - due to lack of agreement on #17015.
Adding some background research on this and why we see this. My current assumption is: 1. We are falling back to SSH agent too quickly, having failed to find an...
> after separating beam search and the vllm core, they can be optimized individually. The simplified code will be much easier to optimize. This is a good goal to work...