A Community Step Template imported as a Custom Step Template will cause an error if used in a Config-as-Code deployment process before "Synchronize Community Step Templates" runs

[donnybell]

Severity

Not blocking

Version

Discovered in 2024.4.6960, likely affects all CaC Octopus versions

Latest Version

None

What happened?

A Community Step Template imported as Custom Step Template will cause an error if used in a Config-as-Code deployment process before "Synchronize Community Step Templates" runs. This is due to the import setting the version for the Custom Step Template as 0. Once the "Synchronize Community Step Templates" system task runs, the imported Custom Step Template will be associated with the Community Step Template if the name and the script are identical.

It might be worth considering automatically launching a fresh run of "Synchronize Community Step Templates" upon import in the relevant Space to prevent this.

Reproduction

1. Add a Community Step Template to a Space
2. Use the overflow menu -> Export -> Copy to Clipboard
3. Delete the Community Step Template
4. From the Step Templates page, click Import -> paste -> Save
5. Add the Step Template to a CaC deployment process
6. Force a re-run of "Synchronize Community Step Templates"
7. An error should appear similar to: Action Template with ID ActionTemplates-XXXX and version v0 specified in the OCL was not found.

Error and Stacktrace

No response

More Information

No response

Workaround

If your process is already affected. You will need to update the version number referenced in Git.

If you want to keep the Step Template as a Custom Step Template:

When importing, add " - custom" or something to the name or change the name entirely. You can edit the paste directly before hitting save.

Example:

If you want to use the Step Template as a Community Step Template:

Keep everything the same. Before you add the Step Template to a deployment process, Force "Synchronize Community Step Templates" to re-run.

Example: