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

clarify initial usage instructions for installation. #239

Open
gbinal opened this issue Oct 31, 2016 · 3 comments
Open

clarify initial usage instructions for installation. #239

gbinal opened this issue Oct 31, 2016 · 3 comments
Labels

Comments

@gbinal
Copy link

gbinal commented Oct 31, 2016

On this page, I'm following the steps quite happily, but when I run step 3, I get this message: open cert-1.yaml: no such file or directory.

Apparently, the certifications listed in the suggested template don't work out of the box. I was told to use this template instead and it worked fine but it'd be good to update the instructions.

@shawndwells
Copy link
Member

shawndwells commented Jan 7, 2017

Using the template suggested above, I can perform a compliance-masonry get, but when trying to convert into a doc:

$ compliance-masonry docs gitbook foo
Error: `opencontrols/certifications/a.yaml` does not exist
Use one of the following:
FedRAMP-low
FedRAMP-moderate
LATO
[shawn@devbox openshift-masonry]$ compliance-masonry docs gitbook FedRAMP-low
Warning: markdown directory does not exist
Component files does not exist
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version
Unknown schema version

Love the idea of compliance masonry, but there doesn't appear to be any working examples of how to get this setup.

@anweiss
Copy link
Contributor

anweiss commented Jan 9, 2017

If you installed compliance-masonry from Releases, the binaries are a bit out of date. Try following the dev install docs here.

@jcscottiii ^ ... we should run another goxc and publish

@git-ingham
Copy link

This issue could also be fixed by fixing this issue:
Parsing errors should display the offending file information #168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants