-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenTF support #562
Comments
This FAQ is indeed good news for now, but maybe another point after yet more time would be abandon HashiCorp's registry at all, but of course with no rush about it (ideally after living in dual registry world for a while when most of users would theoretically use new FOSS registry). For now imo this is completely ok to use it, but they well... proved to be rather... unstable in keeping their own statues :), so this would be kinda not very surprising for me to see above 9. in FAQ evaporated in incoming months or something after they change their mind, because afaik BSL allows to "force" derived software to change their license model(?). |
Remaining action items:
|
No more work planned / needed on this, closing |
From a technical perspective, I expect that it will be a no-op for the time being as OpenTF anticipates maintaining compat/interop for the foreseeable future.
However, When there is a first official OpenTF release we should be able to:
The text was updated successfully, but these errors were encountered: