Make a runnable lifecycle tagger

[loosebazooka]

This takes the bulk tagger and adds bazel wrappers around it. The intention is to query the system and run bulk tagger scripts on cloud run on a cron to tag any older images.

[gemini-code-assist]

Summary of Changes

Hello @loosebazooka, 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 establishes a new framework for automated lifecycle management of container images by integrating an existing bulk tagger with Bazel. The changes introduce specific Bazel rules and macros to enable the identification and tagging of older images, with the ultimate goal of deploying this functionality on Cloud Run as a scheduled task. This enhances the maintainability and organization of image repositories by ensuring timely application of lifecycle tags.

Highlights

• New Lifecycle Tagger Integration: Introduces Bazel wrappers for an existing bulk tagger, making it runnable within the Bazel ecosystem.
• Automated Image Tagging: Enables the system to query for and tag older images, intended for execution on Cloud Run via cron jobs.
• Bazel Rule Definitions: Adds new Bazel build files (BUILD.bazel, defs.bzl, tag.bzl) to define the attach_lifecycle_tags macro and supporting tag rule.
• Script Relocation: Moves the tag.sh script and its README into the new private/tools/lifecycle directory for better organization.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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. ↩

[github-actions]

🌳 🔧 Config Check

This pull request has not modified the root BUILD

[gemini-code-assist]

Code Review

This pull request introduces a runnable lifecycle tagger for container images using Bazel, which is a great addition for automating image management. The implementation is sound, but I've identified a few areas for improvement. My feedback focuses on enhancing code clarity, reducing redundancy, and improving the robustness of a shell command. Specifically, I've pointed out duplicated configuration values that should be centralized, and opportunities to simplify some of the Starlark code for better readability and maintainability.

[github-actions]

🌳 🔄 Image Check
This pull request doesn't make any changes to the images. 👍
You can check the details in the report here