add endpoint to return repository location names from DagsterGraphQLClient

[dagsir]

Issue from the Dagster Slack

This issue was generated from the slack conversation at: https://dagster.slack.com/archives/C01U954MEER/p1668525617649349?thread_ts=1668525617.649349&cid=C01U954MEER

---

Conversation excerpt

U02PY9R25PT: Hey, we’d like to create a sensor that reloads the workspace upon some event (we have dynamic repositories to generate jobs).
What would be the best way to invoke the reload operation through the daemon?
I know it can be done using DagsterGraphQLClient.reload_repository_location but I have to get somehow Dagit’s IP and all the repository locations. Is there a way to extract these from the sensor context? (maybe from the DagsterInstance)?
If there’s another way (not using GraphQL and Dagit) that could be great too!
Thanks!
U028M11QNDD: Hi Roei, out of curiosity, why do you need Dagit's IP? It seems that reload_repository_location accepts a repository location name, so maybe we can just add an endpoint to fetch the repository location names
U02PY9R25PT: Hi <@U028M11QNDD> , as that’s a GraphQL request (through the Python client) it needs a Dagit host and port to send the requests to (the GraphQL endpoint). It’d be awesome to get that information out of the box 😄
U028M11QNDD: Unfortunately, to my knowledge there is no way to programmatically fetch Dagit's IP and the repository locations via the sensor context. I think the easiest way may still be to use DagsterGraphQLClient. I can file a feature request to add an endpoint on DagsterGraphQLClient that returns the repository locations though
U028M11QNDD: <@U018K0G2Y85> issue add endpoint to return repository location names from DagsterGraphQLClient

---

Message from the maintainers:

Do you care about this too? Give it a 👍. We factor engagement into prioritization.