Skip to content

Conversation

@WebSpider
Copy link
Contributor

Fixes #364

@github-actions
Copy link
Contributor

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale Issues or pull requests that have not been updated for a while label Oct 11, 2024
@WebSpider
Copy link
Contributor Author

Well, its ready for merge, so it would be appreciated not to close it.

@github-actions github-actions bot removed the Stale Issues or pull requests that have not been updated for a while label Oct 12, 2024
@github-actions
Copy link
Contributor

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale Issues or pull requests that have not been updated for a while label Nov 11, 2024
@WebSpider
Copy link
Contributor Author

Unstale once more

@WebSpider
Copy link
Contributor Author

@fastlorenzo i dont mind helping out with maintenance of these charts. Let me know how i can help.

@github-actions github-actions bot removed the Stale Issues or pull requests that have not been updated for a while label Nov 14, 2024
@aki-ks
Copy link
Contributor

aki-ks commented Mar 24, 2025

I think before this get's merged and released, a hint could be inserted that, if the old variable is used, the chart fails to render, spitting an explanatory error, that tells about the deprecation. This breaking change would e.g. break my mailu deployment if I would upgrade.


Here's an example what traefik did, when they made a breaking change to theirs values schema:
https://github.com/traefik/traefik-helm-chart/blob/39a4a3d66b28b11b8bec0f0dc2fb53712b9716df/traefik/templates/_podtemplate.tpl#L605-L607

Their previous syntax was:

ports:
  web:
    redirectTo: websecure

This was changed to the following:

ports:
  web:
     redirections:
        entryPoint:
          to: websecure
          scheme: https
          permanent: true

When the old Syntax is used today, the Chart fails to render and yields an explanatory error

@github-actions
Copy link
Contributor

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the Stale Issues or pull requests that have not been updated for a while label Sep 29, 2025
@WebSpider
Copy link
Contributor Author

/unstale

@github-actions github-actions bot removed the Stale Issues or pull requests that have not been updated for a while label Sep 30, 2025
@DrPsychick DrPsychick added the type/major Updates to major version label Oct 17, 2025
@WebSpider
Copy link
Contributor Author

WebSpider commented Oct 20, 2025

I think before this get's merged and released, a hint could be inserted that, if the old variable is used, the chart fails to render, spitting an explanatory error, that tells about the deprecation. This breaking change would e.g. break my mailu deployment if I would upgrade.

Right now as this PR is, the chart does not fail to render as far as i can see, we use this to set the submissions service instead. Could you please let me know what I missed here?

I do agree that it wouldn't hurt to emit a deprecation notice for people using commandline-helm to upgrade / install the chart.

@github-actions github-actions bot added area/charts Changes made in the charts directory area/docs Changes made in the docs files labels Oct 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/charts Changes made in the charts directory area/docs Changes made in the docs files type/major Updates to major version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename smtps to submissions

3 participants