Bump github.com/vladimirvivien/gexe from 0.3.0 to 0.4.1

[dependabot]

Bumps github.com/vladimirvivien/gexe from 0.3.0 to 0.4.1.

Release notes

Sourced from github.com/vladimirvivien/gexe's releases.

v0.4.1

What's Changed

• Updates to CI and CI configurations by @​cpanato in vladimirvivien/gexe#55
• Fixes to example docs by @​vladimirvivien in vladimirvivien/gexe#58
• Ability to specify userid/groupid for process execution by @​vladimirvivien in vladimirvivien/gexe#59
• Ability to set working directory for commands by @​vladimirvivien in vladimirvivien/gexe#61
• Support for context-awareness to gexe packages by @​vladimirvivien in vladimirvivien/gexe#63

New Contributors

• @​cpanato made their first contribution in vladimirvivien/gexe#55

Full Changelog: vladimirvivien/gexe@v0.4.0...v0.4.1

v0.4.0

This release did not introduce new functionalities, but rather implemented fixes and improvements that have been lingering for a while.

Release overview

• Better support for setting Stdout/Stderr when working with exec package
• Fixed out-of-order bug that would make exec.Proc.Resut() and exec.Proc.Out() calls return empty result from the process
• Additional checked error propagation in API call chain in several packages
• Enhancements to exec.CommandBuilder to fix piped commands constructs
• Ability to set stdout/stderr for batch commands with exec.CommandBuilder
• Further standardization of function and method signatures for packages http and fs
• Enhancements to internal tests

API changes

Package exec changes

Previously, method Proc.Out() in package exec would automatically start a defined process (if not started) then return output of the process as a combined Stdout/Stderr streams. This behavior has been simplified:

• The API user is responsible for starting the process prior to calling proc.Out()
• Method Proc.Out() only returns the combined output stream if no other streams were set for the process
• If other streams were set, an API user is responsible for accessing the configured output stream for process result.

Method proc.Result() still returns the combined output stream as string (by calling proc.Out()) if an output stream was not explicitly set.

See example here

Package vars changes

This release introduces subtle changes to how methods vars.Variables.Envs and vars.Variables.Vars work. Before this release, these methods accepted a single string with key=value pairs separated by spaces:

gexe.Vars(`msg0=hello msg1=world`).

In this release, however, the signatures for both Envs and Vars have been updated as variadic methods that accept zero or more string values. Each string parameter is not expected to provide a single key=value pair:

gexe.Envs(`GOOS="linux"`, `GOARCH=arm64`).Run(`go build .`)

Note that this change provides the flexibility of specifying variables with quoted values and supports spaces in the values.

Related PRs

... (truncated)

Commits

• 718e158 Add context-awareness to gexe packages (#63)
• a87a71f Ability to set working directory for commands (#61)
• ed0dddd Support for setting userid/groupid for process execution (#59)
• e2c675e Examples fix (#58)
• 1c64441 updates on ci (#55)
• f294aef Lock contention fix (#54)
• 1ce1b90 Diverse functionality improvements (#53)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign msherif1234 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a netobserv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.