You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
While it's possible to initialize a new solution with any number of deployment steps. Adding new steps or removing steps after the fact is not currently handled completely. Pipelines aren't removed if a step gets deleted, which is okay, not ideal but if the pipeline isn't going to be used it just sits unused in the AzDO project. However, adding new steps does require, today, that the Solution Branch be committed to directly which isn't possible when there is a Branch policy restricting direct updates.
Describe the solution you'd like
Adding new steps should allow for the new pipeline template and the associated pipeline to be created on the subsequent commit after a new step is added. Need to think through the best implementation of this given how pipeline templates are generated and the state of the Solution branch once it exists.
AB#1418
The text was updated successfully, but these errors were encountered:
@mikefactorial This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.
Is your feature request related to a problem? Please describe.
While it's possible to initialize a new solution with any number of deployment steps. Adding new steps or removing steps after the fact is not currently handled completely. Pipelines aren't removed if a step gets deleted, which is okay, not ideal but if the pipeline isn't going to be used it just sits unused in the AzDO project. However, adding new steps does require, today, that the Solution Branch be committed to directly which isn't possible when there is a Branch policy restricting direct updates.
Describe the solution you'd like
Adding new steps should allow for the new pipeline template and the associated pipeline to be created on the subsequent commit after a new step is added. Need to think through the best implementation of this given how pipeline templates are generated and the state of the Solution branch once it exists.
AB#1418
The text was updated successfully, but these errors were encountered: