You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered some issues with the CD3 export of load balancer routing policies from our OCI Tenancy. The imported Terraform configuration doesn't accurately reflect the actual infrastructure for certain aspects of the routing rules. Here are the main problems I've identified:
Truncation of Complex Conditions:
For rules with numerous path conditions, the CD3 import truncates the list. For example:
Imported (truncated):
condition="any(http.request.url.path sw (i '/Path1'), http.request.url.path sw (i '/Path2'), http.request.url.path sw (i '/Path3'),"
Actual (full condition):
condition="any(http.request.url.path sw (i '/Path1'), http.request.url.path sw (i '/Path2'), http.request.url.path sw (i '/Path3'), http.request.url.path sw (i '/Path4'), http.request.url.path sw (i '/Path5'), ...)"
Missing backend_set_names:
Some rules have their backend_set_names incorrectly omitted in the CD3 import. For instance:
Imported:
{
condition ="any(http.request.url.path sw (i '/SomePath'))"
name ="route_example"
backend_set_name =""
}
Actual:
{
condition ="any(http.request.url.path sw (i '/SomePath'))"
name ="route_example"
backend_set_name ="ExampleBackendSet"
}
Incomplete Conditions:
In some cases, only the beginning of a condition is captured. For example:
Imported:
condition="any("
Actual:
condition="any(http.request.url.path sw (i '/Path1'), http.request.url.path sw (i '/Path2'), ...)"
These inaccuracies require manual intervention to correct the Terraform configuration after using CD3 for export.
Environment details:
OCI provider version: 6.3.0
Terraform version: v1.7.1
Steps to reproduce:
Use CD3 to export resources from OCI Tenancy
Check the exported Terraform configuration for load balancer routing policies
Compare with the actual infrastructure using terraform plan
Expected behavior:
CD3 should accurately capture all aspects of the load balancer routing policies, including full conditions and correct backend_set_names.
Actual behavior:
The exported configuration has truncated conditions, missing backend_set_names, and in some cases, incomplete conditions.
The text was updated successfully, but these errors were encountered:
Hello,
I've encountered some issues with the CD3 export of load balancer routing policies from our OCI Tenancy. The imported Terraform configuration doesn't accurately reflect the actual infrastructure for certain aspects of the routing rules. Here are the main problems I've identified:
Truncation of Complex Conditions:
For rules with numerous path conditions, the CD3 import truncates the list. For example:
Imported (truncated):
Actual (full condition):
Missing backend_set_names:
Some rules have their backend_set_names incorrectly omitted in the CD3 import. For instance:
Imported:
Actual:
Incomplete Conditions:
In some cases, only the beginning of a condition is captured. For example:
Imported:
Actual:
These inaccuracies require manual intervention to correct the Terraform configuration after using CD3 for export.
Environment details:
Steps to reproduce:
terraform plan
Expected behavior:
CD3 should accurately capture all aspects of the load balancer routing policies, including full conditions and correct backend_set_names.
Actual behavior:
The exported configuration has truncated conditions, missing backend_set_names, and in some cases, incomplete conditions.
The text was updated successfully, but these errors were encountered: