You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's unusual for us to require something to be released before the GitHub issue is done. So I changed the definition of done and added bottlerocket-os/bottlerocket#3187
qemu-x86-console-bootconfig.data - used by start-local-vm
I'm not sure what the fate of the other content in tools will be long-term; maybe it all gets relocated to a "contrib" repo of some sort, or rewritten as twoliter helper commands (e.g. twoliter-start-local-vm can be a local helper script invoked by twoliter start-local-vm ...), which can embed the data file as a base64 string or whatever.
I'm not sure what the fate of the other content in tools
Most of the rest of the tools will go to the twoliter GitHub repository and be "embedded" in with the twoliter CLI. But you're right, I haven't thought about the "workflow" and "helper" type scripts. It's possible those conveniences could also be added to twoliter.
Description
Add the following things to the
bottlerocket-sdk
:cargo make
cargo deny
docker
(the CLI only, not the daemon)Definition of Done
When the above items have been added to the SDK.
Depends on:
Related to bottlerocket-os/bottlerocket#2669
The text was updated successfully, but these errors were encountered: