Sentinel CCF Connector examples do not support Bicep
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
MSFT Sentinel CCF connectors can be very long ARM templates. Unfortunately, they are not so easy to use with bicep as they use nested templates in the "mainTemplate" property of Microsoft.OperationalInsights/workspaces/providers/contentTemplates.
There are no example of CCF connectors using bicep, nor resource type support for the CCF types.
Bicep decompiles is only able to understand the "outer" template, leaving the nested templates untouched in json.
Contributor guide
Research direction
Start by examining how Bicep handles Microsoft.OperationalInsights/workspaces/providers/contentTemplates and nested mainTemplate ARM JSON during decompilation. The issue calls for CCF connector examples in Bicep and resource-type support; done means both nested templates and the relevant CCF types are supported, with examples available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100