Included supported versions in config documentation

[aowen-uwmad]

A user requested

In the Pelican config documentation, could the minimum version supporting a feature/setting be shown?
I created a config file months ago, and several knobs seem to have disappeared while others were added - I’d like to avoid checking each and every setting too often.

As a facilitator, I think this is an excellent idea.

I further suggest we extend it to

• include the maximum version, for items that we plan to deprecate
• include a list of deprecated options and what version they were deprecated in (this probably only needs to go as far back as the current major release, e.g., no 6.x options are listed in the 7.x manual)

[jhiemstrawisc]

Note that our docs are already versioned (top right corner):
https://docs.pelicanplatform.org/about-pelican

If a user needs to know which knobs are valid/deprecated for a specific version, is it sufficient for them to visit docs for the version in question? Maybe we need to make this docs setting more apparent?

[aowen-uwmad]

I think the docs versioning just helps with the infrastructure for implementing this feature.

My concern with the "change the docs version" approach to finding the config is that it's essentially equivalent to trawling the git commit history. If you have a vestigial option sitting around and you don't remember which version of pelican you were using when you added it, then you could be clicking through versioned docs for a while looking for that information. (At least with git you have the bisect option..)