Skip to content

Conversation

mjwolf
Copy link
Contributor

@mjwolf mjwolf commented Oct 22, 2025

1. What does this PR do?

Add entity to the top level namespace of which it's used in sub-types.

For example, we want user.target.entity fields to be present. user.entity itself is a user type, so entity must be reused on the user type.

This also removes custom generator code which was being used to workaround the fact that this wasn't true before.

2. Which ECS fields are affected/introduced?

3. Why is this change necessary?

Fixed #2555

4. Have you added/updated documentation?

YES / NO / N/A

5. Have you built ECS and committed any newly generated files?

YES / NO

6. Have you run the ECS validation tests locally?

YES / NO

7. Anything else for the reviewers?


Commit Message

Add entity to the top level namespace of which it's used in sub-types.

For example, we want `user.target.entity` fields to be present.
`user.entity` itself is a `user` type, so `entity` must be reused on the
user type.

This also removes custom generator code which was being used to
workaround the fact that this wasn't true before.
@github-actions
Copy link

Documentation changes preview: https://docs-v3-preview.elastic.dev/elastic/ecs/pull/2556/reference/

@github-actions
Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Entity subdomain doesn’t exist in top level domains

1 participant