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

[question] registryScopes in trust policy #278

Open
fseldow opened this issue Sep 4, 2023 · 1 comment
Open

[question] registryScopes in trust policy #278

fseldow opened this issue Sep 4, 2023 · 1 comment
Labels
duplicate This issue or pull request already exists
Milestone

Comments

@fseldow
Copy link

fseldow commented Sep 4, 2023

Hi team,
i am reading the structure of trust policy properties, might have one question about registryScopes
https://github.com/notaryproject/specifications/blob/main/specs/trust-store-trust-policy.md#trust-policy-properties

The article said The scope field supports filtering based on fully qualified repository URI ${registry-name}/${namespace}/${repository-name}. I have one scenario that all my images from certain registry or namespace are signed by same cert. So i would like to input ${registry-name}/* or ${registry-name}/${namespace}/*. However, it does not support according to the doc. So if possible, may i know the reason that we have to input the full url for registry scopes?

@fseldow fseldow changed the title [question] [question] registryScopes in trust policy Sep 4, 2023
@yizha1 yizha1 added this to the future milestone Sep 12, 2023
@yizha1 yizha1 added the duplicate This issue or pull request already exists label Mar 5, 2024
@yizha1
Copy link
Contributor

yizha1 commented Mar 5, 2024

Duplicated with issue #289

@yizha1 yizha1 modified the milestones: Future, 1.2.0 Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
Status: Todo
Development

No branches or pull requests

2 participants