CTI addendum threat.feed.name, threat.feed.dashboard_id

[ecezalp]

• Have you signed the contributor license agreement? yes
• Have you followed the contributor guidelines? yes
• For proposing substantial changes or additions to the schema, have you reviewed the RFC process? yes
• If submitting code/script changes, have you verified all tests pass locally using make test? yes
• If submitting schema/fields updates, have you generated new artifacts by running make and committed those changes? yes
• Is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed. yes
• Have you added an entry to the CHANGELOG.next.md? yes

[peasead]

LGTM

[ebeahan]

Field additions look good to me!

CI is failing because there's several files that need updated each time the schema's updated.

If you run make from the top-level of the repo, it'll auto-generate all the necessary changes. After running make, add and commit the updates artifacts/docs and push the changes. This should make CI go ✅.

Finally, can you add a CHANGELOG.next entry under the 8.2 header: https://github.com/elastic/ecs/blob/main/CHANGELOG.next.md#820-soft-feature-freeze? Though 8.2 is under soft FF, there's no issue adding these fields.

[ebeahan]

LGTM. Thanks!

[ebeahan]

💚 All backports created successfully

Status	Branch	Result
✅	8.2

Questions ?

Please refer to the Backport tool documentation