-
Notifications
You must be signed in to change notification settings - Fork 706
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
k8s image content from PRs: fix execution and add instruction how to use the image #11459
Conversation
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
f46b0f4
to
0cb1b09
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor spelling suggestion
861896a
to
15178b6
Compare
Add option to use a k8s container image to create Profile Bundles. This makes it easy to reference any k8s content image to create Profile Bundles for OCP4 and RHCOS4.
Fix usage of pr_number stored by Kubernetes content image for PR trigger.
Use thollander's comment pull request action. It can upsert the comment with the built content image, instead of creating new comments.
15178b6
to
5da44a1
Compare
@Vincent056 Hey, this should fix consumption of the I have reverted to using thollander's action as well, as it provides Upsert capability. But this PR needs to be merged to get into effect. |
Code Climate has analyzed commit 5da44a1 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 58.3% (0.0% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - just a comment about reorganizing our tools to make it simpler to understand the responsibility of the build script.
Perhaps we can tackle that in a separate PR though.
Let's tackle separating the image push functionality from the build script in a separate PR. |
Sure I'll tackle that soon after we get the action working. |
Description:
utils/build_ds_container.py
just createsProfileBundle
based on a k8s content image.Rationale:
Review Hints: