Automated Bootstrapping for Derived Catalogs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files or tests are named. Start by inspecting the existing extend/import implementation and the grcli command structure to understand catalog parsing, validation, and generation. Done should include a defined init workflow that validates the parent URI and Gemara data, records the parent version, supports selecting controls, and emits a child-catalog boilerplate.
Written by the indexing model from the issue text.
Description
Description
Currently, the Gemara spec supports creating a catalog based on another (inheritance/selection - extend/import), but the process is manual for creation. Based on the ORBIT Working Group discussion on 2026-05-07, there seems to be a growing need to create layered catalogs on top of the OSPS Baseline.
We need a bootstrapping mechanism in the SDK that supports a user to programmatically generate a "child" catalog from a "parent" catalog.
Proposed Workflow
- User runs a command like
grcli init --from [Parent-Catalog-URI]. - User selects whether they want to inherit all controls or a specific subset.
- The tool generates a new Gemara catalog file with metadata already populated.
Success Criteria
- The bootstrapping logic ensures the parent URI is reachable and valid Gemara.
- The metadata is automatically linked tso the child catalog knows which version of the parent it was created from.
- Provide a boilerplate structure for the "new" controls to be added.
Context
- Specifically addressed the friction point of keeping the Baseline clean while allowing specialized extensions.
- This functionality would be supported the Gemara Hub initiative by making it easier to publish derivative works.
- Dominant language
- Go
- Stars
- 0
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from gemaraproj/grcli
-
grcli cat has a confusing error if you are testing different optionsPossibly taken @PaarthPandey10 claimed this 17 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
gemaraproj/grcli#10 · 1 comment · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
gemaraproj/grcli#9 ·
All issues in gemaraproj/grcli
Similar issues
-
Pin and verify Security Insights schema in lintinsights targetPossibly taken @imshubham22apr-gif claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gemaraproj/gemara#618 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
a2aproject/a2a-go#597 ·
Maintainers usually reply within 1 day
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPossibly taken @patelshivani2283-lab claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day