RFPD-77178: log ingestion API#20
Conversation
8a26673 to
25be003
Compare
| "type": "Microsoft.Logic/workflows" | ||
| }, | ||
| { | ||
| "type": "Microsoft.Authorization/roleAssignments", |
There was a problem hiding this comment.
FYI @ErikMangstenRecFut - this is pretty cool.
This is when using Managed Identity - you can apparently ship the role assignments like this, which makes onboarding easier.
We could do this eventually for more logic apps imo if it works well.
It does mean that the person instantiating the logic app needs high permissions. That's why (A)I added an option for it, see other comment
There was a problem hiding this comment.
That is really cool.
Wonder if this is a "well known" pattern, but in some sense, I feel like all of these "easier onboarding" steps is just possible because we have such high permissions, and as we know, questions about permissions is like the number 1 question regarding Azure. So I'm a bit ambivalent of adding these things we quite don't understand and requires high permissions.
There was a problem hiding this comment.
I also wonder if it's well-known / if Microsoft will accept it. I understand it to some extent, I think the new readme covers it pretty well, so I'll try to submit it with the role assignment and see what Microsoft says.
| @@ -0,0 +1,92 @@ | |||
| { | |||
There was a problem hiding this comment.
I don't think this will be accepted by msft. I tried to add this in a previous PR but it was rejected :(
There was a problem hiding this comment.
Gotcha. I'll try again :)
There was a problem hiding this comment.
FYI @ErikMangstenRecFut I moved this JSON to the Data Connectors folder in order to pass validation
|
/upstream-pr |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits:
|
d0fb9fa to
30cf3b7
Compare
|
/upstream-pr |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits: |
|
/upstream-pr |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits: |
f522d7d to
48bdedf
Compare
|
/upstream-pr |
|
Opened PR with MSFT: Azure#14478 |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits: |
Renamed to azuredeploy-incident-creation-analytic-rule.json and moved to Data Connectors/ to pass DetectionTemplateSchemaValidation which requires all files in Analytic Rules/ to be .yaml. Updated deploy button URL in Playbooks/readme.md to match new path.
Adds the custom table definition so KqlValidations CI passes (KS204).
The ARM engine accepts string expressions (e.g. "[parameters('flag')]")
for the resource condition field — this is the standard pattern for
conditional resource deployment in ARM templates. The schema validator
was incorrectly limiting condition to literal boolean values only,
causing PlaybooksValidations CI to fail on any template that uses an
ARM expression for condition (e.g. role assignments gated on a
create_role_assignment parameter).
This change aligns the schema with actual ARM behavior by accepting
both boolean and string types for the resource-level condition field.
The output-level condition (a separate definition) is unchanged.
|
/upstream-pr |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits: |
|
/upstream-pr |
|
Upstream branch: feat/RFPD-77178-log-ingestion-api Cherry-picked commits:
|
|
New PR towards MSFT: Azure#14495 |
| @@ -0,0 +1,49 @@ | |||
| { | |||
There was a problem hiding this comment.
FYI @ErikMangstenRecFut , I think we need to add this in order to pass validation 🤯
We did have an entry in this folder for the previous Identity solution as well so it feels OK.
There was a problem hiding this comment.
Yes this is needed to pass validation, one of the many new "features" :D
| }, | ||
| "condition": { | ||
| "type": "boolean", | ||
| "type": ["boolean", "string"], |
There was a problem hiding this comment.
FYI @ErikMangstenRecFut let's see what Microsoft says about this. But it did work to have condition as a string, this is what we used to implement the create_role_assignment parameter. So I think their validation is too strict here. See Claude's commit message for more details.
No description provided.