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
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 text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: