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.
The Terraform provider needed to set the create_default_rules flag based on whether the firewall was created with default rules, especially during terraform import.
I added a function in the Civo SDK (firewall.go) that checks whether a firewall is using default rules by comparing the actual firewall rules with predefined default rules (e.g., allowing SSH, HTTP, and HTTPS traffic).
In the Terraform provider (resource_firewall.go), I modified the logic to call this function during resource creation and import. This ensures that the create_default_rules flag is accurately set in the Terraform state based on the current firewall rules.
Now, when a firewall is created or imported, the provider checks if default rules are used and sets the create_default_rules flag accordingly, preventing misconfiguration and ensuring consistency between the actual firewall state and Terraform's state.