Comment

Comment by cube2222

Hey!

> The first is, please provide a standalone registry package for both modules and providers - the only I'm aware of is Artifactory, and I don't really feel like running another big repository software in a Nexus shop.

Could you expand on this? Do you mean you'd like a self-contained binary to run a private provider/modules registry? If that's the case, then there are some open source projects for that, and we've done a proof of concept of an approach in which you can distribute providers via OCI registries like DockerHub or the GitHub Container Registry[0] as those are actually perfect for the use-case.

This PoC will be followed by a public RFC soon.

> The second is related: please allow for easier forking of provider modules. The current workflow of either building locally and distributing binaries with collaborators that are manually copied sucks or waiting for upstream to accept PRs, particularly if upstream wants CLAs signed.

Do you possibly have an ideal workflow in mind?

[0]: https://twitter.com/opentforg/status/1696913055576387599

Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the OpenTF Project, until it's committee-steered.

parent cube2222 3 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton