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

Ensure we pass on the enable setting if present, or use the default of True if not in build_schedule_item() #27442

Merged
merged 1 commit into from Oct 5, 2015

Conversation

JaseFace
Copy link
Contributor

Prior to this, when schedule.present compares the existing schedule to the one crafted by this function, enabled will actually be removed at each run. schedule.present sees a modification needs to be made, and invokes schedule.modify, which does so with enabled: True, creating and endless loop of an 'enabled' removal and addition.

…f True if not in build_schedule_item()

Prior to this, when schedule.present compares the existing schedule to the one crafted by this function, enabled will actually be removed at each run.  schedule.present sees a modification needs to be made, and invokes schedule.modify, which does so with enabled: True, creating and endless loop of an 'enabled' removal and addition.
@rallytime
Copy link
Contributor

Thanks @JaseFace!

rallytime pushed a commit that referenced this pull request Oct 5, 2015
Ensure we pass on the enable setting if present, or use the default of True if not in build_schedule_item()
@rallytime rallytime merged commit 7d7b97e into saltstack:2015.5 Oct 5, 2015
@JaseFace JaseFace deleted the fix-27391-for-2015.5 branch October 30, 2015 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core relates to code central or existential to Salt Execution-Module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants