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

build(deps): update fluxcd #44

Merged
merged 1 commit into from
Jun 1, 2023
Merged

build(deps): update fluxcd #44

merged 1 commit into from
Jun 1, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2023

Mend Renovate

This PR contains the following updates:

Package Update Change
fluxcd/image-automation-controller patch v0.34.0 -> v0.34.1
fluxcd/source-controller patch v1.0.0-rc.4 -> v1.0.0-rc.5

Release Notes

fluxcd/image-automation-controller

v0.34.1

Compare Source

CHANGELOG

fluxcd/source-controller

v1.0.0-rc.5

Compare Source

CHANGELOG


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title build(deps): update dependency fluxcd/source-controller to v1.0.0-rc.5 build(deps): update fluxcd Jun 1, 2023
@metalmatze metalmatze merged commit 337df7b into main Jun 1, 2023
@renovate renovate bot deleted the renovate/fluxcd branch June 1, 2023 14:46
@maxbrunet
Copy link
Member

@metalmatze Not a big deal, just FYI

  • It is nice to comment with the output of argocd app diff scaleway-parca-demo-flux --revision=renovate/fluxcd before merging, so we know what changed.
  • Schemas need to be updated with new versions to make sure the CI is accurate:
    https://raw.githubusercontent.com/fluxcd/image-automation-controller/v0.34.0/config/crd/bases/image.toolkit.fluxcd.io_imageupdateautomations.yaml \
    https://raw.githubusercontent.com/fluxcd/image-reflector-controller/v0.28.0/config/crd/bases/image.toolkit.fluxcd.io_imagepolicies.yaml \
    https://raw.githubusercontent.com/fluxcd/image-reflector-controller/v0.28.0/config/crd/bases/image.toolkit.fluxcd.io_imagerepositories.yaml \
    https://raw.githubusercontent.com/fluxcd/source-controller/v1.0.0-rc.4/config/crd/bases/source.toolkit.fluxcd.io_gitrepositories.yaml \
  • For Flux specifically, the components tend to get released at the same time and updates may depend on each other, so we can wait a little to get them all grouped. We'll likely receive another PR for image-reflector-controller shortly.

@metalmatze
Copy link
Member

Oh sorry.
Would this be a CLI we would need to run? Never used argocd app diff before. Maybe there's a GitHub Action that can do that and post the comment to the PR?

@maxbrunet
Copy link
Member

No worries

Would this be a CLI we would need to run? Never used argocd app diff before.

There is some documentation here about how to use argocd: https://github.com/parca-dev/demo-deployments/tree/main/argocd-applications

Maybe there's a GitHub Action that can do that and post the comment to the PR?

It'd be nice. There is a bot, but it is unmaintained: https://github.com/argoproj-labs/argocd-bot

@metalmatze
Copy link
Member

Looking at what we do in our internal polarsignals repository, this should be possible here too:

    - name: Diff
      if: github.event_name == 'pull_request'
      run: |-
        mkdir -p /tmp
        # Need to always return true, as a diff may be expected.
        make diff > /tmp/diff || true
    - name: 'Comment Diff on PR'
      uses: actions/github-script@v6
      if: github.event_name == 'pull_request'
      with:
        script: |
          const fs = require('fs');
          const { issue: { number: issue_number }, repo: { owner, repo }  } = context;
          github.rest.issues.createComment({ issue_number, owner, repo, body: '<details>\n<summary>kubectl diff to be applied on merge</summary>\n\n```diff\n'+fs.readFileSync('/tmp/diff', 'utf8')+'```\n</details>' });

We should be able to run the argocd app diff CLI and pipe its output somewhere that we then paste to the PR 🙂

@maxbrunet
Copy link
Member

You're right, it should not be too hard, I'll try to look into it: #50

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

Successfully merging this pull request may close these issues.

2 participants