Skip to content

Feature: Allow configuring Helm hook weight via values#207

Open
jemsz95 wants to merge 1 commit into
chatwoot:mainfrom
jemsz95:push-zrnrkyzoosuv
Open

Feature: Allow configuring Helm hook weight via values#207
jemsz95 wants to merge 1 commit into
chatwoot:mainfrom
jemsz95:push-zrnrkyzoosuv

Conversation

@jemsz95

@jemsz95 jemsz95 commented Jun 11, 2026

Copy link
Copy Markdown

Why is this needed

As written, the chart can't be installed by argo-cd. Argo-cd maps Helm hooks to its own hook system, translating hook-weight to sync-wave. Because of differences in execution timing, certain migration jobs can enter a deadlock: the sync cannot succeed until the migration runs, but the migration isn't executed until the sync succeeds.

Making the hook weight configurable allows the migration to run after resources are synced but before the overall sync finishes.

Using this in argo-cd

Using the following values ensures that the hooks run before the start of the second sync wave (i.e sync wave 1)

source:
  helm:
    parameters:
      - name: hooks.migrate.hookAnnotation
        value: pre-install,pre-upgrade
      - name: hooks.migrate.hookWeight
        value: '1'

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2b95ec7eba

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread charts/chatwoot/values.yaml
Argo CD maps Helm hooks to its own hook system, translating hook-weight to 
sync-wave. Because of differences in execution timing, certain migration 
jobs can enter a deadlock: the sync cannot succeed until the migration runs, 
but the migration isn't executed until the sync succeeds.

Making the hook weight configurable allows the migration to run after 
resources are synced but before the overall sync finishes.
@jemsz95 jemsz95 force-pushed the push-zrnrkyzoosuv branch from 2b95ec7 to 582dadc Compare June 12, 2026 17:15
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.

1 participant