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

Set -env variables as appropriate #3665

Merged
merged 1 commit into from
Jul 30, 2019

Conversation

QiWang19
Copy link
Contributor

close #3648

podman create and podman run do not set --env value if the environment is not present with a value

Signed-off-by: Qi Wang [email protected]

@mheon
Copy link
Member

mheon commented Jul 29, 2019

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2019
docs/podman-run.1.md Outdated Show resolved Hide resolved
Copy link
Member

@TomSweeneyRedHat TomSweeneyRedHat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title is messed up, please change it. Perhaps "Set -env variables as appropriate"

@QiWang19 QiWang19 changed the title not set --env if thvariable is not present Set -env variables as appropriate Jul 30, 2019
test/e2e/run_test.go Outdated Show resolved Hide resolved
@QiWang19 QiWang19 force-pushed the env branch 2 times, most recently from 8fa7103 to a4570f0 Compare July 30, 2019 14:44
@@ -253,7 +253,7 @@ You need to specify multi option commands in the form of a json string.

Set environment variables

This option allows you to specify arbitrary environment variables that are available for the process that will be launched inside of the container. If you specify a environment variable without a value, podman will check the host environment for a value or set the environment to "". If you specify a environment variable ending in --*--, podman will search the host environment for variables starting with the prefix and add them to the container. If you want to add an environment variable with a ***** following it, then you need to set a value.
This option allows arbitrary environment variables that are available for the process to be launched inside of the container. If an environment variable is specified without a value, Podman will check the host environment for a value and set the variable only if it is set on the host. If an environment variable ending in __*__ is specified, Podman will search the host environment for variables starting with the prefix and will add those variable to the container. If an environment variable with a trailing ***** is specified, then a value must be supplied.

See **Environment** note below for precedence.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a link to #environment? from the **Environment**

@TomSweeneyRedHat
Copy link
Member

@QiWang19 fwiw, I'm done picking nits!

@QiWang19 QiWang19 force-pushed the env branch 2 times, most recently from 081da34 to bf22f16 Compare July 30, 2019 15:55
close containers#3648

podman create and podman run do not set --env variable if the environment is not present with a value

Signed-off-by: Qi Wang <[email protected]>
@QiWang19
Copy link
Contributor Author

@TomSweeneyRedHat @mheon PTAL

Copy link
Member

@TomSweeneyRedHat TomSweeneyRedHat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @QiWang19

@TomSweeneyRedHat
Copy link
Member

@giuseppe has you change been addressed? Can you remove the request if so please?

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe, mheon, QiWang19

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:

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

@giuseppe
Copy link
Member

LGTM

@rhatdan
Copy link
Member

rhatdan commented Jul 30, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2019
@openshift-merge-robot openshift-merge-robot merged commit e84ed3c into containers:master Jul 30, 2019
@QiWang19 QiWang19 deleted the env branch June 26, 2020 15:10
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Environment passing behavior differes from docker
7 participants