Ability to disable some standard step templates
We want to standardize on some templates that all developers can use for their deployments. That because we need to add compliance checks on all code before promoting to Production.
the 'Run custom script' built-in step is dangerous because that opens the opportunity to do more or less anything.
As an Octopus admin I want to disable some of the built in step templates.
Bill Attar commented
This will not only allow for standards, better acceptance and usage while increasing speed to market, more importantly, this will minimize risk of multiple hand offs and process integration. Putting the controls in the hands of the developers and allowing the flexibility to leverage "approved" templates is key to the success and disabling non-approved templates is the first step in achieving our goals.
Vishal More commented
Agreed, this has to be disabled or restricted to limit the scope of developers.
Agreeing with what has been stated to date. There needs to be some form of accessibility controls, this way everybody doesn't have free reign on a target resource.
Jeff Forst commented
Agreement for a limited scope of options which will enable Standards for efficient approach and support.
Rick Holler commented
Agreed, we have had a few incidents in regards to rogue scripts being run defying our standard enterprise processes.
Darren Wright commented
The ability to disable templates will allow a wider range of teams to onboard that have niche needs
Richard Barton commented
Jumping in, this is a ability that we truly need to see as well.
Agreeing on the comments already mentioned here!
Nathan Reid commented
This is a pain for us as well from an interface standpoint. When I go to add a new Step to a Project's process, I am confronted with a ton of built-in templates that we don't use. I have to scroll to the bottom of the page to pick from the only templates that we do use, which are our user-defined templates.