Skip to content
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

feat!: allow specifying capabilities to receive when authorizing #70

Merged
merged 3 commits into from
Mar 29, 2023

Conversation

alanshaw
Copy link
Member

@alanshaw alanshaw commented Mar 29, 2023

You can specify these, so the agent does not have to receive admin.

This also removes the default * capability from w3 delegation create, making the -c, --can flag non-optional.

bin.js Outdated
@@ -37,7 +37,8 @@ cli
cli.command('authorize <email>')
.alias('auth')
.example('authorize user@example.com')
.describe('Authorize this agent to interact with the w3up service with any capabilities granted to the given email.')
.describe('Authorize this agent to interact with the w3up service with capabilities granted to the given email.')
.option('-c, --can', 'One or more abilities to authorize.', '*')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer not to add a default of *. Can we add the flag separately from adding the default?
Not a hard blocker though. I asked for advice on tradeoffs

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes, will change this now...

@alanshaw alanshaw requested a review from gobengo March 29, 2023 22:21
@alanshaw alanshaw changed the title feat: allow specifying capabilities to receive when authorizing feat!: allow specifying capabilities to receive when authorizing Mar 29, 2023
@alanshaw alanshaw merged commit 40208f5 into main Mar 29, 2023
@alanshaw alanshaw deleted the feat/specify-caps-for-authorize branch March 29, 2023 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants