Add lib/inspec-objects.rb so inspec-objects can be required #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, require "inspec-objects" would throw an error. With this
commit the gem can be pulled in directly.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the
best of my knowledge, is covered under an appropriate open
source license and I have the right under that license to
submit that work with modifications, whether created in whole
or in part by me, under the same open source license (unless
I am permitted to submit under a different license), as
Indicated in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including
all personal information I submit with it, including my
sign-off) is maintained indefinitely and may be redistributed
consistent with this project or the open source license(s)
involved.
Signed-off-by: Luke Malinowski <[email protected]>
|
As long as there is an I believe that one of the following needs to happen:
Option 2 is the preferred option because it provides this repository the most control - with option 3 there may be a chance where the unique name |
When using autoload, the path was nondeterministic since the inspec/objects folder would sometimes be loaded. This moves over to using require_relative which guarantees we are loading from inspec_objects. Note that some imports had to be reordered since they were dependent on one another.
- added Bundle file - added cookstyle - ran the rake unit tests
- inital support for adding headers to controls - simplifed logic for adding the header per peer review - implementation is a basic string block - Setup unit tests and linting for project - added Bundle and added cookstyle - ran the rake unit tests Signed-off-by: Aaron Lippold <[email protected]>
* Post-Body Object - added inital object for post body of a control - a post-body should usually be a block of ruby/inspec code - the assumption will be that we just dump it as is into the control Signed-off-by: Aaron Lippold <[email protected]> * updated .gitignore file removed .vscode dir from repo Signed-off-by: Aaron Lippold <[email protected]> * added an ignore to our rubocop file given testing issues and whitespace using standard linting gem that the chef folks used before Signed-off-by: Aaron Lippold <[email protected]>
Signed-off-by: Aaron Lippold <[email protected]>
Signed-off-by: Aaron Lippold <[email protected]>
This reverts commit 722093e.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Previously, require "inspec-objects" would throw an error. With this
commit the gem can be pulled in directly.
Related Issue
Possible Fix for #2
Types of changes
Checklist: