-
Notifications
You must be signed in to change notification settings - Fork 1
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
Bootstrapping #1
Comments
Hi @adamdonahue , Great to hear from you that this could be useful! This was a solo effort that gave me the basis of what I needed to get started with Dremio. Yes, the docs are basically non-existent, sorry about that! Now that I know there's interest I'll take a look at improving them! I've got my provider set up as: I haven't tried importing into state - I've just got it provisioning everything from scratch. The ids in general should match the ids you get from using the dremio api so hopefully that may work? Though if there's any additional import code required in the provider then that doesn't exist yet. Like I said, if you are interested in using this then I'll certainly help fix/document/give examples. Our current use case that we're running is setting up some sources, physical datasets, virtual datasets and reflections. |
Thanks for the quick reply. Importing isn't essential since we're deploying a fresh installation (Terraform reports import is not supported by the provider), but definitely eager to use and help improve it if possible. Let me see if I can get a data resource loaded to verify it's accessing the API correctly, but the URL is helpful. (I had a trailing I'll let you know how it goes. Adam |
Hello @saltxwater Would you have some examples, for example how to create a dataset from S3, etc... ? |
We'd like to use this provider for managing our Dremio objects, but the documentation is sparse.
Can you elaborate on the DREMIO_URL expected for the provider, as well as the IDs needed to import existing objects into state? (I can look through the code for these as well.)
The text was updated successfully, but these errors were encountered: