GraphQL secretCreate Mutation
I have a runpod teams account, and want to programatically add secrets to the account (https://docs.runpod.io/sdks/graphql/manage-pod-templates#create-a-secret). I'll then be using these secrets in my Pod. This API works when I use my personal key, however, when I use the team API key, it gives me the following error: Not authorized. Missing required scope(s): TEAM_ADMIN, TEAM_DEV
My API key already has all full access, and running the "myself" query shows that I do have the "admin" role in "teamScopes". What exactly am I missing?
Manage Templates | RunPod Documentation
Create, modify, and delete templates in RunPod using GraphQL API with various parameters for container disk size, Docker arguments, environment variables, and more.
10 Replies
@zacksparrow how do scopes for secret mutations work?
Hi. Any updates on this?
@zacksparrow any assistance on this would be appreciated.
Hey sorry, yeah so when you say you have your personal api key, where is the team api key coming from? Are you the owner of the team?
Yea, I'm one of the owners of the team account
What I meant was that I tested the above mutation with my personal api key and it worked fine for my personal account
however, it doesn't work when i use the team api key in the team account
If you run the myself query with the team api key, what do you get back?
I get the team details and the teamScopes key has the following value:
"teamScopes": {
"role": "admin"
}
I only queried for the team related keys. Anything else I should be looking out for?
The key itself is not a "legacy" key. It has "All" access.
Gotcha, and who generated the team api key?
I did
For context, I was given the admin access afterwards
The original owner was someone else
however, I generated the key after the "admin" access
Also, the other mutations work fine. I have another mutation which updates one of my existing pods. It's only an issue with the secretCreate mutation
Let me look into this for you
Sure, thanks.