The docs recommend separate deployments for production, dev/head and test/qa but that currently isn't possible with the dscc-scripts connector command.
The easiest implementation would probably be to expose a new updateDeployment handler, similar to the updateProduction one. This could be exposed as a command such as dscc-scripts connector update_deployment {deploymentId} {description}.
Alternatively, it would be nice to be able to add custom "dsccConnector" entries in the package.json. This would probably provide a better dev experience but the implementation would need to be ironed out.
The docs recommend separate deployments for production, dev/head and test/qa but that currently isn't possible with the
dscc-scripts connector
command.The easiest implementation would probably be to expose a new
updateDeployment
handler, similar to the updateProduction one. This could be exposed as a command such asdscc-scripts connector update_deployment {deploymentId} {description}
.Alternatively, it would be nice to be able to add custom "dsccConnector" entries in the
package.json
. This would probably provide a better dev experience but the implementation would need to be ironed out.