The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

would it be possible to unify the locations.yaml between the typical `dagster-cloud workspace sync` format and the GitHub actions format?

CLI/Cloud format
```locations:
  - location_name: ${INSTANCE_NAME}
    image: ${GCP_REGION}-docker.pkg.dev/${GCP_PROJECT_ID}/${IMAGE_NAME}/${IMAGE_NAME}:latest
    working_directory: /root/app
    code_source:
      package_name: teamster.local
    container_context:
      k8s:
        env_secrets: 
          - ${INSTANCE_NAME}```


GH Action format:
```locations:
  ${INSTANCE_NAME}:
    build: ../
    registry: ${GCP_REGION}-docker.pkg.dev/${GCP_PROJECT_ID}/${IMAGE_NAME}/${IMAGE_NAME}
    working_directory: /root/app
    package_name: teamster.local
    container_context:
      k8s:
        env_secrets:
          - ${INSTANCE_NAME}```


I'm talking specifically about the first child node

on the CLI it's a list, on the GH Action, it's a dict

yeah, this is something I've been wanting to do so that the CI/CD .yaml is a superset of the cloud workspace .yaml

cool, yeah I stumbled upon the difference this week when I was figuring out our CI/CD workflow