feat(albwaf): onboard WAF - #1612
Conversation
6cbea1f to
3a169c3
Compare
d9fa9f6 to
5b601ad
Compare
5b601ad to
ff1b28b
Compare
| //go:embed testdata/managed-rule-set.tf | ||
| managedRuleSetConfig string | ||
| //go:embed testdata/resource-max.tf | ||
| wafConfig string |
There was a problem hiding this comment.
In the acc tests the resources should be in independent tests. So for the managed rule set, it should remain like before and for the new waf_configuration, there should be a new test terraform config added with a separate test function.
Otherwise it will be difficult in the future to maintain it, when the test config grows with each new resource. In the new test config for waf_config, you can also add a waf_managed_rule_set. But there you don't need to add checks for the waf_managed_ruleset.
See for example the test configs of kms: https://github.com/stackitcloud/terraform-provider-stackit/tree/770998656083e829003cc3ed1c067739cc3033d3/stackit/internal/services/kms/testdata
There was a problem hiding this comment.
I see. I re-added the deleted test and minimized the checks for waf managed rule set from the max test
fc9d078 to
1a97b9b
Compare
Relates to STACKITTPR-749
Relates to STACKITTPR-749
Relates to STACKITTPR-749
Relates to STACKITTPR-749
Relates to STACKITTPR-749
Relates to STACKITTPR-749
1a97b9b to
b8e6408
Compare
Merging this branch changes the coverage (1 decrease, 1 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
Relates to STACKITTPR-749
Description
Onboards WAF
Checklist
make fmtexamples/directory)make generate-docs(will be checked by CI)make test(will be checked by CI)make lint(will be checked by CI)