Detect multiple `esc run -- cmd` in a session and recommend alternatives

[pose]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

I'm new to the Pulumi ecosystem so I was invoking pulumi this way:

esc run myorg/myenv -- pulumi preview
esc run myorg/myenv -- pulumi up
# Code changes
esc run myorg/myenv -- pulumi preview
esc run myorg/myenv -- pulumi up
# Code changes
esc run myorg/myenv -- pulumi preview
esc run myorg/myenv -- pulumi up

Questions:

• Could we detect through env if the user is doing a lot of esc run and suggest either:
  • eval $(pulumi env open -f shell myorg/myenv)
  • Add to the Pulumi.my-stack.yaml file an environment entry for myorg/myenv.

Also, @rgharris suggested an alternative approach that could be an opt-in configuration via the ESC yaml like:

imports:
    - #pulumi-context

That could be included that in the empty template/when creating a new env from pulumi config so you get it by default for future envs.

Discarded Approach

• We are polluting the env and it's a breaking change: cli: Add ESC-specific environment variables to esc run command. #570

Affected area/feature

esc / pulumi/pulumi