Add fips_compatible boolean flag for input package policy templates#914
Merged
jsoriano merged 2 commits intoelastic:mainfrom Jul 1, 2025
Merged
Conversation
5 tasks
💚 Build Succeeded
cc @jsoriano |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Add the
fips_compatibleflag to input packages too. It was added to integration packages in #894.Add tests for this flag.
Why is it important?
We want this flag in input packages too, as of https://github.com/elastic/integrations/pull/14068/files#diff-fb59326b77824eddf3679997b911a05757b595bf8b64da7fef533e53f60401d6R15.
Checklist
test/packagesthat prove my change is effective.spec/changelog.yml.Related issues
fips_compatibleflag to multiple packages integrations#14068