Hi. I have a question about agent in hybrid. I am currently trying to do the following in branch-deployment

- Build agent in multiple environments.
  - For example, a dev environment and a staging environment.
    - Specific branch runs in dev environment
    - Specific branch runs in staging environment

I was thinking that I could do the above by using different TOKENs, but is this impossible? The behavior I can confirm now is:

1. create branch-deployment
  - Use the token for dev
2. Add code-location
  - Use the token for dev

If you do the above, the code-location server will be built through the agent in all environments (dev and staging). Please let me know if there is something I am not communicating. Your answer would be greatly appreciated.

Hi, right now it’s not possible for branch deployments to be associated with a specific deployment (staging vs dev) instead you just have an agent that’s responsible for every branch deployment in your organization.

Thank you very much. Understood. I am waiting for this feature to be released. We would like to have two organizations to avoid this problem. So we would like to change the name of full-deployment, is this possible? (I can't find the corresponding function in the documentation or dagster-cloud CLI)

We can change it for you if you give us the name of your organization and the new deployment name

It will be very helpful. The organization name is "techtouch-dev". Could you please change the deployment name from "prod" to "staging"?

Hey @taker multiple deployments is a Dagster Cloud Ent feature, teams are only supposed to have a single organization. Our sales org can help determine the best way to support your use case

Hi. Yes, I understand Ent, but we probably can't adopt it due to the cost (I don't know the actual cost, but we are in a situation where we don't have the budget to pay many costs). .