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

Feature Request: Support Fallback director type via fastly_service_v1 director attribute #436

Open
cwanda opened this issue Jun 29, 2021 · 1 comment
Labels
enhancement New feature or request feature request requires internal discussion The issue/PR requires further internal discussion to understand if it's appropriate for the project. revisit Revisit the issue once a separate change/feature is merged.

Comments

@cwanda
Copy link

cwanda commented Jun 29, 2021

Currently we specify directors in our VCL specifications and use Fallback director for some.
Is it possible to specify Fallback director via the fastly_service_v1 director attribute?

The documentation indicates the supported types are: 1(Random), 3(Hash), 4 (client) and the code matches the documentation(aware that round robin has been retired)

@smaeda-ks
Copy link
Contributor

Hi @cwanda, unfortunately, creating a fallback director is not even supported at our public API yet:
https://developer.fastly.com/reference/api/load-balancing/directors/director/

and that the fastly provider that's relying on our the public APIs also cannot support it. The only workaround at the moment is to use VCL snippets and define a fallback director manually.

We're tracking it internally as a feature request, but in the meanwhile, I also encourage you to subscribe: https://developer.fastly.com/changes/

@Integralist Integralist added enhancement New feature or request requires internal discussion The issue/PR requires further internal discussion to understand if it's appropriate for the project. revisit Revisit the issue once a separate change/feature is merged. labels Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request requires internal discussion The issue/PR requires further internal discussion to understand if it's appropriate for the project. revisit Revisit the issue once a separate change/feature is merged.
Projects
None yet
Development

No branches or pull requests

3 participants