Skip to content

A Flag to deactivate the Escaping for Enviroment Variables #957

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

Closed
wants to merge 6 commits into from

Conversation

Taikobo2
Copy link

Summary

I created a Flag to disable esaping of Enviroment Variables

Additional Context

Add any additional context about the problem here.

  • In our Enviroment the DOCKER_GID needs to be Dynamicaly set. But the Escapings hindered our shell to do so.
  • Thats why we just created the Flag, so People can disable the Escaping for a more Dynamical environment.

Related Issues (if any)

Your Change came in PR: docker_run_flags: Shellescape any provided values #869

Checklist

  • i Manully checked that in my docker Puppetenviroment by puppet apply.

@Taikobo2 Taikobo2 requested a review from a team as a code owner October 20, 2023 09:01
@CLAassistant
Copy link

CLAassistant commented Oct 20, 2023

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Taikobo2
❌ u2382/Mario Sicilia


u2382/Mario Sicilia seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@Taikobo2 Taikobo2 closed this Oct 20, 2023
@Taikobo2 Taikobo2 deleted the Environment_escape_flag branch October 20, 2023 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants