You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The optional attribute reusable.order was introduced in #864 to ensure chained reuses happen in the right order. It may be a necessary setting when dealing with chained reuses.
This attribute should be added to the schemas/README.md doc.
Background
As of ECS 1.7.0, reusable.order is configured on the group fieldset to handle the group => user, user => many places chained reuse case.
Custom fields may also use reusable.order for custom chained reuse. Example:
Without adding order: 3 in host.yml, the generator will default order to 2. Under the default, host won't have all the expected nestings before host is reused under acme.
Documenting this parameter will be useful for users dealing with this particular scenario.
The text was updated successfully, but these errors were encountered:
Summary
The optional attribute
reusable.order
was introduced in #864 to ensure chained reuses happen in the right order. It may be a necessary setting when dealing with chained reuses.This attribute should be added to the
schemas/README.md
doc.Background
As of ECS 1.7.0,
reusable.order
is configured on thegroup
fieldset to handle thegroup
=>user
,user
=> many places chained reuse case.Custom fields may also use
reusable.order
for custom chained reuse. Example:./custom_schemas/host.yml
:./custom_schemas/acme.yml
:Generator script command:
$ python scripts/generator.py --include _testing/discuss/schemas --out _testing/discuss/output
Without adding
order: 3
inhost.yml
, the generator will defaultorder
to2
. Under the default,host
won't have all the expected nestings beforehost
is reused underacme
.Documenting this parameter will be useful for users dealing with this particular scenario.
The text was updated successfully, but these errors were encountered: