Conversation
* avoiding use of `describe.one` due to upstream bug inspec/4547
results in cleaner code
* avoid repetition of tests between dev and prod server profiles
* as problematic controls removed in previous commit
|
@dafyddj Good job, I like the look of this (scanned in general, not in detail yet). However, it's come at a very "interesting" time, which you're also responsible for! saltstack-formulas/template-formula#175 is a whole new take on how improve things on Travis, including adding These are the options that are apparent to me right now:
I don't believe it's fair for me to request number 1. Number 3 is a really ugly workaround; the whole point of the TOFS overrides is almost like a to-do list for things to be standardised across the whole org (and then remove the TOFS override -- such as the current What are your thoughts at this stage? Do you have a different opinion about how to proceed, or can you see an alternative option? |
|
Yes, I noticed your new PR some time after creating this, and realised they would conflict a little bit. |
|
@dafyddj That's very kind of you to offer, I appreciate it. |
|
Thanks @aboe76. We're going to merge saltstack-formulas/template-formula#175 soon, spread those changes to all of the formulas including this one and then revisit this PR again, rebased. |
|
Let me know when you want them merged. |
|
@aboe76 I'm almost done with saltstack-formulas/template-formula#175. I'm going to run tests on all formulas in my own forks in Travis, to make sure the propagation is going to work as expected. Please have a look at it in the meantime, if you get a chance. Just in case there's something we've missed. |
Accomplish two main things:
describe.oneby cleaning up inspec profilesthat was broken in the past (and was almost broken again in a subsequent refactor)