stackabletech / stackabletech/nifi-operator
XML reserved characters are not escaped when being used in XML configuration files
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 48
- Forks
- 12
- Avg merge
- 11h 26m
- Merged PRs (30d)
- 10
Description
Affected Stackable version
25.7
Affected Apache NiFi version
2.4.0
Current and expected behavior
When the Stackable NiFi operator takes a parameter value and uses it in one of its XML-based configuration files it does not escape reserved characters. This means that if the value contains a character such as an ampersand (&) then the result is malformed XML document that cannot be parsed, causing NiFi to fail on startup.
Possible solution
The operator should escape any reserved characters when it includes a parameter value e.g. replacing & with &.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the code that renders XML-based configuration from parameter values, then reproduce the failure with an ampersand or another reserved character. Confirm that the generated configuration remains valid XML and that NiFi can start successfully with the escaped value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100