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

Scope Map: Built-in scope-map that can pull & read tags #690

Closed
gldraphael opened this issue Apr 14, 2023 · 4 comments
Closed

Scope Map: Built-in scope-map that can pull & read tags #690

gldraphael opened this issue Apr 14, 2023 · 4 comments

Comments

@gldraphael
Copy link

What is the problem you're trying to solve
Make it easy for fluxcd to be able to pull any image/chart from an ACR.

The problem right now: _repositories_pull only allows pull operations. fluxcd like tools require you to also be able to read tags which needs metadata/read in addition to content/read.

Describe the solution you'd like

Option A: Add a new built-in scope-map repositories_pull_read or something similar, that can pull and read any repository.
Option B: Add support for a * wildcard for user-defined respository scope-maps so that users can create a scope-map with any permission combination as they'd like.

@gldraphael gldraphael changed the title Scope Map: Built-in scope-map Scope Map: Built-in scope-map that can pull & read tags Apr 14, 2023
@sajayantony
Copy link
Contributor

/cc @johnsonshi

@johnsonshi
Copy link
Contributor

Yes indeed. The built in scope map only assigns content_read and not metadata_read, which means they can pull but not list.

image

image

Creating a custom scope map that has both content_read and metadata_read is limited by the fact that you need to list every repo.

I hear you and see the validity of option A as without it, there's no way to have a scope map that encompasses all repos, and allows pulls and listing. Let me do some further investigation. Thanks

@johnsonshi johnsonshi self-assigned this Aug 9, 2023
@github-actions
Copy link

github-actions bot commented Oct 9, 2023

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Oct 9, 2023
Copy link

github-actions bot commented Nov 8, 2023

This issue was closed because it has been stalled for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants