-
Notifications
You must be signed in to change notification settings - Fork 85
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
Support non-cloud, no CNA #51
Comments
We would like to see this as well. I just wrote a bunch of HCL and then realized that this is required - we do not have it nor am I aware of any need for it here. Currently we're doing everything with the wapi that we need via rest calls. |
Same. We aren't using extensible attributes in Infoblox. I had to comment out the EA references in the code to get it to work in our environment. |
The thing is all our plugins written in go uses our go library and if we change the library , it will break the other plugins. you can just manually create those 4-5 EA's in NIOS instead of making changes in NIOS |
It would be great to make those conditional. Kind of a poor design without that in mind.
I don't like the names you guys used. Not everything is for a VM or cloud related.
Currently i am commenting these lines out to bypass your EA restrictions (I'm only using IPAllocation, A & PTR records currently).
In the future, if this project becomes an official Terraform provider, I would hope to not have to make these changes. |
I still had some problems after commenting out those lines. Turns out i was able to get this to work by adding the required extensible attributes into infoblox. Go to Administration > Extensible Attributes and then add these as strings: Then i rebuilt the provider using a new copy (no changes) and it successfully worked. |
Now the feature is available at |
This provider still depends on cloud ea (tenantid and other attributes), will this provider support non-cloud? Can we have a option to omit cloud attributes and not be required? I know this would be a change to the dependent go infoblox client as well, is this something that can be enhanced from both the go client and this provider?
The text was updated successfully, but these errors were encountered: