Invoke-SpnLifecycle
Runs the SpnManager SPN lifecycle for a registered provider.
module 0.4.0PowerShell 5.1 · 7SupportsShouldProcesswrites to AD when Implement runs
voice / plain · this tab is sample content; the generation pipeline supplies the real voices
This is the one command most people run first. Give it a provider ID and it walks the whole lifecycle for that provider: it senses what is running, proposes the SPN set, tests the plan against AD, and then either implements the change or, for audit-only providers, produces a hand-off bundle.
Nothing is written to AD unless the provider has a write path and you did not pass -WhatIf. For any provider whose far side holds a keytab, the final stage is always a runbook.
Each stage is a separate function registered in providers.json. This command is thin glue; MCP and pipeline callers should call the stages directly.
parameters
- -ProviderId
- Registry ID of the provider to run, for example
SQL.EngineorAD.RDP. Must match a registered provider with Status = Implemented. Mandatory. - -TargetComputer
- Host to target. Forwarded to each stage function that declares a TargetComputer parameter; local-only sense functions receive nothing.
- -PassThru
- Return the final stage result object to the pipeline. Without it, progress goes to Write-Verbose only.
- -WhatIf / -Confirm
- Standard ShouldProcess switches. -WhatIf shows what the Implement stage would do without changing AD.
examples
outputs
Nothing by default. With -PassThru: the result object from the final stage — SpnExecutionResult, SpnAuditResult, or a hand-off bundle.
stage routing
| stage | receives | notes |
|---|---|---|
| Sense | TargetComputer, if accepted | |
| Propose | Candidate + TargetComputer | |
| Test | Plan + TargetComputer | blocks on unresolved conflict |
| Implement | Plan + TargetComputer | ShouldProcess-gated |
| Handoff | Plan + TargetComputer | audit-only providers |
related
generated from module source ·
{{ tok.WIKI_BUILD_ID }}report an error on this page