fortios_vpncertificate_local forces privatekey usage

[tiagoasousa]

Any reason for the provider to enforce private key where the api does not ? this blocks creation of letsencrypt certs

via api it works well: curl -X POST "https://fg-address/api/v2/monitor/vpn-certificate/local/import?access_token=TOKEN" -H "accept: application/json" -H "Content-Type: application/json" -d "{"acme_ca_url": "https://acme-v02.api.letsencrypt.org/directory","acme_domain": "url","acme_email": "email","certname": "arroz","scope": "global","type": "automated"}"

but provider enforces privatekey so it breaks. can it be updated?

[lix-fortinet]

Hi @tiagoasousa,

Thank you for raising this issue. Team are working on this issue. We will let you know once it's resolved.

By the way, the REST API for resource fortios_vpncertificate_local is /api/v2/cmdb/vpn.certificate/local, not /api/v2/monitor/vpn-certificate/local/import.

Thanks, Xing

[lix-fortinet]

Hi @tiagoasousa,

The latest version of FortiOS Terraform provider v1.14.1 fixed this issue. Please switch to v1.14.1 and try it again.

Please let me know if you have any questions.

Thanks, Xing

[lix-fortinet]

Hi @tiagoasousa,

We will close this issue since it has been fixed. Feel free to open a new issue if you have any other questions.

Thanks, Xing