search

RHSecurityCompliance / contest

Content Testing for ComplianceAsCode/content
Other
4 stars 7 forks source link

Remove `openscap` and `ssg` versions from waivers #47

Closed comps closed 7 months ago

comps commented 1 year ago

Since we decided to split waivers to upstream and released, we stopped using RPM versions in them.

This opens up more scratch testing possibilities - our tests already use datastream XMLs instead of content RPMs (even copying them to VMs, hosting via HTTP for Anaconda, etc.), so it should be possible to extend this logic to use arbitrary uploaded/provided

only some of which will be needed, depending on the tests executed.

For example - one could

  1. reserve a Beaker (or other) persistent OS for some 24 hours
  2. upload (scp) + build content there, no RPMs necessary
  3. run tmt giving it paths to the content pieces
  4. find bugs, edit content, goto 2

All that without ever needing to make a commit in either content or contest.

This was possible early in Contest development, but we ditched it because we needed RPM versions for waivers. But since we probably don't need them anymore, we could re-enable this workflow.

comps commented 7 months ago

I'll close this as fixed with https://github.com/RHSecurityCompliance/contest/pull/80/files - we didn't remove oscap version capabilities, but that PR decoupled content testing from scap-security-guide which is what this issue was about.