Skip to content
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

fix: Helmfile promote config per env #263

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cameronbraid
Copy link
Contributor

@cameronbraid cameronbraid commented Jan 27, 2021

The .jx/promote.yaml file is unusable as it overrides the namespace and helmfile rule for any promotion in the cluster repo

This PR fixes this by configuring the helmfile promotion rule per environment

For example You add a file helmfiles/foo/promote.yaml

apiVersion: promote.jenkins-x.io/v1alpha1
kind: HelmfilePromote
spec:
  keepOldVersions:
  - dev/myapp

Then the spec is merged into the HemlfileRule which then functions as it did before

I also simplified the tests to only test the case where HelmfilePromote is used

I set this up as a draft since it introduces a new API kind : HelmfilePromot which would need to be moved into the api package

@jenkins-x-bot-test
Copy link
Contributor

Hi @cameronbraid. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 jenkins-x/lighthouse repository.

@jenkins-x-bot-test
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign rajdavies
You can assign the PR to them by writing /assign @rajdavies in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cameronbraid cameronbraid force-pushed the helmfile-promote-config-per-env branch from 21f1177 to 1b4f446 Compare January 27, 2021 05:17
@cameronbraid cameronbraid changed the title Helmfile promote config per env fix: Helmfile promote config per env Jan 27, 2021
@cameronbraid cameronbraid force-pushed the helmfile-promote-config-per-env branch from 1b4f446 to e7959cf Compare January 27, 2021 05:21
@cameronbraid cameronbraid force-pushed the helmfile-promote-config-per-env branch from e7959cf to 4e1f713 Compare January 27, 2021 05:23
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
18.0% 18.0% Duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants