Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move schnauzer to the bottlerocket-settings-sdk #4167

Open
cbgbt opened this issue Aug 27, 2024 · 1 comment
Open

Move schnauzer to the bottlerocket-settings-sdk #4167

cbgbt opened this issue Aug 27, 2024 · 1 comment
Labels
area/core Issues core to the OS (variant independent) area/out-of-tree-builds Related to the efforts of making it easy to create builds outside of the main Bottlerocket repo type/enhancement New feature or request

Comments

@cbgbt
Copy link
Contributor

cbgbt commented Aug 27, 2024

What I'd like:
Configuration templates that are rendered by Bottlerocket's settings API are rendered using the schnauzer utility. The source code canonically lives in bottlerocket-core-kit; however, Bottlerocket migrations currently use schnauzer to perform migrations on template-based settings generators.

We need to consider some mechanism for sharing schnauzer as a library between this repository and core-kit. One potential solution would be to move schnauzer to the bottlerocket-settings-sdk.

@cbgbt cbgbt added type/enhancement New feature or request status/needs-triage Pending triage or re-evaluation area/core Issues core to the OS (variant independent) area/out-of-tree-builds Related to the efforts of making it easy to create builds outside of the main Bottlerocket repo and removed status/needs-triage Pending triage or re-evaluation labels Aug 27, 2024
@cbgbt
Copy link
Contributor Author

cbgbt commented Aug 27, 2024

One challenge here is that schnauzer depends on apiclient in order to fetch the settings needed to render a template. We may similarly need to publish Bottlerocket's apiclient as a standalone crate.

The apiclient is settings-model-agnostic; however, we would need to be more cautious regarding API client/server compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core Issues core to the OS (variant independent) area/out-of-tree-builds Related to the efforts of making it easy to create builds outside of the main Bottlerocket repo type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant