Closed leonardoauribe closed 1 year ago
Hi @leonardoauribe,
Thank you for raising this issue. Team is working on this issue. We will fix it in the next release.
Thanks, Xing
Has there been any progress made with this issue?
Hi @leonardoauribe,
We will have a new release in early Feb which will fix this issue.
Thanks, Xing
Has there been a date identified for the new release? We are still running into issues. thanks!
Hi @leonardoauribe , This issue has been fixed in Terraform FOS provider version 1.17.0, please check it out. I will go ahead to close it, if the issue still occurs, you are free to reopen it or open another case.
I use hosts in an isolated environment to configure Fortigate firewalls via Terraform. I've upgraded to the latest provider v1.16.0 and noticed a change in behavior compared to the previous version I was running, 1.14.1. The latest version of fortios provider leverages proxy environment variables for forwarding traffic. It appears to have been introduced in v1.15. This configuration is fine for access to AWS services like S3, but traffic destined to the Fortigates themselves we want direct access. This traffic shouldn't require a proxy and is being denied at the proxy as designed. I would like to request the following;
We have rollback to v1.14.1 for the time being until we figure out a better solution.
Similar issues found: https://github.com/fortinetdev/terraform-provider-fortios/issues/229 https://github.com/hashicorp/terraform/issues/17386
Error