```locations: - location_name: data-eng-pipeline...
# ask-community
a
Copy code
locations:
  - location_name: data-eng-pipeline
    code_source:
      package_name: hooli_data_eng
    build:
      directory: ./
      registry:  <http://764506304434.dkr.ecr.us-west-2.amazonaws.com/hooli-data-science-prod|764506304434.dkr.ecr.us-west-2.amazonaws.com/hooli-data-science-prod>
Hello, how do I go about adding more projects via Definitions? I'm trying to transition from using repository. Would I just add another project with a top level definition to this yaml?
Copy code
locations:
  - location_name: data-eng-pipeline
    code_source:
      package_name: hooli_data_eng
    build:
      directory: ./
      registry:  <http://764506304434.dkr.ecr.us-west-2.amazonaws.com/hooli-data-science-prod|764506304434.dkr.ecr.us-west-2.amazonaws.com/hooli-data-science-prod>

  - location_name: finance-pipeline
    code_source:
      package_name: finance_eng
    build:
      directory: ./
      registry:  <http://764506304434.dkr.ecr.us-west-2.amazonaws.com/finance-prod|764506304434.dkr.ecr.us-west-2.amazonaws.com/finance-prod>
Would the above be correct?
j
i think so - this section of the docs should be helpful https://docs.dagster.io/concepts/code-locations/workspace-files#loading-multiple-repositories note that it only applies to repositories, though
a
Is loading-multiple-repositories going to be deprecated in the near future? I don't currently see a benefit of switching over to Definitions.
j
it won’t be deprecated until we have a feature parity alternative, and that likely won’t happen for the foreseeable future
👍 1