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
Long ago in the reference implementation, creating a delegation was equivalent to creating a role. That is not the case, however, as a delegation can point to an existing role. Accordingly, the Targets class method 'delegate()' creates a role. We made some changes previously to allow delegate() to work even if the role to delegate to already exists, but the code is still confusing in this regard. It's probably best to separate role creation from delegation to that role.
The text was updated successfully, but these errors were encountered:
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.
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.
Related to #660 .
Long ago in the reference implementation, creating a delegation was equivalent to creating a role. That is not the case, however, as a delegation can point to an existing role. Accordingly, the Targets class method 'delegate()' creates a role. We made some changes previously to allow delegate() to work even if the role to delegate to already exists, but the code is still confusing in this regard. It's probably best to separate role creation from delegation to that role.
The text was updated successfully, but these errors were encountered: