-
Notifications
You must be signed in to change notification settings - Fork 518
Add fips_compatible flag to Azure * packages
#14769
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
Conversation
| multi: false | ||
| required: false | ||
| show_user: false | ||
| default: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please note that these changes are due to running elastic-package-changelog. I think as it runs elastic-package format internally, hence the change. I also validated the same by using the format command, it is because of that only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is applicable to all unrelated formatting changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you
muthu-mps
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
🚀 Benchmarks reportTo see the full report comment with |
|
@elastic/security-service-integrations You own some packages that use azure-eventhub as well. I did not touch them, as I am specifically raising this PR for azure* But I'd request you to take a look at these — elastic/beats#44885, elastic/beats#44902 and elastic/beats#44909; as you might be using them in your packages. |
|
@elastic/obs-ds-hosted-services and @elastic/security-service-integrations Can someone please take a look at this PR? |
|
security-service-integrations is not a codeowner here. |
|
Can someone from @elastic/obs-ds-hosted-services please take a look? |
|
@shmsr there are some more azure related integrations that are not listed in your pr. Is there a reason not to include them? |
In this you will find more. And apart from that, only packages left are:
As you can see as cc: @gizas |
gizas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comment above. Good to have it here to make clear for future review (as the title might be a little misleading)
💚 Build Succeeded
History
cc @shmsr |
|
|
Package azure_ai_foundry - 0.6.0 containing this change is available at https://epr.elastic.co/package/azure_ai_foundry/0.6.0/ |
|
Package azure_app_service - 0.7.0 containing this change is available at https://epr.elastic.co/package/azure_app_service/0.7.0/ |
|
Package azure_application_insights - 1.9.0 containing this change is available at https://epr.elastic.co/package/azure_application_insights/1.9.0/ |
|
Package azure_billing - 1.9.0 containing this change is available at https://epr.elastic.co/package/azure_billing/1.9.0/ |
|
Package azure_functions - 0.10.0 containing this change is available at https://epr.elastic.co/package/azure_functions/0.10.0/ |
|
Package azure_logs - 0.4.0 containing this change is available at https://epr.elastic.co/package/azure_logs/0.4.0/ |
|
Package azure_metrics - 1.10.0 containing this change is available at https://epr.elastic.co/package/azure_metrics/1.10.0/ |
|
Package azure_openai - 1.9.0 containing this change is available at https://epr.elastic.co/package/azure_openai/1.9.0/ |


Proposed commit message
The
fips_compatibleflag is added to all policy templates (Azure *) that use either azure/metrics or azure-eventhub inputs.These inputs are explicitly disabled in FIPS-enabled environments within Beats (elastic/beats#44885, elastic/beats#44902). By marking the relevant policy templates with
fips_compatible: false, we ensure consistency and proper behavior of these integrations when deployed in FIPS environments.Related Context:
fips_compatibleflag: elastic/package-spec#894, elastic/package-spec#914Checklist
changelog.ymlfile.