hasura / hasura/graphql-engine

CLI: Local dev with cloud only workflow fails

Open
#10,364 0 comments 0 reactions 0 assignees View on GitHub
c/v3-cli ddnbugbounty-2024 k/v3-bug p/high
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### What is the current behaviour?
Local dev without local dev is currently not possible? Currently ddn connector-link update --add-all-resources, calls the connector schema URL to get the NDC schema and generate the models. However, the cloud connector URL's are not accessible to the public internet and hence this command doesn't succeed.

We cannot track models via the LSP either

### What is the expected behaviour?
CLI should have an option to generate all the models and commands (behaviour of --add-all-resources) from connector-link.hml that's generated during ddn connector build

### How to reproduce the issue?

1. Do a cloud connector build
2. Use the generated cloud connector URL's in the .env files in the connector-link update

### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords

Contributor guide

Open the contributing guide

Research direction

Start with `ddn connector-link update --add-all-resources` and the `connector-link.hml` produced by `ddn connector build`; compare how the command currently obtains the NDC schema with the local artifact. Done means cloud-only local development can generate all models and commands without accessing cloud connector URLs, and the LSP can track those models.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.