Bump github.com/vladimirvivien/gexe from 0.2.0 to 0.3.0 in the all group

[dependabot[bot]]

Bumps the all group with 1 update: github.com/vladimirvivien/gexe.

Updates github.com/vladimirvivien/gexe from 0.2.0 to 0.3.0

Release notes

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

v0.3.0

What's Changed

Improvement of session variables

Now all types (existing and new ones) allows an injection of value of type vars.Variables to allow tracking and use of variables during a gexe session. The following shows an example of process being launched with variables:

variables := vars.New().SetVar("proc", "echo")
exec.RunProcWithVars(`$proc "Hello World!"`, variables)

In the majority of cases, you will start the API chain from the gexe package which has a default instance of vars.Variables ready to use as shown below:

gexe.SetVar("proc", "echo")
gexe.Run(`$proc "Hello World!")

Extending the fs package

The fs package has been extended to introduce types and methods to work with OS directory paths. In addition to working with files, the new fs.Path allows the followings:

• Query path information
• Creation of directory at a specified path point
• Removal of resources at specified path

Improvements to package http

In this release, package http has been updated to use an API similar to that of fs (for file reading/writing). Using the new API makes it easy to retrieve resources from an HTTP server and output it in different types including string, bytes, io.Reader, etc. The same changes has been done to write data to a remote web server.

Example:

gexe.FileWrite("/tmp/eapv2.txt").String(gexe.GetUrl(`https://remote/file`).String())

PR list

• See PR General improvements for project by @​vladimirvivien in vladimirvivien/gexe#51
• Update project documentation by @​vladimirvivien in vladimirvivien/gexe#52

Full Changelog: https://github.com/vladimirvivien/gexe/compare/v0.2.0...v0.3.0

Commits

• 14fa016 Merge pull request #52 from vladimirvivien/update-doc
• d243e3b Update project documentation
• bc8da74 Merge pull request #51 from vladimirvivien/improvements-add-missing-features
• 6132d28 General improvements for project
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[k8s-ci-robot]

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

I'm waiting for a kubernetes-sigs 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[harshanarayana]

/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, dependabot[bot]

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

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/kubernetes-sigs/e2e-framework/blob/main/OWNERS)~~ [cpanato] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment