You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Pulumi deploy uses the pulumi/pulumi image by default.
It would be useful to have the Pulumi esc command installed on the image so it is available for things like prerun commands that use esc env run
Affected area/feature
The text was updated successfully, but these errors were encountered:
I'm considering contributing to this and it looks like it might be a fairly substantial change from the workflows, CI, and finally the images themselves. To avoid a lot of back and forth on the PR I was wondering if you had thoughts on whether this should be an additional top-level variable next to pulumi_version, and if so, if you could offer some insight into the events that appear to be defaulting the existing pulumi version ENV variables.
I assume this is typically triggered via an event hook from upstream pulumi SDK changes. If so, could you offer context or guidelines on replicating that from an upstream ESC pipeline?
Lastly, if it would be desired to replicate event hooks, top level variables, environment variable defaults all for ESC... it seems like it might be a good time to rename the existing 'pulumi_version' to 'pulumi_iac_version' so the new variables and defaults could be 'pulumi_esc_version' now that the products are GA and more differentiated.
Hello!
Issue details
Pulumi deploy uses the pulumi/pulumi image by default.
It would be useful to have the Pulumi
esc
command installed on the image so it is available for things like prerun commands that useesc env run
Affected area/feature
The text was updated successfully, but these errors were encountered: