Skip to content
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

[infoblox provider] hability to configure basepath of wapi call #4435

Closed
mcarbonneaux opened this issue May 6, 2024 · 3 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@mcarbonneaux
Copy link

mcarbonneaux commented May 6, 2024

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/.

@mcarbonneaux mcarbonneaux added the kind/feature Categorizes issue or PR as related to a new feature. label May 6, 2024
@mcarbonneaux mcarbonneaux changed the title [infoblox provider] [infoblox provider] hability to configure basepath of wapi call May 6, 2024
@jcralbino
Copy link

jcralbino commented Jun 12, 2024

Hello

I am also a user of the infoblox integration, and i wanted to let you know that it seems that the infoblox provider in-tree was removed in version 0.14.2, removal of infoblox commit

So i assume you need to place this in the infoblox provider repository instead of this one?

https://github.com/AbsaOSS/external-dns-infoblox-webhook

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 10, 2024
@mcarbonneaux
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants