is there a way to add a "wildcard" code location that applies to any docker image? Using ECS hybrid, I want my agent container to register a code location (using the CLI

dagster-cloud workspace add-location ...

) that applies to all images - so I can specify the

container_context

ecs secrets, env vars,

task_role_arn

etc. Otherwise users need to keep track of all these AWS ARNs each time they add a code location. When I provision my agent via AWS CDK, I have access to all of those so would like to register that info once, for all code locations. https://docs.dagster.io/dagster-cloud/deployment/agents/amazon-ecs/configuration-reference#per-location-configuration

You can set many of these fields at the deployment level, which will make them apply to all code locations: https://docs.dagster.io/dagster-cloud/deployment/agents/amazon-ecs/configuration-reference#per-deployment-configuration (the downside is that this configuration has to go in the agent task definition)

can that accept

env_vars

and

secrets

like the locations yaml?

secrets and env_vars are options, yeah - it looks like those are missing from that reference for some reason, we'll get that fixed

oh great, thanks!

https://github.com/dagster-io/dagster-cloud/blob/main/dagster-cloud/dagster_cloud/workspace/ecs/launcher.py#L137-L167 there they are

hmm, it looks like

agent_token

is plaintext in the cloudformation config and

dagster.yaml

. Is there a way to have dagster retrieve this from an AWS secret? Or can it be left out of the yaml and retrieved from an environment variable?

Both of those are possible, yeah - the only detail is you'll then need to make sure that that env var or secret is included in any tasks that the agent spins up, by setting that same secret or env_var in the secrets or env_vars options mentioned earlier

thanks