Add iac_blueprints and scoped provider_permissions for integrations/inputs - #1225
Open
bhapas wants to merge 2 commits into
Open
Add iac_blueprints and scoped provider_permissions for integrations/inputs#1225bhapas wants to merge 2 commits into
bhapas wants to merge 2 commits into
Conversation
Allow integrations and inputs to declare IaC composition contributions via RFC 6902 patch files, and extend provider_permissions with resource scoping and conditional narrowing. Split from elastic#1209 per review feedback. Co-authored-by: Evgeniy Belyi <jeniawhite92@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
💚 Build Succeeded
|
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
1 participant
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?
iac_blueprintsat package, policy_template, input, and data_stream levels (RFC 6902 patch contributions)provider_permissions.permissionsitems withresourcesandconditionsformat_versionbefore3.7.0good_provider_permissionsWhy is it important?
Integrations and inputs need a way to declare IaC composition contributions and scoped provider permissions for frictionless cloud deployment. Split out of #1209 so these field changes can be reviewed separately from the new
blueprintpackage type.Checklist
test/packagesthat prove my change is effective.spec/changelog.yml.Related issues
Made with Cursor