fix: lacework_agent_configuration type #63
Merged
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
The keyword map is a shorthand for map(any), which accepts any element type as long as every element is the same type. This is for compatibility with older configurations; for new code, we recommend using the full form.
Need to change variable type of
lacework_agent_configuration
from a collectionType to a structuralType. This means defining specific object attributes.My best attempt at finding documented agent configuration Configure Linux Agent Behavior in config.json File | Lacework Documentation. There are a lot more nested objects that are supported. Even the TF examples contains an undocumented variable
privileges
.Therefore I am proposing changing the type to
any
.How did you test this change?
Local testing with
terraform validate
andterraform plan
.Example
main.tf
attached to Jira ticket. With this change:Issue
LINK-1111