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

Continuation of issue #11868: target by state ID #65292

Open
Mrten opened this issue Sep 26, 2023 · 2 comments
Open

Continuation of issue #11868: target by state ID #65292

Mrten opened this issue Sep 26, 2023 · 2 comments
Labels
Feature new functionality including changes to functionality and code refactors, etc. info-needed waiting for more info needs-triage

Comments

@Mrten
Copy link
Contributor

Mrten commented Sep 26, 2023

I'd like to target highstate runs by state. This way I could, say, restart all apaches at the same time and be sure that I haven't missed any.

Like this:

salt -S apache state.highstate

Explanation: I write my states for, say, apache, with one basic state that sets everything that I want the same for all apaches (like the LogFormat, the mimesettings, etc) and include: that basic state from every other apache that gets deployed, however different its usecase may be.

When one is then confronted with something like the Heartbleed OpenSSL bug one would like to upgrade/restart all those apaches in one go.

I could work around this with pillar values but that feels like a kludge to me.

Workarounds with jq exist, see here.

@Mrten Mrten added Feature new functionality including changes to functionality and code refactors, etc. needs-triage labels Sep 26, 2023
@Mrten
Copy link
Contributor Author

Mrten commented Sep 26, 2023

There's lots of input from other folks on the referred issue.

@dmurphy18 dmurphy18 added the info-needed waiting for more info label Sep 26, 2023
@dmurphy18
Copy link
Contributor

@Mrten One of the reason for closing out old issues, circa 10 years ago, was to use the new template with issues etc. stating, bug, feature request, etc. which allows for better tracking etc.

Can you please update this accordingly,since this is a Feature Request, if you want the issue to be considered. Noting you had Feature Request on the old issue from 2014.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. info-needed waiting for more info needs-triage
Projects
None yet
Development

No branches or pull requests

2 participants