(IAC-732) - implement `Run only when user is logged on #150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scheduled_task is a typeBreaking changes to this file MAY impact these 10 modules (near match):This module is declared in 0 of 575 indexed public
|
Codecov Report
@@ Coverage Diff @@
## master #150 +/- ##
==========================================
- Coverage 95.31% 94.97% -0.35%
==========================================
Files 6 6
Lines 833 835 +2
==========================================
- Hits 794 793 -1
- Misses 39 42 +3
Continue to review full report at Codecov.
|
sanfrancrisko
approved these changes
Jul 30, 2020
REFERENCE.md
Outdated
| @@ -66,6 +66,10 @@ Please also note that Puppet must be running as a privileged user | |||
| in order to manage `scheduled_task` resources. Running as an | |||
| unprivileged user will result in 'access denied' errors. | |||
|
|
|||
| If a user is specified without an accompanying password the | |||
There was a problem hiding this comment.
Suggested change
| If a user is specified without an accompanying password the | |
| If a user is specified without an accompanying password, the |
sanfrancrisko
approved these changes
Jul 30, 2020
sigv
added a commit
to sigv/puppetlabs-scheduled_task
that referenced
this pull request
Mar 29, 2021
Since the enhancement intended to help sysadmins, pulled in as puppetlabs#150: When not setting a password, this is interpreted as "Run only when user is logged on". When configuring a scheduled task to use a Group Managed Service Account (gMSA) principal, there is no password to provide. The scheduler will get the password automatically when properly configured, and should be able to run the task even though the service account is not "logged on". Otherwise, the Managed Service Account is never "logged on" so the task does not run on expected schedule. It does not seem viable to add a proper test case for this particular situation without an AD domain configuration and a proper gMSA in place. Without a correct gMSA, an error message stating "No mapping between account names and security IDs was done" appears to be returned.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.