automate-setup #7
Conversation
|
|
||
| Input `name`, `password`, `email`, and `access_token`. The first three are as described in regular user create API. The `access_token` is unique in that it is the scope of permissions to create an access token for this user. | ||
|
|
||
| The scope may be one or more of the following in a single string separated by spaces: |
There was a problem hiding this comment.
Is there a need for scope? As I understand the idea is to initialize the admin user which can later be used to initialize other users. If someone creates a user with user:read scope only then you'll have to manually create the admin user.
There was a problem hiding this comment.
I originally just had access_token: true which would then have all permissions added to the token. I'm can't think of a reason not to give all permissions.
There was a problem hiding this comment.
I don't think it's strictly necessary to include permission scope, but I think it could be useful to have as an option. Maybe we can default to all true and if someone provides scope we can limit it to that.
| "username": "admin", | ||
| "email": "[email protected]", | ||
| "encrypted_password": "QmPdFZdvfjA0JvnNPEdIZhtKzBjQmXgqQvabEXDYNL0ucHmUXhlPEUzgMThMEN6V", | ||
| "access_token": "6WQPRJZ5HHC6G8L2T5TM9MCGBSIX0AFJXKVVDYOH", |
There was a problem hiding this comment.
Is this an oauth token. How is this going to be generated? You would need to also create an organization with an application to do so. Afaik you need both in order to generate an application token that would give you access to Quay's api.
There was a problem hiding this comment.
Yes, the user is the organization. We don't enable this through quay api right now, but I've confirmed it works so no org needs to be created.
No description provided.