Open kpollich opened 23 hours ago
cc @seanstory
Makes sense 👍 I think this could have been used even in some packages that have many policies now, like AWS.
I would only avoid focusing on representation and call the flag something like disable_parent_policy
, or something like this.
Something else to note when it comes to supporting this in Fleet - perhaps we should use the policy template name when populating the integration policy's name field. Today creating an "AWS Billing Metrics" integration policy still results in an integration policy named "aws-1" and editing it takes you to the full integration policy page for all policy templates.
For integrations like
elastic_connectors
, usage of ofpolicy_templates
is more about easing maintenance burden and less about reusing variables across different templates or leveraging any kind of information architecture. For integrations like this, we should have an option/flag in the manifest that allows Fleet to hide the "parent tile" for the integration, instead only showing the policy templates cards.