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
Kubefirst currently natively supports Terraform as its IaC engine. I would love to see Pulumi offered as an alternative, especially since I migrated most of my current infra stacks from TF to Pulumi.
It would be nice to have pluggable architecture options for other parts of the Kubefirst ecosystem (IaC included, naturally), much like the option of GitHub and GitLab feature support (CI runners, container registry, etc.).
Is this missing feature preventing you from using kubefirst?
Yes
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
For now there is no plan to offer Terraform alternatives, but we will use this issue to gage the community interest. Note that with the latest license changes from HashiCorp, it does not affect Kubefirst, nor our community so far, but we are keeping our eyes on the situation, as it may be one reason we move away or offer Terraform alternatives.
What is your feature idea?
Kubefirst currently natively supports Terraform as its IaC engine. I would love to see Pulumi offered as an alternative, especially since I migrated most of my current infra stacks from TF to Pulumi.
Note that Pulumi has native support for migrating Terraform HCL to Pulumi source code, which may be useful if this is integrated.
Why is it needed?
It would be nice to have pluggable architecture options for other parts of the Kubefirst ecosystem (IaC included, naturally), much like the option of GitHub and GitLab feature support (CI runners, container registry, etc.).
Is this missing feature preventing you from using kubefirst?
Code of Conduct
The text was updated successfully, but these errors were encountered: