Skip to content

entityanalytics_ad: do not rename msDS-* fields #13094

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

Merged
merged 1 commit into from
Mar 13, 2025

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Mar 13, 2025

Proposed commit message

entityanalytics_ad: do not rename msDS-* fields

Apparently there are 322 msDS-* fields, so we either enumerate them in
the look-up table or hope that camelCase to snake_case is not lossy for
any of them if we want to do renames. Rather than doing that, accept
that we cannot rename any of them and revert this single case to retain
a consistent naming convention for them.

Note

Strictly breaking, but we are before v1.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

@efd6 efd6 added enhancement New feature or request Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] Integration:entityanalytics_ad Active Directory Entity Analytics labels Mar 13, 2025
@efd6 efd6 self-assigned this Mar 13, 2025
@efd6 efd6 force-pushed the entityanalytics_ad_subtle branch from aa1e50e to 7e04a21 Compare March 13, 2025 04:50
@efd6 efd6 requested a review from w0rk3r March 13, 2025 04:51
Apparently there are 322 msDS-* fields, so we either enumerate them in
the look-up table or hope that camelCase to snake_case is not lossy for
any of them if we want to do renames. Rather than doing that, accept
that we cannot rename any of them and revert this single case to retain
a consistent naming convention for them.
@efd6 efd6 force-pushed the entityanalytics_ad_subtle branch from 7e04a21 to 80c6fca Compare March 13, 2025 05:24
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @efd6

Copy link

@efd6 efd6 marked this pull request as ready for review March 13, 2025 05:42
@efd6 efd6 requested a review from a team as a code owner March 13, 2025 05:42
@elasticmachine
Copy link

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 merged commit a316378 into elastic:main Mar 13, 2025
7 checks passed
@elastic-vault-github-plugin-prod

Package entityanalytics_ad - 0.9.0 containing this change is available at https://epr.elastic.co/package/entityanalytics_ad/0.9.0/

flexitrev pushed a commit that referenced this pull request Mar 20, 2025
Apparently there are 322 msDS-* fields, so we either enumerate them in
the look-up table or hope that camelCase to snake_case is not lossy for
any of them if we want to do renames. Rather than doing that, accept
that we cannot rename any of them and revert this single case to retain
a consistent naming convention for them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:entityanalytics_ad Active Directory Entity Analytics Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants