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

Command line builder for FCCs #129

Closed
bostrt opened this issue Aug 20, 2020 · 1 comment
Closed

Command line builder for FCCs #129

bostrt opened this issue Aug 20, 2020 · 1 comment

Comments

@bostrt
Copy link

bostrt commented Aug 20, 2020

NOTE: This is partially duplicated work now that I've learned about fcct local files: coreos/fedora-coreos-docs#163

I've been working on a command line builder for FCCs, called fccb. Source is here: https://github.com/bostrt/fccb. My use case is for building FCCs from files that are in Git that I'd rather keep there for various reasons, including:

  • Better version tracking and potentially easier merges then keeping in an FCC Yaml
  • Easier to use linting tools on content outside of YAML (e.g. https://github.com/koalaman/shellcheck)
  • Syntax highlighters function better when code isn't embedded in YAML

A side use-case is that command line interaction is sometimes more fun than editing YAML directly.

I'm curious if anyone else in the Fedora CoreOS community might find fccb useful and if so, do you think a standalone tool is appropriate or if I should submit a PR to fcct?

Below are some examples that might better explain what this tool does exactly. BTW, Its output is FCC that can be piped directly into fcct. I didn't go directly to Ignition configs since fcct handles that already.

$ fccb add file test.fcc mymotd.txt -p /etc/motd | fcct -p # Add motd and instantly transpile
$ fccb add unit test.fcc -f test.service -d test.service.d/ # Add Systemd service unit and some drop-ins
$ fccb add user test.fcc -n bostrt -G floppy -s /bin/ksh # Add user in floppy and uses KSH
...
@bgilbert
Copy link
Contributor

I think this isn't the direction we'd want to go for Butane, since it could encourage folks to keep their canonical configuration in their bash history (or a random shell script or Makefile) rather than in a proper config. As you say, local files and storage.trees entries should help with your use case.

I'll close this out. Thanks for the pointer!

@bgilbert bgilbert closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants