'Deploy a Bicep' - Move Into/Move Out breaks the step template and returns error

[RobMcCarther]

Severity

low

Version

latest

Latest Version

I could reproduce the problem in the latest build

What happened?

'Deploy a Bicep' - Move Into/Move Out of 'Run an Azure script' step breaks the 'Deploy a Bicep' step template and returns error when saving the process

This step can only run after package acquisition has been completed. The only supported option is 'After package acquisition

'

Reproduction

Either import provided process JSONdjb-configstore-process (1).json

or

• Create new process
• Add 'Run an Azure script' step
• Add 'Deploy a Bicep' step
• Move 'Deploy a Bicep' step into 'Run an Azure script' step
• save process
• notice error

Error and Stacktrace

No response

More Information

Customer who reported this experienced something similar. We weren't able to reproduce the error until "Move into/Move out"

When using inline source for the bicep template, the following error gets displayed when saving the process, even if the step does not depend on a package or have any package referenced.

Their workaround is a bit different per their scenario

The workaround seems to be that the “deploy a bicep step” must be in a group with “Run an Azure script” – even if that script step ultimately does nothing.

Workaround

initiating the process entirely from scratch New 'Deploy a Bicep' step New 'Run an Azure script' step no child steps

[michelle-luana]

The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future. We prioritize issues based on the number of people affected, the impact type, and available workarounds. If you’ve encountered this issue and haven’t informed our support team, please email support@octopus.com. Knowing how many people this issue affects helps us determine its priority.