search

opencontrol / discuss

a place to have conversations about OpenControl projects
https://github.com/opencontrol/discuss/issues
Other
16 stars 0 forks source link

subdirectory structures in component repos #41

Open shawndwells opened 6 years ago

shawndwells commented 6 years ago

In the current RedHat content repo, directory structure is used to breakout products:

https://github.com/opencontrol/RedHat/tree/master/OpenShift-v3 https://github.com/opencontrol/RedHat/tree/master/OpenStackPlatform

edit: Not sayin' this is the best practice or most ideal, just how we got started :)

If I understand the OpenControl schema for systems correctly, only url and revision can be passed as arguments:

https://github.com/opencontrol/schemas/blob/master/kwalify/opencontrol/v1.0.0.yaml#L53#L61

      systems:
        type: seq
        sequence:
          - type: map
            mapping:
              url:
                type: str
              revision:
                type: str

This forces us to create many content repos, e.g. redhat-rhel, redhat-openshift, redhat-jboss, instead of one per vendor.

Has there been a discussion on if this is desired? Should we update the schema to support a directory tree, e.g.:

  systems:
    - url: https://github.com/opencontrol/RedHat
      revision: master
      folder: tree/master/Product1

    - url: https://github.com/opencontrol/RedHat
      revision: master
      folder: tree/master/Product2
shawndwells commented 6 years ago

Bump. Would a PR to update the schema in this manner be welcome? Would be very useful for the ComplianceAsCode project, which is aggregating content from multiple vendors/technologies (unifying the SCAP, Ansible, and OpenControl workflow).