Open shaneutt opened 1 year ago
I'd go a step further and validate the PRs as they come, i.e. try to apply every manifest from the config/samples
and check that those don't fail.
After that's added we can introduce test assertions that e.g. a particular annotation is indeed present etc.
Current Behavior
Currently it's possible for the release process to miss generated kustomize manifests, or changes to APIs that would affect our
config/samples/
. In https://github.com/Kong/gateway-operator/pull/881 we added a reminder to our release process to handle this manually as a bandaid.Expected Behavior
CI for PRs should automatically verify that generators have run, and should run tests to exercise the kustomize manifests to ensure that everything is working. The
config/samples/
should be tested as well to verify they are functioning properly with recent changes.