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

Pass pillar data through kwarg for salt.state #13575

Closed
dnd opened this issue Jun 19, 2014 · 4 comments
Closed

Pass pillar data through kwarg for salt.state #13575

dnd opened this issue Jun 19, 2014 · 4 comments
Labels
Duplicate Duplicate of another issue or PR - will be closed Feature new functionality including changes to functionality and code refactors, etc.
Milestone

Comments

@dnd
Copy link
Contributor

dnd commented Jun 19, 2014

Through discussion on IRC, currently custom pillar data can be set on the command line when calling states, or using salt-run for say the orchestration runner. Pillar data cannot be set inside an orchestration file, and then passed along to the states that it calls, though.

@whiteinge
Copy link
Contributor

Thanks for filing this. It would be handy to be able to define custom Pillar values within the orchestrate sls file.

The salt.state function needs a kwarg option like the salt.function has. (Or just a dedicated pillar kwarg.)

Something like:

stuff_and_things:
  salt.state:
    - tgt: 'all-the-minions'
    - sls: mygroovyslsfile
    - pillar:
        stuff: True
        things: False

@whiteinge whiteinge added this to the Approved milestone Jun 19, 2014
@basepi
Copy link
Contributor

basepi commented Jun 19, 2014

This is a duplicate of #11904.

@whiteinge
Copy link
Contributor

My bad.

@basepi
Copy link
Contributor

basepi commented Jun 19, 2014

No worries. =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Duplicate of another issue or PR - will be closed Feature new functionality including changes to functionality and code refactors, etc.
Projects
None yet
Development

No branches or pull requests

3 participants