Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove UseIsolatedEnv from system.Command #110

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

aramprice
Copy link
Member

This struct attribute is only ever set to true by the bosh-cli, and the value if this use case is in question, see:

In addition the UseIsolatedEnv capability can be wholely handled within the bosh-cli codebase itself without the need for this featuer in bosh-utils.

@aramprice
Copy link
Member Author

aramprice commented Dec 12, 2024

Master Branch Protection / check-branch (pull_request) is ❌ even though the PR was initially created against develop

¯_(ツ)_/¯

... and then force-pushing to fix a comment (maybe?) re-ran the check and it's ✅

This struct attribute is only ever set to `true` by the bosh-cli, and
the value if this use case is in question, see:
- cloudfoundry/bosh-cli#660
- cloudfoundry/bosh-cli#663
- cloudfoundry/bosh-cli#673

In addition the `UseIsolatedEnv` capability can be wholely handled
within the `bosh-cli` codebase itself without the need for this featuer
in `bosh-utils`.
@aramprice aramprice force-pushed the remove-use-isolated-env branch from 3d85a2a to c7f70b5 Compare December 12, 2024 22:54
@aramprice aramprice changed the title Rmove UseIsolatedEnv from system.Command Remove UseIsolatedEnv from system.Command Dec 12, 2024
@aramprice aramprice marked this pull request as draft December 12, 2024 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

1 participant