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

add vault|unvault filters #12087

Closed
bcoca opened this issue Aug 25, 2015 · 3 comments
Closed

add vault|unvault filters #12087

bcoca opened this issue Aug 25, 2015 · 3 comments
Assignees
Labels
affects_2.1 This issue/PR affects Ansible v2.1 affects_2.3 This issue/PR affects Ansible v2.3 feature This issue/PR relates to a feature request. support:core This issue/PR relates to code supported by the Ansible Engineering Team.

Comments

@bcoca
Copy link
Member

bcoca commented Aug 25, 2015

ISSUE TYPE

Feature Idea

COMPONENT NAME

core

ANSIBLE VERSION

2.1

CONFIGURATION
OS / ENVIRONMENT
SUMMARY

they should take in a string and create a vault hash (vault) or take in a vault hash and return the containing string (unvault).

STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
@h0nIg
Copy link
Contributor

h0nIg commented Nov 25, 2015

do you have an idea to create this filter? since you can not access the parser instance (with vault password saved) from a filter class, this seems to be impossible right now

@bcoca
Copy link
Member Author

bcoca commented Nov 25, 2015

I was thinking we either need to pass the vault object to action plugins and filters or allow for explicitly passing as a variable.
It requires more changes than just creating the filter itself, which is the easy part and would have been done already if I could figure out best way to pass vault w/o making it insecure.

@jimi-c jimi-c removed the P3 label Dec 7, 2015
@alikins alikins self-assigned this May 26, 2016
@ansibot ansibot added the affects_2.1 This issue/PR affects Ansible v2.1 label Sep 8, 2016
@bcoca bcoca removed affects_2.0 This issue/PR affects Ansible v2.0 affects_2.1 This issue/PR affects Ansible v2.1 labels Sep 15, 2016
@ansibot ansibot added the affects_2.1 This issue/PR affects Ansible v2.1 label Sep 15, 2016
@ansibot ansibot added the affects_2.3 This issue/PR affects Ansible v2.3 label Dec 13, 2016
@ansibot ansibot added needs_info This issue requires further information. Please answer any outstanding questions. needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly. labels Apr 4, 2017
@ansibot
Copy link
Contributor

ansibot commented Apr 4, 2017

@bcoca Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

  • issue type
  • ansible version
  • component name

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

@ansibot ansibot removed needs_info This issue requires further information. Please answer any outstanding questions. needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly. labels Apr 4, 2017
@ansibot ansibot added the support:core This issue/PR relates to code supported by the Ansible Engineering Team. label Jun 29, 2017
@calfonso calfonso closed this as completed Oct 5, 2017
@ansibot ansibot added feature This issue/PR relates to a feature request. and removed feature_idea labels Mar 2, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.1 This issue/PR affects Ansible v2.1 affects_2.3 This issue/PR affects Ansible v2.3 feature This issue/PR relates to a feature request. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

No branches or pull requests

6 participants