Version controlled project commit of Azure App Service step doesn't commit all enabled features #8731
Assignees
Labels
kind/bug
This issue represents a verified problem we are committed to solving
Comments
KennethBates
added
the
kind/bug
|
Release Note: Fix EnabledFeatures not being added for Azure App Service Step |
|
🎉 The fix for this issue has been released in:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
One report
Version
2024.2.4636
Latest Version
None
What happened?
When configuring a new Azure App Service step in a version controlled project, the first commit does not include the enabled features in the resulting deployment_process.ocl file. Furthermore, if you navigate to another step in the same process after the commit, and navigate back into the App Service step, the Commit button is activated (no changes made), and on this subsequent commit the .ocl includes the EnabledFeatures and RunOnServer entries.
After first commit:
After second commit:
Reproduction
Add an Azure App Service step to a version controlled project and commit
View the deployment_process.ocl file
Navigate away from, and back to the App Service Step
Commit again
View the deployment_process.ocl file once again
Error and Stacktrace
No response
More Information
Internal report (private): https://octopus.zendesk.com/agent/tickets/178950
Workaround
No response
The text was updated successfully, but these errors were encountered: