Clean up mechanism in Optimize

[mboskamp]

Acceptance Criteria (Required on creation)

Background
The ConfigurationValidator class is used to validate the Optimize configuration. If users use a configuration property that does not exist anymore, Optimize will detect this and log an error and throw an exception.

Current situation
Deleted properties are managed within deleted-config.yaml. It has the deleted property name and a link to the relevant documentation section.
The current validator logic does not use the links from deleted-config.yaml but replaces all of the links with the generic DOCS_URL (here, see also ConfigurationValidatorTest).

We can clean this behavior up as the links in deleted-config.yaml are not used.

Hints

This might be something the Optimize 8 team is interested in as well. Let's sync with them.

Links

Breakdown

Pull Requests

Preview Give feedback

No tasks being tracked yet.

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment