Currently, mule-deploy uses muleDeploy.env to select the target environment and also set the "env" CH property. We'd like to enhance environment selection and property generation to support the following scenarios:
Default (Single env value being passed in is used as application env property and deployment target in runtime manager)
Option to specify these 2 values separately each as their own property
Option to configure what the application property name is
Currently, mule-deploy uses muleDeploy.env to select the target environment and also set the "env" CH property. We'd like to enhance environment selection and property generation to support the following scenarios: