docs(examples/minimal): pin real root key, align enforcement mode, and add unit test (fixes #218) - #220
Conversation
…ion and config validation
|
Thanks for this, @aipd506. Closing it for now, and it is not about the change itself. This repository asks first-time contributors to be vouched by a maintainer before opening a pull request. That is because agent-written contributions are easy to produce and expensive to review, and we would rather talk to you first than review something neither of us can explain. To get vouched: open an issue saying what you want to change and why, in your own words. A maintainer will reply, and add you with See CONTRIBUTING.md for the detail. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Fixes #218
Summary of Changes
This PR aligns
examples/minimal/README.mdwith the committed configuration and adds test coverage for the minimal example commands:examples/minimal/README.mdCorrections:<trusted-root-issuer-hex>placeholder on line 14 with the actual pinned trusted root issuer public key (eda38c446da3db3eba68852ca9869260c36badd48b2cab16ec8d8faf607eb162) defined inca2a-config.yaml.ca2a-config.yamlon line 7 from(software-only, advisory)to(software-only, enforcing)to match the configuredenforcement_mode: enforcing.New Unit Test Suite (
tests/unit/test_example_minimal.py):ca2a verify-chainagainstexamples/minimal/chain.jsonwith the pinned root key, assertingverified: True,hops: 3, andleaf_scope: ["cap:read"].ca2a validate-configagainstexamples/minimal/ca2a-config.yaml, asserting exit code 0 and outputok: provider=software-only enforcement=enforcing.Verification