Ignore user-specified readiness checks
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
Users might want to explicitly disable readiness checks related to specific configuration parameters without disabling readiness checks altogether. Currently we don't have such an option.
### Describe the solution you'd like
I propose that we add a `polaris.readiness.ignore-offending-properties` config which can be, for example, set up as follows:
```
polaris.readiness.ignore-offending-properties=\
polaris.metrics.user-principal-tag.enable-in-api-metrics,\
polaris.features."ALLOW_INSECURE_STORAGE_TYPES",\
polaris.features."SUPPORTED_CATALOG_STORAGE_TYPES"
```
all readiness checks that blame one of the specified properties will be suppressed.
### Describe alternatives you've considered
We could have one config per readiness check but this is an overkill.
### Additional context
_No response_
Contributor guide
Research direction
Start by locating the readiness-check implementation and configuration handling for the properties named in the request. Trace how checks identify offending properties, then define the configuration behavior so matching checks are suppressed while other readiness checks remain active; verify the behavior with the project's readiness-check tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100