Make base_uri dinamically configurable

Further clarification:
The list of available/preferred hosts (base_uri) are all safe in this usecase as the database to be queried is already public and shared.

Furthermore, the list changes over time, so it would be unpractical to maintain it has a fixed config yml rather than Drupal content that itself can be updated from an API (in case of public, active validators) or entered by the "providers" themselves (in case of business/partner nodes).

Dinamically selecting the base_uri would also help load balancing the public infrastructure and avoiding possible rate limits.

If this feature is too difficult to implement in this module, where would you suggest I look into? 🙏🏻

Idea & question:
I could set up redirects from the configured base url (keeping the path) to the different available sources (and rotate them with some business logic for load balancing). Would requests managed by this module still work and provide the result back to the action plugin?

Hi @kopeboy

I'm not an expert developer but reading from the related (closed) issue and seeing /admin/config/services/http-client-manager/settings, it seems to me this is still not possible.

Yes you actually can. I'm gonna upload a couple screenshots for you to see how to do it.

Alternatively please take a look at this patch and let me know if using tokens could be a solutions for you: ✨ Allow using tokens as base_uri value Fixed

Regards,
aronne

Yes, I had seen that option, but that was a manual, static, override.
Now that you fixed the linked issue, allowing token substitution, it seems I have a working solution :)
I'll test soon and let you know, thanks! 🙏🏻

Automatically closed - issue fixed for 2 weeks with no activity.