-
Notifications
You must be signed in to change notification settings - Fork 4
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
cli tool to generate terraform resources & state from existing workspace #56
Comments
Thanks for the feedback and very happy to finally have a provider for the community! We will take this request into consideration 🙂 |
Same here, we'd love to use the provider without manually importing existing configurations. |
Hi @macnibblet and @mr8ock! Have you given https://developer.hashicorp.com/terraform/language/import/generating-configuration a try yet? I haven't had time to take it for a spin against the Segment provider yet, but it might just work out of the box. |
I have tried it. It requires a little massaging here and there to get running, but by and large it has let me migrate a lot of our stuff relatively painlessly. Some discipline is required to swap between dev, staging and prod envs, but you get in the swing of it pretty quickly. |
Hey just wanted to pop in here and let y'all know we just launched a feature called Git Sync to public beta that generates a real time config of your workspace in HCL, so it can be used to generate config for your terraform provider. Not all resources are currently supported, but we are actively working on adding more. |
Is your feature request related to a problem? Please describe.
Increased adoption of the terraform provider
Describe the solution you'd like
CLI Tool to generate terraform for existing WorkSpace as well as importing the existing state
Describe alternatives you've considered
Manually importing all sources/destinations, which would probably be very error-prone
Additional context
I have been waiting for two years for this provider, thank you so much for creating it!
The text was updated successfully, but these errors were encountered: