User Roles in Apollo Studio - Lock down API keys about apollo-studio-community

[daniman]

Woohoo, glad you've enjoyed the updates @setchy! I definitely agree about having API keys match to variants in the future, but we can make a new ticket for that. I'm going to close this one for now.

For reference, Graph Roles, Protected Variants, and Roles for Graph API keys are all now available in Studio Enterprise: https://www.apollographql.com/blog/graphql-roles-and-protected-variants/

[tvvignesh]

Hi. I had raised this already here: apollographql/apollo-server#3734 and had also sent a note to the support team. Looks like this is on their radar and they are working on it.

[daniman]

We've outlined a plan that will give a lot more control to API keys for graphs by allowing you to both set a role for those keys, and set certain variants as protected that we'd love to get your feedback on: https://github.com/apollographql/apollo-studio-community/blob/main/preview-docs/GraphRoles.md

[setchy]

Today is the day 🎉

[setchy]

Really liking the updates @daniman. The new roles for users and API Keys is great, protected variants and graph visibility are all much welcome at my organization.

Like the OP, it'd be great if in a future enhancement we could also assign a graph variant to an API Key, so that we can have separate API Keys dedicated for each variant (or environment as our use-case is). We use this practice for our secret-based tokens

[setchy]

@daniman isn't the original issue / feature request still unresolved though? #10 (comment)

Happy to raise a new ticket if you'd prefer

[setchy]

Raise #53