@brandontruong Right now we are using a hack:
We define a gen-2 resource in our convox.yml which is used for most environments. Then we have our production resource as a gen-1 resource, and during deployment to production, or CI job rewrites our convox.yml file to remove the gen-2 definition.
It’s particularly fragile, because if someone tries to deploy to production manually, it will end up creating a new gen-2 resource and sending all traffic to it. Haven’t found a solution to this yet. I asked about adding a option to disable gen-2 resources via env vars, but no response.
I’m still open to other suggestions on how to solve this.