Enhance clab tools cert sign to generate node certificates for topology nodes
#2851
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds topology-based certificate generation to the
clab tools cert signcommand, allowing users to generate certificates for all nodes in a topology file that havecertificate.issue=trueconfigured.Problem
Previously, the
clab tools cert signcommand could only generate individual certificates by manually specifying certificate parameters. Users had to run the command multiple times for each node in their topology, manually providing hosts, common names, and other certificate attributes.Solution
Added a new
--topologyflag that:certificate.issue=truerouter1)clab-mylab-router1)router1.mylab.io).tls/nodename/)Usage
Example
Given a topology file:
The command generates a certificate for
router1with SANs:router1,clab-mylab-router1,router1.mylab.io,router1.lab.example.com,172.20.20.10, and skipsrouter2.Implementation Details
Fixes #[issue_number]
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.