-
Notifications
You must be signed in to change notification settings - Fork 6
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
[feature request] hability to configure basepath of wapi call #18
Comments
Hi @mcarbonneaux. Thank you for asking and I agree with your requirement. This is unfortunately hardcoded in infoblox-go-client and I'm afraid that it cannot be changed in a simple way on our side. |
i've post feature request on infoblox go client her : infobloxopen/infoblox-go-client#238 |
i've made pull request : infobloxopen/infoblox-go-client#239 |
Hi @mcarbonneaux , awesome job! When I have some time, I'll try to see if we can incorporate it on our side. Thank you! |
note: @k0da , once infobloxopen/infoblox-go-client#239 has been merged (ideally released) into infoblox-go-client, we will be able to release extended configuration with the basepath. |
What would you like to be added:
can be possible to add new environement variable to permit to set basepath before /wapi like //wapi.
Why is this needed:
i need to use infoblox api behind api gateway, and i'm oblige to add /api before /wapi (/api/wapi), and actualy is not possible to configure infoblox provider to change base path of the /wapi/, like //wapi/.
The text was updated successfully, but these errors were encountered: