A code sample at the following URL is incorrect:

https://octopus.com/docs/runbooks/runbook-examples/routine/updating-linux#:~:text=To%20create%20a%20runbook%20to,and%20then%20click%20ADD%20STEP.

The script under step 7 of "Create the Runbook" section (CentOS/RHEL) should be updated to reflect the existence of additional yum exit codes which indicate successful execution. Currently, this script does not account for exit code 100. From 'man yum':

"DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs."

This can be corrected by introducing a compound conditional as follows:

if [[ $? -ne 0 && $? -ne 100 ]]

The problem is, when you have multiple projects, is not very common that they share the same environments.

"Production" for "Project A" means a very different thing than "Production" for "Project B". Different machines or group of machines in case of a web-farm, for example (Deployment Targets).

Currently, the only way that this could be solved, is by creating custom environments per-project (ProjectAProduction, ProjectBProduction), as discussed in the support site (http://help.octopusdeploy.com/discussions/questions/10999-environments-per-project)

But this is more a workaround than an actual solution. The home page Dashboard gets really messy, because you can't filter environments for certain projects.

I think that configuring environments per project could be something worth for you guys to analyze.

Ensuring certificates for the OD server are up to date are a little annoying. It would be awesome if the OD server could support renewing it's own hosting certificate with Let's Encrypt.

I've had a stab at creating custom steps to do this. The main issue is domain validation (DV). DNS validation often requires manual intervention and OD server controls http (see discussion at https://community.letsencrypt.org/t/domain-validation/26512 ).

The only way I see this really progressing forward is if OD server supports Let's Encrypt in the server as a maintanence task as it would be able to respond to http DV requests. It could then get the new certificate issued after successful http DV and update its https binding to use the new certificate.

I would also like to have the same thumbprint configured in the registry of the server for RDP access. An option to support this as part of the certificate renewal would be great.

The variables view is very basic and it generally needs improving since it quickly gets hard to use when you begin adding lots of variables.

1. You have to add the same variable name for multiple environments and the ordering of environments is not the same. This is error prone and makes the list hard to parse.
2. There is no description for variables so you need to add very long names sometimes. This has already been covered, but I added it for completeness. See https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6079578-enhance-the-variable-maintenance-screen-with-varia
3. There can be different types of variables which are changed for different reasons. It would be great to have a category concept to group them with.
4. For very large numbers of variables it would be great with a search box which filters the variables as you type. It should also search in the description.

See the following mockup for an example:
http://s288.photobucket.com/user/withoutprecedence/media/OD%20variables%20view_zpsfesl13ke.png.html

It would be nice to have the option to reorder step template parameters just like one can reorder the environments.

Right now step template parameters are displayed in the same order they have been created. If one does not pay attention to the order at that time then I can only export the json string, change the parameter order, delete the step template and reimport my modified version.

Also if a step template is modified at a later time and parameters are added or removed, then the order of the parameters might be now incorrect. Imagine that I want to put parameters into logical groups indicated by the order they appear in the step form.

So I think a similar drag & drop functionality would be very nice.

It would be really helpful if I could target a set of tenant machines in the script console.

Sometimes I want to run a script on the machines allocated to a specific tenant, but right now I need to pick those machines manually. That's OK if all my tenanted machines are named using a convention including the tenant name, but with the public cloud that often isn't the case.

What would be lovely is if I could choose one or more tenants and have the script console run the script across all the machines those tenants are allocated to.

Likewise it would be nice if this could extend to tenant tags using the same logic: find the list of tenants matching this tag query, and then run the script against all machines allocated to those tenants.

Source (private link): https://secure.helpscout.net/conversation/347634339/0/