-
Notifications
You must be signed in to change notification settings - Fork 67
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
Still being worked on? #69
Comments
I'm also interested in the state of this project. We began the work to adopt this generator and are getting ready to use it. We've run into some problems that have been reported here and on other projects adopting this generator. #28 , #66 , #65. I understand that the original author is no longer associated with the org. |
Hey y'all, I communicated this some privately, but to put it on the record here publicly: This project is something we're still interested in. We still, as a team, think it's a good idea and a promising direction for Terraform provider development tooling. Projects involving it are in our roadmap. Unfortunately, we're a very small team, and so we need to make some difficult choices about what we work on sometimes. In this case, we all agree this is a useful and good tool, and want to do it justice. However, we have a couple of more high-impact initiatives that we need to address first before we can give this tooling the attention it deserves. I'm eager for us to work on some of the tooling surrounding Terraform provider development, too, but we have to focus our energies where they'll do the most good for Terraform provider developers first and foremost. We have no official timeline for when we'll have room in our roadmap to actively maintain this tooling the way we'd like to. If I were to personally, unofficially, finger-to-the-wind, back-of-the-napkin guess as to when it would happen, I would put a vague "end of the year" circle on my calendar, as that's where it fits in my head at the moment. But that's subject to change from the higher-impact initiatives taking more time than anticipated, other priorities coming up, team changes, shifts in strategy or direction, etc. and should not be considered a promise or a target date. I just want to give people a ballpark of the timeframe we're talking about here. |
Thanks @paddycarver, no problem, that's what I hoped really (de-prioritised as opposed to dropped). |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Hi, I'm just curious if
tfplugindocs
is still being worked on?Just slightly worried to notice no commits for several months when quite active previously, except moving an Action from @paultyng's repo to Hashicorp's; that not authored or committed by him (instead @smacfarlane), who was previously the committer on almost all and authored most.
Thanks! 🤞🏻 it's nothing, just a priority shift 🙂
The text was updated successfully, but these errors were encountered: