Why is disabling storage cleaning experimental?

Help
1

1. The problem I’m having:

Hi, we would like to turn off storage cleaning but were wondering about diasable_storage_clean being marked as experimental and subject to change. Why exactly is it marked experimental? Can we guarantee this option will be available and stable in the near future?

The reason we’d like to do this is because the storage module we are using has a bug that deletes all of our certificate data when used in specific circumstances (with load_storage). We’d like to disable storage cleaning until this is fixed.

2. Error messages and/or full log output:

N/A

3. Caddy version:

11.2

4. How I installed and ran Caddy:

a. System environment:

homebrew, macOS Sequoia 15.6.1

b. Command:

N/A

c. Service/unit/compose file:

N/A

d. My complete Caddy config:

N/A

5. Links to relevant resources:

2

We mark things as experimental when the API may not be final. That’s all. You can just watch the release notes in case we do make a change. But this one has been essentially stable for a long time now, and we probably just forgot to unmark it as experimental.

3

That makes sense. Thank you so much for your response!

4

Francis is right about this. And in this case, it’s likely to stay, however I remember also feeling “iffy” about this since it’s not generally a good idea… it was an immediate workaround for a problem that needed more time and analysis to solve properly (I think it was expensive billing rates for all the calls associated with cleaning storage). But a more proper solution should be developed in which case the workaround won’t be needed anymore. However in your case it definitely sounds better than the alternative!