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
Please fill in the fields below to submit an issue or feature request. The
more information that is provided, the better.
Description of issue or feature request:
In the basic_repo.py example when the metadata is created the target ("basic_repo.py) is used as a Targetfile with a target path set of “manual_repo/basic_repo.py”.
But then when the delegated role is created its path pattern is “*.py” which given the spec should not match to be a delegated role for that target path.
When the generated metadata files are tested with a client, one cannot fetch the target since there's no match.
Please fill in the fields below to submit an issue or feature request. The
more information that is provided, the better.
Description of issue or feature request:
In the basic_repo.py example when the metadata is created the target ("basic_repo.py) is used as a Targetfile with a target path set of “manual_repo/basic_repo.py”.
But then when the delegated role is created its path pattern is “*.py” which given the spec should not match to be a delegated role for that target path.
When the generated metadata files are tested with a client, one cannot fetch the target since there's no match.
References:
python-tuf/examples/manual_repo/basic_repo.py
Line 106 in e7cc34a
python-tuf/examples/manual_repo/basic_repo.py
Line 283 in e7cc34a
Current behavior:
A client cannot fetch the desired target file since there's no match.
Expected behavior:
A client should be able to fetch the desired target file.
The text was updated successfully, but these errors were encountered: