search

dagster-io / dagster

An orchestration platform for the development, production, and observation of data assets.
https://dagster.io
Apache License 2.0
11.26k stars 1.42k forks source link

dagster_graphql: repository_location_name and repository_name purpose not defined in docs #13165

Open LucaMD opened 1 year ago

LucaMD commented 1 year ago

What's the issue or suggestion?

see https://github.com/dagster-io/dagster/blob/master/docs/content/concepts/dagit/graphql-client.mdx

from dagster_graphql import DagsterGraphQLClientError

try: new_run_id: str = client.submit_job_execution( JOB_NAME, repository_location_name=REPO_LOCATION_NAME, repository_name=REPO_NAME, run_config={}, ) do_something_on_success(new_run_id) except DagsterGraphQLClientError as exc: do_something_with_exc(exc) raise exc

what is the purpose of repository_location_name and repository_name? This is not defined in documentation.

Additional information

see above

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

danielgafni commented 7 months ago

I believe repository_name should be set to __repository__, while repository_location_name should take the code location name

danielgafni commented 7 months ago

@erinkcochran87 should this be reflected in docs?