chore: add var lacework_integration_guid to outputs and sleep for az role propogation #62
Conversation
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
…re role propogation
kirklandnuts
approved these changes
Jul 29, 2025
Contributor
kirklandnuts
left a comment
kirklandnuts
left a comment
There was a problem hiding this comment.
LGTM @lokesh-vadlamudi!
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Need lacework_integration_guid variable in output for self deployment automation.
for azurerm_role_assignment or other azurerm resources where you specify a principal_id, Azure ARM expects the object ID GUID, not the resource ID path.
so changed:
- principal_id = azuread_service_principal.data_loader[0].id to
+ principal_id = azuread_service_principal.data_loader[0].object_id
Since azure roles take few seconds to propogate, sometimes when we are creating integration in lacework platform, it throws error 400.
How did you test this change?
Tested locally, Subscription-SIngle region
Issue