Skip to content

Drop legacy maxconcurjobs storage parameter#236

Draft
smortex wants to merge 3 commits intomasterfrom
drop-legacy-maxconcurjobs
Draft

Drop legacy maxconcurjobs storage parameter#236
smortex wants to merge 3 commits intomasterfrom
drop-legacy-maxconcurjobs

Conversation

@smortex
Copy link
Member

@smortex smortex commented Jan 4, 2026

In #235, we fixed an incorrect behaviour of the maxconcurjobs parameter of the storage configuration, and aligned it with the other bacula components by calling it max_concurrent_jobs.

Backward compatibility was kept, and a deprecation warning was added.
This PR drop these.
It is intended to be merged in the next major release of the module following a release including #235.

@smortex smortex force-pushed the drop-legacy-maxconcurjobs branch from 8e6b4b3 to c401e74 Compare January 4, 2026 20:57
@smortex smortex added the backwards-incompatible This change will lead to a major version bump for the next release label Jan 4, 2026
@smortex smortex added this to the 9.0.0 milestone Jan 4, 2026
This fix a bunch of deprecation warnings.
When data types where added in version 5.4.0 a few years ago (#117),
backward compatibility with old catalog that used String for all
parameters was preserved.

We already did a few major releases so keeping this backward
compatibility does not make sense and we can make the types more
consistent by removing them.
This parameter has been replaced by a max_concurrent_jobs for
consistency with other classes.
@smortex smortex force-pushed the drop-legacy-maxconcurjobs branch from c401e74 to f1d4976 Compare January 20, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backwards-incompatible This change will lead to a major version bump for the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants