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 there value in having a config file to avoid the need to add more and more unique arguments?
Values could then be overridden with a generic "set-config" type of argument or environment variables.
This solves some of the issues around handling support for different CI/CD platforms without having Azure DevOps (etc.) specific arguments.
The text was updated successfully, but these errors were encountered:
Alternatively this could be a section in the config file for a particular application - e.g. a StackManager property. This has the advantage of not being an additional config file, but makes the configuration application specific rather than global.
Is there value in having a config file to avoid the need to add more and more unique arguments?
Values could then be overridden with a generic "set-config" type of argument or environment variables.
This solves some of the issues around handling support for different CI/CD platforms without having Azure DevOps (etc.) specific arguments.
The text was updated successfully, but these errors were encountered: