State of the provider

[davidwinderlTNG]

Hello,

I just wanted to know the current development state of the provider.

There are some dependabot PRs (unanswered and unmerged) and the last commit has been a few years ago.

Is it still advisable to use this library in a software-stack (will it be further maintained) or shall we look for alternatives?

[Malet]

I’ve spun up an alternative heavily inspired by the shell provider (and mostly compatible with some small interface changes) to address some issues I was facing for a client, the main ones being:

• inability to import existing resources
• lack of proper diffs in plans (is_dirty wasn’t verbose enough)
• hard to develop the lifecycle hooks without TF_LOG

I’ve resolved these issues, and it’s written in the new provider framework: https://github.com/customcrud/terraform-provider-customcrud
On the roadmap is the ability to use write only attributes, and to have custom ephemeral resources. I’m already using it in production and welcome any bug reports or feature requests.

[stevehipwell]

I've also created a shell provider using the new Terraform plugin framework, terr4m/shell. It was inspired by this provider rather than a direct copy. The highlights of terr4m/shell would be:

• Simple output logic inspired by GitHub Actions
• Output is dynamic type (Terraform diff works correctly)
• Output in state can be accessed by script
• Script can hook into Terraform logging
• Supports multi-platform usage (GOOS based)
• Scripts can be modified alongside other inputs