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

Include ref when writing out inspec control objects #2259

Merged
merged 2 commits into from
Oct 24, 2017
Merged

Conversation

arlimus
Copy link
Contributor

@arlimus arlimus commented Oct 18, 2017

just like tags for all auto-generation and api-driven development :)

Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
Signed-off-by: Dominik Richter <dominik.richter@gmail.com>
@aaronlippold
Copy link
Collaborator

Just for rounding it out do we want to add 'remediation' which should fully flush out the object with respect to what is documented and supported.

@adamleff
Copy link
Contributor

@aaronlippold that's outside the scope of this PR, which simply ensures that refs are properly output when writing out a control object to disk. Adding "remediation" as a first-class citizen to the DSL would warrant an RFC for discussion. Right now, "remediation" is used as an example of a ref key, but isn't part of the DSL.

@adamleff adamleff changed the title support ref for inspec control objects Include ref when writing out inspec control objects Oct 24, 2017
@adamleff adamleff added the Type: Enhancement Improves an existing feature label Oct 24, 2017
Copy link
Contributor

@adamleff adamleff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, @arlimus!

@adamleff adamleff merged commit 39d743b into master Oct 24, 2017
@adamleff adamleff deleted the dom/object-ref branch October 24, 2017 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Improves an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants