Closed deigaard closed 5 months ago
Hi @deigaard, thanks for providing such a detailed bug report!
It looks like the Terraform state is reporting an empty array for hosts, protocols and ports, while your Terraform configuration is setting them as null. I'll work on a fix this week.
In the mean time, to suppress these annoying errors, you can set these values for each rule on the oxide_vpc_firewall_rules
resource as an empty array on your configuration file where necessary, like this:
filters = {
hosts = []
ports = []
protocols = []
},
I gotta say, running terraform (or really anything with the Oxide system) is so fast that it was a pleasure to take a little bit of time to put together a decent, and repeatable bug summary.
Thank you for the workaround. It works great.
Thanks for the kind words!
Fix is implemented, will be part of the next release. Thanks for helping us improve our product :)
Preliminary checks
What was the expected behaviour
Per #219, when adding new firewall rules to a new, non-default VPC using terraform, I'm expecting that I need to re-create the existing, default firewall rules with a new terraform-provided copy of the default ones so that I can add some additional firewall rules.
In the end, I'm expecting to have the default rules plus the ones I add.
What is the current behaviour and what actions did you take to get there
When I attempt to do this with an already created VPC named
globus
, I'm getting the following results:However, I get an error for each firewall rule that says:
The terraform code that I'm using is:
The terraform apply plan looks like this:
Provider version
0.3.0
Terraform version
1.8.4
Operating system
darwin_arm64 - Mac
Anything else you would like to add?
No response