Thanks everyone who provided feedback on this ticket. We published a blog post yesterday showing how to do PowerShell DSC with Octopus – everything from deploying DSC scripts, detecting drift, getting email notifications when drift occurs, and automatically fixing the drift:
With that in mind, I think many of the comments on this suggestion are “done”. But there might be some areas of DSC support that we still don’t do. I’d really appreciate if you could read the post, and let us know of any scenarios we’ve missed. If it looks like we’ve done nearly everything, I might close this UserVoice suggestion and we can open new, more targeted suggestions for any gaps.
Is this a duplicate of this item? https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/5923829-add-the-ability-to-add-child-steps-an-or-multiple
You can create a custom User Role for this.
Role Name: Variable manager
Description: Variable managers can view and edit variables.
Roles: VariableEdit, VariableEditUnscoped, VariableView, VariableViewUnscoped
Can't you just put two manual intervention steps in?
The lifecycle retention policies work like this. The retention policy on the package feed only applies to packages that have not been deployed.
Basically - I think this functionality already exists for you!