Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Using set_sector in a remap transform produces a warning on startup. It works as expected tho. This warning is misleading and leaks secrets to the logs.
Another strange behaviour: when .event.category is commented out, then the warning disappears.
Running tests
2024-07-08T09:39:48.574972Z WARN transform{component_kind="transform" component_id=transform0 component_type=remap}: vector::transforms::remap: VRL compilation warning. warnings=
warning[E900]: unused result for function call `set_secret("splunk_hec_token", "B7E5D595-61E8-4008-A556-E557421E81F0")`
┌─ :2:1
│
2 │ set_secret("splunk_hec_token", "B7E5D595-61E8-4008-A556-E557421E81F0")
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the result of this expression or remove it
│
= this expression has no side-effects
= see language documentation at https://vrl.dev
= try your code in the VRL REPL, learn more at https://vrl.dev/examples
test name0 ... passed
### Example Data
_No response_
### Additional Context
_No response_
### References
_No response_
A note for the community
Problem
Using
set_sector
in aremap
transform produces a warning on startup. It works as expected tho. This warning is misleading and leaks secrets to the logs.Another strange behaviour: when
.event.category
is commented out, then the warning disappears.Configuration
Version
vector 0.39.0
Debug Output