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
Is your feature request related to a problem? Please describe.
Terramate currently lacks support for block-typed configuration in generated providers, only supporting argument-based configuration. This limitation is problematic when working with providers like AWS and Helm, where block-typed configurations (e.g., assume_role in AWS, kubernetes in Helm) are necessary. The absence of block support forces users to work around the limitation or manually configure these providers, reducing the automation benefits of Terramate.
provider"helm" {
kubernetes { // Not supportedhost=data.aws_eks_cluster.cluster.endpointcluster_ca_certificate=base64decode(data.aws_eks_cluster.cluster.certificate_authority[0].data)
token=data.aws_eks_cluster_auth.cluster.token
}
}
provider"aws" {
assume_role { // Not supportedrole_arn=""
}
}
Describe the solution you'd like
I would like Terramate to support block-typed configuration for generated providers
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
As @krystek17 pointed out, you can customise the provider's generate block to also generate specific inner blocks based on a configuration condition.
The annoying part is that you cannot just configure blocks in a generic way.
We are looking into options to make that possible but HCL syntax is quite limited in this regard.
Is your feature request related to a problem? Please describe.
Terramate currently lacks support for block-typed configuration in generated providers, only supporting argument-based configuration. This limitation is problematic when working with providers like AWS and Helm, where block-typed configurations (e.g.,
assume_role
in AWS,kubernetes
in Helm) are necessary. The absence of block support forces users to work around the limitation or manually configure these providers, reducing the automation benefits of Terramate.Describe the solution you'd like
I would like Terramate to support block-typed configuration for generated providers
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: