It would be beneficial for the Kestra Terraform provider to support authentication methods other than basicAuth and the built-in JWT. Kestra seems to only support those two methods (or no auth) whether the user is using EE or OSS versions.
In many scenarios, there are additional layers between Terraform and the Kestra instances. Many organizations have user and access management outside of their applications and services. In our case, we have Cloudflare Access in front of Kestra. This means we are unable to use Terraform to provision or manage Kestra because there is no way to handle the tokens required for access.
An ideal solution would be for the Kestra provider to have support for adding additional headers to it's connection. This would allow Kestra to fully integrate with almost any existing authentication framework in their infrastructure. It could potentially look something like this...
Feature description
It would be beneficial for the Kestra Terraform provider to support authentication methods other than basicAuth and the built-in JWT. Kestra seems to only support those two methods (or no auth) whether the user is using EE or OSS versions.
In many scenarios, there are additional layers between Terraform and the Kestra instances. Many organizations have user and access management outside of their applications and services. In our case, we have Cloudflare Access in front of Kestra. This means we are unable to use Terraform to provision or manage Kestra because there is no way to handle the tokens required for access.
An ideal solution would be for the Kestra provider to have support for adding additional headers to it's connection. This would allow Kestra to fully integrate with almost any existing authentication framework in their infrastructure. It could potentially look something like this...