-
Notifications
You must be signed in to change notification settings - Fork 0
Fix env support in prepare runner #32
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
base: main
Are you sure you want to change the base?
Conversation
This change corrects prepare runner playbook being not aware of running environment when we use input environment selector.
Summary of ChangesHello @darmach, I'm Gemini Code Assist1! 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 addresses a critical oversight in the Highlights
Using Gemini Code AssistThe 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
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 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
|
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.
Code Review
This pull request aims to make the prepare-runner workflow aware of the selected environment by adding logic to append an environment-specific runner label. However, the current implementation incorrectly uses ${{ matrix.environment }} in a context where no matrix strategy is defined for the job, which will cause the workflow to fail. I have provided a critical-severity comment with a suggested correction to use a workflow input instead, and have outlined the other necessary changes to fully implement this feature.
| <%- if github_environment_selector == 'input' and (github_registry.share | default(github_default_registry.share)) is false -%> | ||
| <%- set github_runs_on = github_runs_on + ['${{ matrix.environment }}'] -%> | ||
| <%- endif -%> |
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.
The use of ${{ matrix.environment }} on line 2 is incorrect because the prepare-runner job within this reusable workflow does not have a strategy.matrix defined. This will cause the workflow to fail because the matrix context is not available.
Given the intent to use the environment from a workflow input, you should use an input variable. To achieve this, you'll need to:
- Declare
kayobe_environmentas aworkflow_callinput in this file. - Pass the input from the calling workflow (likely in
generic.yml.j2). - Use
${{ inputs.kayobe_environment }}here instead of${{ matrix.environment }}.
This suggestion corrects the variable, assuming the necessary changes to pass the input will also be made.
<%- if github_environment_selector == 'input' and (github_registry.share | default(github_default_registry.share)) is false -%>
<%- set github_runs_on = github_runs_on + ['${{ inputs.kayobe_environment }}'] -%>
<%- endif -%>
This change corrects prepare runner playbook being not aware of running environment when we use input environment selector.