So! At the moment, Get-PSDeployment does a few (IMHO) bad things:
It tests for source existing. If this fails:
It assumes path is relative, joins path with DeploymentRoot
It errors out
There are many conceivable cases where a Source may not exist - e.g. perhaps you are chaining deployments
Made the following changes to accommodate this
Added handling for specifying WithOptions @{SourceIsAbsolute = $True}. When this is used, we don't assume it is a relative path, even when test-path fails
Created an array of reserved options, including SourceIsAbsolute ... these will never be splatted against a deployment script, or generate warnings
Hit me up if you have any concerns, suggestions, etc! Will plan to merge this evening (Sunday) or tomorrow AM.
So! At the moment, Get-PSDeployment does a few (IMHO) bad things:
There are many conceivable cases where a Source may not exist - e.g. perhaps you are chaining deployments
Made the following changes to accommodate this
WithOptions @{SourceIsAbsolute = $True}. When this is used, we don't assume it is a relative path, even when test-path failsSourceIsAbsolute... these will never be splatted against a deployment script, or generate warningsHit me up if you have any concerns, suggestions, etc! Will plan to merge this evening (Sunday) or tomorrow AM.
Cheers!