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
Currently, the pipeline CLI uses a compile time variable support. This provides an ability to work with configurations by externalizing things like CP Code.
property-manager CLI does not appear to support variables. Would it be possible to add the same functionality to this CLI as well? It would help customers who are either getting started with the automation effort or have multi-brand configurations where the order of deployment may vary and the rigidity of pipeline may not help.
The text was updated successfully, but these errors were encountered:
We have based our pipeline solely on property-manager CLI and we don't want the rigidity of pipeline for most of our configs.
it would be great if this is looked into, been inactive since 2019.
Currently, the
pipeline
CLI uses a compile time variable support. This provides an ability to work with configurations by externalizing things like CP Code.property-manager
CLI does not appear to support variables. Would it be possible to add the same functionality to this CLI as well? It would help customers who are either getting started with the automation effort or have multi-brand configurations where the order of deployment may vary and the rigidity ofpipeline
may not help.The text was updated successfully, but these errors were encountered: