Update kustomize repo version to use pinned version from group_vars#3792
Open
evallesp wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Open
Update kustomize repo version to use pinned version from group_vars#3792evallesp wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
evallesp wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
…n from group_vars Now we can get the version from group_vars pinned section. We can still override this by passing extra vars or directly defined it from CI jobs. Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
force-pushed
the
kustomize_deploy_add_version_pinned
branch
from
bfe5086 to
7abbddf
Compare
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
evallesp
added a commit
to evallesp/ci-framework
that referenced
this pull request
Mar 24, 2026
This file in conjuction with: * openstack-k8s-operators#3774 * openstack-k8s-operators#3772 * openstack-k8s-operators#3792 Allows ci-framework to clone those repos (architecture was already enabled) when repositories are not already there due to zuul has not marked them as required-projects or because we're running them outside the zuul ecosystem. This is the almost the lowest in precedence, so if we still have these vars defined at zuul level or defaults-vars (passed as extra-vars) or scenarios files, this file is not taken into consideration. Precedence chain: * Zuul repos * cifmw_reproducer_repositories * cifmw_reproducer_default_repositories * Git pull logic in each of the roles Signed-off-by: Enrique Vallespi Gil <evallesp@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now we can get the version from group_vars pinned section. We can still override this by passing extra vars or directly defined it from CI jobs.