cloudfoundry / cloudfoundry/cli
cf ssh - container does not have app's environment (same issue 3 years later)
Open
@a-b is already working on this.
Since Oct 3, 2024.
unscheduled
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 990
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
Description
When I run cf ssh <app> the terminal session does not have the same environment that the application process has - my $PATH etc is not setup for the interpreter provided by the buildpack, etc.
I must always remember to run /tmp/lifecycle/launcher "app" "$SHELL" "" immediately after cf ssh.
When I raised this in Feb 2016 (3 years ago) in cloudfoundry/cloud_controller_ng#754 the answer was something about Windows support.
Can we please fix this now so that cf ssh always sets up the environment to match the application process from the buildpack?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.