metadata API: avoid raising securesystemslib exceptions #1646
Labels
1.0.0 blockers
To be addressed before 1.0.0 release
backlog
Issues to address with priority for current development goals
discussion
Discussions related to the design, implementation and operation of the project
Milestone
I think Metadata API should not require its users to import securesystemlib exceptions to be able to call Metadata API methods, it just seems weird -- as a user of TUF I am not necessarily directly using securesystemslib at all, yet I need to handle exceptions from it
Current behavior:
sign(), from_file() and to_file() are documented to raise these exceptions
Expected behavior:
I should only need to import modules from tuf to be able to handle tuf exceptions. This could mean either
verify_delegate()
doesThe text was updated successfully, but these errors were encountered: