Update rpm lockfile config

[joelcapitao]

See commit messages

[gemini-code-assist]

Summary of Changes

Hello @jcapiitao, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the RPM lockfile configuration by relocating key YAML files to the repository root and updating the associated build script to reflect these new paths. Additionally, it modifies the RPM input configuration to explicitly define the build context using a Dockerfile, aiming to improve clarity and consistency in the RPM build process.

Highlights

• Configuration File Relocation: The rpms.in.yaml and rpms.lock.yaml configuration files have been moved from the ci/hermetic/ directory to the repository's root directory. This centralizes the RPM lockfile configuration.
• Script Path Updates: The ci/hermetic/update_rpms_lockfile script has been updated to reflect the new location of rpms.in.yaml and rpms.lock.yaml, ensuring it correctly references these files from their new root-level paths.
• RPM Build Context Definition: The rpms.in.yaml file's context configuration has been updated from bare: false to containerfile: ./Dockerfile. This change explicitly defines the build context for RPMs to be based on a Dockerfile, likely streamlining or clarifying the build environment setup.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors the RPM lockfile configuration by moving rpms.in.yaml to the project root and updating its content and the associated scripts. The changes are logical and consistent. My feedback focuses on improving the shell script's robustness by avoiding hardcoded relative paths, which will make it more maintainable.

[jbtrystram]

LGTM

[joelcapitao]

I proposed openshift/release#66738 to ignore running PROW jobs for the lockfiles.

[joelcapitao]

/override ci/prow/rhcos
/override continuous-integration/jenkins/pr-merge
This PR changes the Konflux config only

[openshift-ci]

@jcapiitao: Overrode contexts on behalf of jcapiitao: ci/prow/rhcos, continuous-integration/jenkins/pr-merge

Details

In response to this:

/override ci/prow/rhcos
/override continuous-integration/jenkins/pr-merge
This PR changes the Konflux config only

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.