Skip to content

Fix: empty property value is considered as "not set" by quarkus#62

Open
Ksiona wants to merge 8 commits into
mainfrom
fix/documentation_mismatch
Open

Fix: empty property value is considered as "not set" by quarkus#62
Ksiona wants to merge 8 commits into
mainfrom
fix/documentation_mismatch

Conversation

@Ksiona
Copy link
Copy Markdown
Collaborator

@Ksiona Ksiona commented May 15, 2026

Redesigned:

  • The code contains a property, but no corresponding environment variable.
  • This property must be mapped to an environment variable, serving as its default value in the configuration file (to docs)
  • The property accepts a comma-separated list of allowed values; specifically, it should be populated with headers from the internal blacklist (which is not externally configurable). The property name is quarkus.context.propagation.allow-blocked-headers, and it is case-insensitive.
  • The documentation must clearly explain—from start to finish—how to configure this property in application.yaml using an environment variable. We handle this up to the container's environment variable level.

@Ksiona Ksiona requested a review from lis0x90 as a code owner May 15, 2026 20:40
@github-actions github-actions Bot added the bug Something isn't working label May 15, 2026
@Ksiona Ksiona requested review from alsergs and estetsenko May 19, 2026 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants