resource/alicloud_threat_detection_malicious_file_whitelist_config: support remark parameter - #10413
Open
api-tool-agent wants to merge 1 commit into
Conversation
…e_whitelist_config
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
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.
Adds the
remarkOptional string parameter to thealicloud_threat_detection_malicious_file_whitelist_configresource. The Remark parameter is supported by the CreateMaliciousFileWhitelistConfig and UpdateMaliciousFileWhitelistConfig APIs and allows users to attach a remark note to a whitelist rule.The parameter is set during Create and Update. Documentation and acceptance test coverage are updated accordingly.
Test Cases