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

Don't assume content is in a file called opencontrol.yaml #11

Open
shawndwells opened this issue Mar 11, 2019 · 1 comment
Open

Don't assume content is in a file called opencontrol.yaml #11

shawndwells opened this issue Mar 11, 2019 · 1 comment

Comments

@shawndwells
Copy link

Most OpenControl content is named component.yaml, don't statically code in expectations that file is called opencontrol.yaml

docker container run -v $REPOSITORY:/opencontrol -p 127.0.0.1:8000:8000 --rm -it hypergrc:latest
hyperGRC failed to start:
Path `/opencontrol` to Compliance as Code repository does not contain a file named opencontrol.yaml.
@JJediny
Copy link

JJediny commented Jul 10, 2019

agree if/when the schema is changed from opencontrol -> NIST's OSCAL it'd be better to use component.yaml and/or component.yml. This is also related to the issue of having multiple files per control family in a /dir vs. a single file for a single component. #14

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

No branches or pull requests

2 participants