Julien P 1672ba246f Use the full path when running pulumi from a custom CLI install (#15802) ... # Description <!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> Fixes https://github.com/pulumi/pulumi/issues/15796 Turns out nodejs already uses the [full command name](bc4a9ad59b/sdk/nodejs/automation/cmd.ts (L176)). Fixed for python and go. ## Checklist - [x] I have run `make tidy` to update any new dependencies - [x] I have run `make lint` to verify my code passes the lint check - [x] I have formatted my code using `gofumpt` <!--- Please provide details if the checkbox below is to be left unchecked. --> - [x] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. -->		2024-03-27 21:12:00 +00:00
..
pending	Use the full path when running pulumi from a custom CLI install (#15802)	2024-03-27 21:12:00 +00:00
config.yaml	Fix coming soon misrender (#15783)	2024-03-26 17:24:37 +00:00