pashcan

This functionality would be helpful and goes hand-in-hand with overall recommendation to manage all configurations as code and to create custom image with your plugins. Other than the build logs...

@jgournet out of curiosity, is there any particular reason why you set `controller.overwritePluginsFromImage` that way instead of using `false`?

@jgournet No worries whatsoever! There are so many permutations with different versions of the helm chart and how built-in templates parse and apply certain values... I'll take any insight on...

I had a situation recently where we were using templating parts of the ingress and accidentally borked the URL part because it gets used there: https://github.com/jenkinsci/helm-charts/blob/main/charts/jenkins/templates/_helpers.tpl#L85 Took me better part...

Great explanation of the mechanics behind `overwritePlugins: true` and you are spot on about the variable comment verbiage being a bit misleading, @adambournsonos :pray: There are many levers to pull...

@laimonasA, suppressing unfurling does not appear to work for me while using Slack Workflow Builder & Webhook. ``` ... uses: slackapi/[email protected] with: payload: | { "pr-url": "https://github.com/some-org-here/test-slack-action/pull/4", "version": "0.4.3", "unfurl_links":...

After some additional poking around, I discovered that our slack workflows were of the [unmigrated legacy kind](https://slack.com/help/articles/16787711643411-Migrating-legacy-workflows-to-the-new-version-of-Workflow-Builder). Config to suppress unfurling works with the new workflow! :tada: Knowing that it...

The ability to subscribe to only the failed workflows would be super helpful to help reduce the notification noise :pray: