you are viewing a single comment's thread
view the rest of the comments
[โ€“] 13 points 2 years ago* (last edited 2 years ago) (4 children)

Turns out that IBM is leading OpenTofu efforts. Nevermind, it's OpenBao they are working on (Hashicorp Vault FOSS fork), we might just be done here.

Also Pulumi is technically fucked too. Back to good old shell scripting boys

  • source
  • hideshow 8 child comments
  • [โ€“] 29 points 2 years ago (2 children)

    Turns out that IBM is leading OpenTofu efforts.

    IBM is in no way involved in OpenTofu. Afaik they are involved in OpenBao.

    Source: I'm the technical lead of the OpenTofu project.

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] 4 points 2 years ago (2 children)

    Isn't Pulumi moving to native API stuff instead of the tf provider?

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] 2 points 2 years ago (1 child)

    They wish. Nobody is gonna replicate that effort successfully any time soon.

    Youโ€™d sooner get the cloud providers to standardize on an api.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 3 points 2 years ago (2 children)

    I mean, they have AWS Native (in preview) and Azure Native. So it's a little more substantial than a wish.

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] 2 points 2 years ago

    Crossplane has also had internal providers in development for 3 years. Bottom line is unless the actual cloud provider is devoting developer resources to a provider(like they do for the TF providers), it's unlikely to happen.

  • source
  • parent
  • [โ€“] [S] 1 point 2 years ago* (1 child)

    I guess I need to start looking deeper into this, and the potential for importing existing infrastructures into pulumi's purview. But I'm hesitant - I don't want pulumi to pull a Hashicorp. I'm wondering if it's best to just go with CFN and Bicep.

  • source
  • parent
  • hideshow 2 child comments