Replies: 1 comment 5 replies
|
Hi @a1994sc, I think what you are suggesting is to publish all of the providers that live inside the Can you say more about what you would do with such packages if we published them? Since those providers are already all available from the OpenTofu Registry anyway it seems like this would just be a less convenient way to get the same result, and would require us to store an additional copy of each provider package. I don't mean this to say that we would not do it. I just want to understand what the benefit to you would be so we can evaluate whether it's worth the additional storage and build-time costs. Thanks! |
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
So with the release of
v1.10.0, OpenTofu now supports using OCI, Open Container Initiative, artifacts as mirrors for the provider and modules.ref:
provider-mirrorSo I wonder if there was any reason not to start to populate providers under
ghcr.io/opentofu/provider?At least following the docs linked above it would seem that you can add some logic around here in the
opentofu/scriptsthat looks like the following:The above actions are a very rough flow on how it would need be done so there maybe a bit of a better way to refine that action.
All reactions