-
Notifications
You must be signed in to change notification settings - Fork 36
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 provision
script to CLI
#603
Comments
another note on the cli for this: in the past we have used spf13/cobra, but we are making a conscious effort to replace that and use urfave/cli instead |
Noted, I saw that discussion in the past (I think it was driven by PS: Noticed the repo link was private, just changed that to public. |
10% that, 90% i just don't like cobra 😂 |
This issue is stale because it has been open 60 days with no activity. |
This issue was closed because it has been stalled for 365 days with no activity. |
Describe the solution you'd like:
As of now, the
provision.sh
does most of the heavy lifting to setup Flintlock and dependencies (Firecracker, containerd, networking etc) to a host machine. The idea is to port this script to a CLI.Why do you want this feature:
Even though the script works great, having this feature in a CLI would make for a better developer experience, and probably easier to maintain and extend.
I believe there's still the discussion of whether this should be part of the
flintlock
CLI or maybe of aclient
(similar to what was discussed here), I ended up creating a repo to start working on this, very early stages still. We can later decide where we want that to live. If anyone else also wants to work on this, we could easily just move that to a branch insidefl
orflintlock
though.About the code itself, there's also the decision to use
exec.Command
vs adding more dependencies (for example, DIgitalOcean maintains a SDK to interact withlibvirtd
), just something to consider.The text was updated successfully, but these errors were encountered: