SAAS-29539 - Auto-Discovery | AWS | Single | Terraform | Split volume scanning deployment#16
SAAS-29539 - Auto-Discovery | AWS | Single | Terraform | Split volume scanning deployment#16
Conversation
… scanning deployment Resolves: SAAS-29539
|
|
Terraform Validation Results:Terraform Format Check ✅ Pusher: @noamshraga1, Action: |
|
bugbot run |
Resolves: SAAS-29539
Terraform Validation Results:Terraform Format Check ✅ Pusher: @noamshraga1, Action: |
|
Terraform Validation Results:Terraform Format Check ✅ Pusher: @noamshraga1, Action: |
Resolves: SAAS-29539
Terraform Validation Results:Terraform Format Check ✅ Pusher: @noamshraga1, Action: |
The PR adds a condition to all the volume scanning resources that are created during the AWS single account onboarding process.
This condition depends on a new variable called volume_scanning_deployment, which defaults to true and can be set to false.
If the variable does not exist or is set to true, onboarding will proceed as it does today — all volume scanning resources will be created as expected and volume scanning integration will be created in the Aqua console.
If the variable is set to false, none of the volume scanning-related resources will be created.
Note: When the variable is set to false, the regions variable is not relevant.
I also ran
terraform fmt -recursiveto format all the Terraform files in the directory.Resolves: SAAS-29539