You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
fseldow
changed the title
[question]
[question] registryScopes in trust policy
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?The text was updated successfully, but these errors were encountered: