-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename of splunk_hec token
to default_token
not documented
#10610
Comments
Hi @treethought ! Thanks for the report. |
Hey @jszwedko, yeah I only noticed the change because when deploying with the helm chart and with |
🤔 could you share the full output? I wasn't able to reproduce that running Vector locally using |
This was renamed to `default_token`. Ref: #10610 Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
Sure, here is the logs from the vector container
With the following sink config. And as stated above, token is set via helm
|
@jszwedko actually it does look like With |
Aaah, yeah, I see. We've run into this issue before with the configuration deserialization framework we use, Apologies for the confusion here. I'll link this to #9115 so we can make sure whatever solution we come up with for the future of Vector's config deserialization handles these cases. |
excellent, thanks for the context and quick response as always! |
This was renamed to `default_token`. Ref: #10610 Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
This was renamed to `default_token`. Ref: #10610 Signed-off-by: Jesse Szwedko <jesse@szwedko.me>
The 0.19.0 highlights describe the changes to splunk acknowledgements and passthrough token but do not call out the ranming of
token
todefault_token
as a breaking change.https://vector.dev/highlights/2021-12-28-0-19-0-upgrade-guide/
The text was updated successfully, but these errors were encountered: