-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update NETWORK_SUBGRAPH_MAINNET & add api-key
to CLI
#1760
Conversation
|
Deploying graph-tooling with Cloudflare Pages
|
After looking into it I feel like the proper way would be to use
BTW in Studio it actually tells you to use I propose returning What do you think @alex-pakalniskis @0237h @DenisCarriere ? |
Good point, I think it makes sense to have all API keys managed from a single command like |
@YaroShkvorets I'm wondering, aren't those technically the same keys ? @DenisCarriere qualifies the gateway key as just the studio API key and from what I understand it is also treated as such on the Explorer (see pic) |
These are different keys. |
|
Added version extraction from network subgraph for an existing subgraph to properly update metadata. |
…#1760) * update NETWORK_SUBGRAPH_MAINNET & add `api-key` to CLI * Fail publish if missing API key with Subgraph ID * get version from network subgraph --------- Co-authored-by: Etienne Donneger <etienne@pinax.network> Co-authored-by: YaroShkvorets <shkvorets@gmail.com>
fixes: #1753
CLI changes
--api-key
: The API key to use for the Subgraph queries.Example
Website changes
NETWORK_SUBGRAPH_MAINNET
with https://gateway.thegraph.com/api/{api-key}/subgraphs/id/DZz4kDTdmzWLWsV373w2bSmoar3umKKH9y82SUKr5qmpNETWORK_SUBGRAPH_SEPOLIA
with https://gateway.thegraph.com/api/{api-key}/subgraphs/id/3xQHhMudr1oh69ut36G2mbzpYmYxwqCeU6wwqyCDCnqV?apiKey=<STUDIO API KEY>
apiKey
is not provided in URL params