Repository navigation
Remove version strings from file names - #247
Conversation
… feature/fix-246 * 'feature/fix-246' of https://github.com/CERTCC/SSVC: add subsubsection header for tree versioning Update link to SSVC_Provision.schema.json Update link to SSVC_Computed.schema.json Update 055_decision-points_2.md (#250) Two small typo fixes (#253) Replace Utility with Automatable in Deployer tree (#248) Add detail about customization, tree sharing, and decision point scope (#242) add text to point ahead to "Information Changes over Time" bulletize list # Conflicts: # ssvc-calc/SSVC_Computed.schema.json # ssvc-calc/SSVC_Provision.schema.json
cgyarbrough
left a comment
cgyarbrough
left a comment
There was a problem hiding this comment.
I concur and approve these changes. I presume that the SSVC Provision Table would change with each customer, correct? I know there is a CISA-specific component for this run.
We include the CISA tree because we had it from helping to develop https://www.cisa.gov/ssvc-calculator (which is based on the ssvc-calc included in this repo. However, it strikes me that the default tree that loads for our calculator should probably not be the CISA-tuned one, but instead one of the ones described in the document. I'll create a separate issue to capture that. |
|
@ahouseholder & @cgyarbrough we need to establish our own tree. |
@laurie-tyz See #257 for the proposed change and #258 for the PR that implements it |
This branch was previously deployed
3 participants
resolves #246