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

feature: Improve UX when APIBinding contains pending permission claims #2789

Open
1 task done
lionelvillard opened this issue Feb 15, 2023 · 0 comments
Open
1 task done
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@lionelvillard
Copy link
Contributor

lionelvillard commented Feb 15, 2023

Feature Description

I'm always frustrated when I create an APIBinding there is no clear indication there are pending claims and that there is no easy way to accept all claims.

Proposed Solution

  • Add a new "Pending" claim state
  • Print current status on claims when entering a workspace (already supported)
  • Print message when kcp bind apiexport has permission claims
  • For accepting claims:
    • at binding time: provide CLI flags (--accept-all-claims, --accept-claim GR [identityhash], --interactive)
    • after binding: provide CLI command (eg. kcp claims accept|reject [GR [identityhash]] [--all] [--interactive])

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

@lionelvillard lionelvillard added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 15, 2023
@ncdc ncdc added this to kcp Feb 15, 2023
@github-project-automation github-project-automation bot moved this to New in kcp Feb 15, 2023
@lionelvillard lionelvillard changed the title feature: feature: Improve UX when APIBinding contains pending permission claims Feb 15, 2023
@mjudeikis mjudeikis moved this from New to Backlog in kcp Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Backlog
Development

No branches or pull requests

1 participant