imperva_cloud_waf: clarify imperva file compression configuration

[efd6]

Proposed commit message

See title.

Apparently it is possible for people to interpret the original text as a conditional imperative rather than an imperative with an explanatory clause as is intended, resulting in incorrect configuration.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

��� Build Succeeded

• Buildkite Build
• Commit: 6e31946

cc @efd6

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[chrisberkhout]

Both look okay to me. I guess we'll see if the new one works better.

I wonder if the "Compress logs." at the start of the line is being misinterpreted. It could be "Log compression." which might be clearer for the documentation but might not match the UI anymore.

[efd6]

Yeah, I found it hard to misinterpret the original, but it was possible.

[elastic-vault-github-plugin-prod]

Package imperva_cloud_waf - 1.10.2 containing this change is available at https://epr.elastic.co/package/imperva_cloud_waf/1.10.2/