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
Describe the bug
While testing [https://community.f5.com/kb/technicalarticles/f5-hybrid-security-architectures-part-5---f5-xc-big-ip-apm-cis-and-nginx-ingress/320168]
NGINX App Protect output "external_name" is not getting populated in Terraform Cloud outputs. Resulting in the below error in the run.
│ Error: Error in function call │ │ on ingress.tf line 9, in resource "kubernetes_ingress_v1" "***-ingress": │ 9: host = try(data.tfe_outputs.nap[0].values.external_name, data.tfe_outputs.nic[0].values.external_name) │ ├──────────────── │ │ while calling try(expressions...) │ │ Call to function "try" failed: no expression succeeded: │ - Unsupported attribute (at ingress.tf:9,48-62) │ This object does not have an attribute named "external_name". │ - Unsupported attribute (at ingress.tf:9,94-108) │ This object does not have an attribute named "external_name". │ │ At least one expression must produce a successful result.
To Reproduce
Steps to reproduce the behavior:
Configure github and Terraform cloud with variables and tokens mentioned in the article
Create/navigate to branch deploy-xcbn-cis, and configure infra/terraform.tfvars accordingly
Push the changes to trigger the run
Infra, EKS, BIGIP base, BIGIP CIS, NAP were successful
One of the outputs created from NAP run is not accessible to ARCADIA runs
Expected behavior
Output "external_name" should have been populated in terraform cloud and logs under NAP.
Screenshots
Desktop (please complete the following information):
OS: mac
Browser: chrome
Version 130.0.6723.59
Smartphone (please complete the following information): NA
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Also, instead of creating new nginx-service the run is only refreshing the already existing resource even though no resource is available in the region.
The text was updated successfully, but these errors were encountered:
Describe the bug
While testing [https://community.f5.com/kb/technicalarticles/f5-hybrid-security-architectures-part-5---f5-xc-big-ip-apm-cis-and-nginx-ingress/320168]
NGINX App Protect output "external_name" is not getting populated in Terraform Cloud outputs. Resulting in the below error in the run.
│ Error: Error in function call │ │ on ingress.tf line 9, in resource "kubernetes_ingress_v1" "***-ingress": │ 9: host = try(data.tfe_outputs.nap[0].values.external_name, data.tfe_outputs.nic[0].values.external_name) │ ├──────────────── │ │ while calling try(expressions...) │ │ Call to function "try" failed: no expression succeeded: │ - Unsupported attribute (at ingress.tf:9,48-62) │ This object does not have an attribute named "external_name". │ - Unsupported attribute (at ingress.tf:9,94-108) │ This object does not have an attribute named "external_name". │ │ At least one expression must produce a successful result.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Output "external_name" should have been populated in terraform cloud and logs under NAP.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information): NA
Additional context
Also, instead of creating new nginx-service the run is only refreshing the already existing resource even though no resource is available in the region.
The text was updated successfully, but these errors were encountered: