Add Suppression Rules Support

[t1edtke]

This pull request introduces support for managing and interacting with suppression rules and closes #260.

Features:

1. Plugin Framework provider
   Introduced a new provider based on the Terraform Plugin Framework. The existing SDKv2 provider was muxed with the new provider to ensure backward compatibility.
2. Suppression Rule Data Source
   Added a new read-only data source suppression_rules, allowing users to fetch and interact with existing suppression rules.
3. Suppression Rule Resource
   Introduced a suppression_rule resource that allows users to manage newly created or existing suppression rules.
4. API client extension with suppression rule calls
   Implemented the following methods in the AquaSec client:
   • GetSuppressionRules(): Retrieve all suppression rules.
   • GetSuppressionRule(id): Fetch a specific suppression rule by ID.
   • CreateSuppressionRule(data): Create a new suppression rule.
   • UpdateSuppressionRule(id, data): Update an existing suppression rule.
   • DeleteSuppressionRule(id): Delete a suppression rule.
   • ActivateSuppressionRule(id): Activate a suppression rule.
   • DisableSuppressionRule(id): Disable a suppression rule.

Examples:

# Example of using suppression_rule resource
resource "aquasec_suppression_rule" "example" {
  name = "example-suppression-rule"
  application_scopes = ["Global"]
  scope = {
    expression = "v1"
    variables = [
      {
        attribute = "aqua.registry"
        value = "\"Docker Hub\""
      }
    ]
  }
  score = []
  severity = ""
  fix_available = "false"
  vulnerabilities = "CVE-2016-1000027,CVE-2014-9515,CVE-2021-41411"
  expiry = 370
  comment = "Check Risk 123"
  status = true
}

# Example of using suppresion_rule data source
data "aquasec_suppression_rules" "all" {}

output "suppression_rules" {
  value = { for rule in data.aquasec_suppression_rules.all.suppression_rules : rule.id => rule.name }
}

Commits:

• fix(client): Clone gorequest in GetCspAuthToken
• feat(suppression_rules): Add CRUD methods to client
• feat(suppression_rules): Add and mux additional plugin-framework provider
• feat(suppression_rules): Add suppression_rule data source
• feat(suppression_rules): Add suppression_rule resource
• doc(suppression_rules): Add documentation and examples

[CLAassistant]

All committers have signed the CLA.

[semyonmor]

@t1edtke
Is there any reason why you decided to put your changes under an internal provider?
FYI @KoppulaRajender

[semyonmor]

Is there any reason why you decided to put your changes under an internal provider?

[semyonmor]

Is there any reason why you decided to put your changes under an internal provider?

[t1edtke]

Is there any reason why you decided to put your changes under an internal provider?

Thank you for your feedback.

The main reason behind my decision is that I chose to implement the new features using the terraform plugin framework. This is the most recent SDK that is easier to use and more extensible than SDKv2.

However, there is a separate package required for this. I chose the internal/provider location as it’s the default location, isn’t it?

Would you like this to be changed?