-
Notifications
You must be signed in to change notification settings - Fork 48
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
Empty arrays are turned into nil #188
Comments
This was referenced Nov 10, 2021
andrewkroh
added a commit
to elastic/beats
that referenced
this issue
Jul 20, 2022
The module tests were failing because the empty tags array was being discarded resulting in the tags value being treated as `nil`. And this was not being accepted as a valid type for the inList function. The cause was elastic/go-ucfg#188.
andrewkroh
added a commit
to elastic/beats
that referenced
this issue
Jul 26, 2022
…ation (#32422) * system.auth - sync pipeline with Fleet integration (#32360) Sync the pipeline for the system.auth dataset with the Fleet integration from elastic/integrations#3705. This removes the event.type authentication_failed and authentication_success values which are not allowed as per ECS. You can use event.category: authentication and event.outcome: success/failure to query instead. (cherry picked from commit 475dd7e) * Update go-ucfg to v0.8.6 The module tests were failing because the empty tags array was being discarded resulting in the tags value being treated as `nil`. And this was not being accepted as a valid type for the inList function. The cause was elastic/go-ucfg#188. * Fix tests affected by go-ucfg upgrade Backport fix from 0022ea4. Co-authored-by: Andrew Kroh <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When parsing empty arrays from YAML to config objects and unpacking into an untyped representation like
map[string]interface{}
arrays in the original source are turned intonil
. Marshalling back to YAML this turns intonull
and is thereby not round-trippeable through ucfg:Consider:
leaves us with:
We have been hit in the ECK operator a couple of times by this issue:
coordinating
node role Coordinator nodes cannot be defined using node.roles cloud-on-k8s#3718We are using untyped
map[string]interface{}
target data structures in the operator for application configuration because it is difficult for us to model each Elastic stack application's configuration completely and for all versions of the Elastic stack that we need to support.The text was updated successfully, but these errors were encountered: