We’re evaluating drone for CI/CD. The approach we’d like to take is to have two separate drone servers in our staging and production clusters. The two clusters are isolated and cannot communicate with one another. We’re trying to figure out how to best setup our .drone.yaml to support running this.
For example, we’d like to have code automatically get deployed to staging when it’s merged to master. However, we don’t want the same code to be deployed in production until some user does a
drone deploy. Since there is only one .drone.yml file per repo how would we prevent that automatic deploy from happening in our production environment?