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.

Sign up for GitHub

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

Jump to bottom

Changes from schedule.enable / schedule.disable not persisted #54847

Closed
OrangeDog opened this issue Oct 2, 2019 · 5 comments
Closed

Changes from schedule.enable / schedule.disable not persisted #54847

OrangeDog opened this issue Oct 2, 2019 · 5 comments
Assignees
@garethgreenaway
Labels
Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Feature new functionality including changes to functionality and code refactors, etc.
Milestone
Approved

Comments

@OrangeDog
Copy link
Contributor

OrangeDog commented Oct 2, 2019 •
edited
Loading

Description of Issue

Changes made by salt-call schedule.enable or salt-call schedule.disable are not reflected on-disk in /etc/salt/minion.d/_schedule.conf, but do appear in salt-call schedule.list. Similarly, salt-call schedule.reload doesn't have any affect on the global status.

https://gist.github.com/OrangeDog/fd08470a682752347efd52fe7a5b830d
@OrangeDog OrangeDog mentioned this issue Oct 2, 2019
Closed
@garethgreenaway garethgreenaway self-assigned this Oct 2, 2019
@garethgreenaway
Copy link
Contributor

This should be a simple fix and we'll get it for the Neon release since it would technically be a new feature, we currently support being able to persist when enabling and disabling individual jobs but not the entire scheduler.

@garethgreenaway garethgreenaway added this to the Approved milestone Oct 2, 2019
@garethgreenaway garethgreenaway added the Feature new functionality including changes to functionality and code refactors, etc. label Oct 2, 2019
@garethgreenaway garethgreenaway mentioned this issue Oct 2, 2019
Merged
@stale
Copy link

stale bot commented Jan 7, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Jan 7, 2020
@OrangeDog
Copy link
Contributor Author

Still a desired feature

@stale
Copy link

stale bot commented Jan 7, 2020

Thank you for updating this issue. It is no longer marked as stale.

@stale stale bot removed the stale label Jan 7, 2020
@waynew waynew added the Confirmed Salt engineer has confirmed bug/feature - often including a MCVE label Jan 7, 2020
@OrangeDog
Copy link
Contributor Author

This was released in 3000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@garethgreenaway garethgreenaway

Labels
Confirmed Salt engineer has confirmed bug/feature - often including a MCVE Feature new functionality including changes to functionality and code refactors, etc.
Projects
None yet
Milestone
Approved
Development

No branches or pull requests
3 participants
@waynew @OrangeDog @garethgreenaway