`simp config` should have an express installation method


It's entirely possible to run through `simp config` and do nothing except hit <Enter> on repeat and have it generate the appropriate data files that a user needs. There should be an option that does this and auto-fills every response in a non-interactive way. Many users are interested in trying SIMP for the first time and this would allow them a way to get started as quickly as possible.

Acceptance Criteria



Chris Tessmer
August 30, 2019, 8:40 PM

: Are you looking for the -f option, a.ka., --force-defaults / --non-interactive (deprecated)?

You can even override some of the default options set by -f with KEY=VALUE pairs:

Kendall Moore
August 30, 2019, 9:32 PM

I’m not 100% sure. I saw that but had a few thoughts. The first was that I thought that option was deprecated, though reading it in this Jira comment makes me think -f itself isn’t deprecated but only an older option was (this is still sort of confusing to me but that’s the interpretation I have right now). Can we separate these out into their own flags entirely so that it’s a little more clear? The other was that I didn’t entirely trust the word “defaults” as written. When you go through simp config there are current OS values and “recommended values.” Without a better understanding of what the recommended values are I’m tempted to say I’d want this flag to just assume the current OS defaults. Is that what -f does or does it use the recommended values?

Trevor Vaughan
September 3, 2019, 4:22 PM

--non-interactive is a different option that has been deprecated. We may want to rearrange the options a bit so that's less confusing but that's the way Ruby's OptionParser handles it.

Trevor Vaughan
September 4, 2019, 5:50 PM

Thought I would run through this to see what was up and I think I get it.

was filed to help address unknown values.

It looks like the following is as close as you're going to get to a "hands free" configuration:

Kendall Moore
September 4, 2019, 8:57 PM

The linked ticket is indeed relevant in that I would expect users to be able to use simp config in a “hands free” way and end in a state that allows them to immediately run simp bootstrap without any manual intervention no matter how SIMP was installed (ISO, YUM, etc.). The goal here is that a new user should be able to get started as quickly as possible in a lab environment so they can start testing SIMP.


Epic Link


Story Points