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
{{ message }}
Repository navigation
KeyError while trying to delegate to new role with CLI #1114
The new role is added to the target.json and also snapshot and timestamp updated, but there is no myrole.json created from the delegate command. This problem surfaces at the last command, it tries to load the repo again (for signing) and fails because it can not find metadata for the delegated role... After that all commands immediately fail at loading the repo.
Expected behavior:
That it creates a myrole.json and signs it with mykey.
Additional info:
I have also gone through the Advanced Tutorial and this works fine (creates the role metadata) running the functions from repository_tool.py directly.
Looking through the code I am not sure how it is intended to work with repo.py. Should the sign step create the missing role metadata instead? So signing before adding the delegation? But that does not work either:
Closing this issue as it was filed against (what is now known as) the legacy codebase: issue seems to not be relevant anymore. Please re-open or file a new issue if you feel that the issue is revelant to current python-tuf.
Note that we do not provide a repository CLI tool at the moment: examples/repo_example shows how to implement repository workflows with current codebase.
More details
Current source code (and upcoming 1.0 release) only contains the modern components
a low-level Metadata API (tuf.api) and
tuf.ngclient that implements the client workflow,
Legacy components (e.g. tuf.client, tuf.repository_tool, tuf.repository_lib as well as the repo and client scripts) are no longer included. See announcement and API reference for more details.
Activity
lukpueh commentedon Aug 21, 2020
Thanks for reporting the issue, @Jakeler! I'm adding this to the collection of known cli tool issues: #881
jku commentedon Feb 16, 2022
Closing this issue as it was filed against (what is now known as) the legacy codebase: issue seems to not be relevant anymore. Please re-open or file a new issue if you feel that the issue is revelant to current python-tuf.
Note that we do not provide a repository CLI tool at the moment: examples/repo_example shows how to implement repository workflows with current codebase.
More details
Current source code (and upcoming 1.0 release) only contains the modern components
tuf.api) andtuf.ngclientthat implements the client workflow,Legacy components (e.g. tuf.client, tuf.repository_tool, tuf.repository_lib as well as the repo and client scripts) are no longer included. See announcement and API reference for more details.