For checking wether the api was tempered with, we need separate action,
that just checks the code against the currently pulled spec.
This introduces two subactions for `npx api`.
These are `npx api:generate` and `npx api:pull`.
Use curl to download `api.yaml` from `osbuild/image-builder` in
`api.sh`.
Now we do not need to manually download `api.yaml` from `image-builder`
before running `npm run api`.
This reverts commit 36f9e70565.
The Compliance v1 API is not stable and not intended for consumption by
other teams. We will implement the OpenSCAP MVP without the Compliance
API for now with a hard coded list of polices in image-builder, and when
their v2 API is ready in the near future begin using it to retrieve
policies.
This commit adds the Compliance service's API, which we can query for a
list of SCAP security policies.
In a follow-up PR, we will allow the user to optionally select a policy
when creating an image in the wizard.
This commit updates the readme to reflect the use of
`@rtk-query/codegen` for generating API slice definitions and adds a new
script, `api.sh`, that is used to generate the API slices when the user
runs `npm run api`.
