chore: add the optional queryLanguage enum value where used
#625
Conversation
This file contains 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
gspofford-lw
force-pushed
the
georges/add-query-language-for-queries
branch
from
6410186 to
1ddb765
Compare
…used This change adds the `queryLanguage` enumeration to the lacework_query and lacework_policy_compliance resource types. For a query, it is an optional part of the create submission. It is also an optional part of query payload response from the result of creating, updating, or retrieving the definition of a query. For a policy, it is an optional part of the response from creating, updating or retrieving the definition of a policy.
…used This change adds the `queryLanguage` enumeration to the lacework_query and lacework_policy_compliance resource types. For a query, it is an optional part of the create submission. It is also an optional part of query payload response from the result of creating, updating, or retrieving the definition of a query. For a policy, it is an optional part of the response from creating, updating or retrieving the definition of a policy.
gspofford-lw
force-pushed
the
georges/add-query-language-for-queries
branch
from
1ddb765 to
96b2bbb
Compare
PengyuanZhao
reviewed
Apr 9, 2024
Ensuring that it is populated from compliance policy responses. Adding the value to policy (violation policies) responses as well. This is for more-complete information purposes. It is only valid at this time to create a violation policy with LQL.
Ensuring that it is populated from compliance policy responses. Adding the value to policy (violation policies) responses as well. This is for more-complete information purposes. It is only valid at this time to create a violation policy with LQL.
gspofford-lw
force-pushed
the
georges/add-query-language-for-queries
branch
from
58151f7 to
dde37aa
Compare
1. Ensure that query_language is handled identically for policy and policy_compliance resources 2. Add query_language to variable and output in main.tf
1. Ensure that query_language is handled identically for policy and policy_compliance resources 2. Add query_language to variable and output in main.tf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue: https://lacework.atlassian.net/browse/RAIN-93039
Description:
This change adds the
queryLanguageenumeration to the lacework_query and lacework_policy_compliance resource types.For a query, it is an optional part of the create submission. It is also an optional part of query payload response from the result of creating, updating, or retrieving the definition of a query.
For a policy, it is an optional part of the response from creating, updating or retrieving the definition of a policy.
Additional Info:
Include any other relevant information such as how to use the new functionality, screenshots, etc.