Closed istr closed 2 years ago
@ross This issue should be transferred to https://github.com/octodns/octodns-constellix now.
@ross This issue should be transferred to https://github.com/octodns/octodns-constellix now.
👍. I have a TODO on my list to go through after all the extractions and move all the issues that now belong in module-specific repos.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.
The optional
fallback
for the global value(s) in adynamic
setup seems to be set implicitly in the constellix provider. Expected behavior for the failing test-case: no fallback will be set / existing fallback entries will be removed. Observed behavior for the failing test-case: fallback "eu" is set implicitly, so there is always a difference betweenconfig.yml
(fallback: None
) and constellix provider (fallback: eu
) that leads to an update on every run.My suspicion is, that the implementation uses the
fallback
mechanism to construct the necessary "World filter", instead of using the givenvalues
for the record. A test case that provides only pools with geo (no catch-all pool) fails as well.My expectation would be that a setup without a catch-all pool constructs the "world" filter from the
values
and does not set fallback values on each pool.As per documentation the "global" fallback constructed from the
values
is handled differently (unmonitored) than a catch-all pool used as a fallback. From that I conclude that these cases should be handled differently. I would expect all following test cases to work and to construct the "world" fallback from thevalues
in any case. When not configured, implicit fallback entries should not be generated.Working test-case (all pools set a fallback, the fallback pool is a catch-all pool):
Failing test-case (a catch-all pool is given, an implicit fallback is constructed for all other pools and leads to a mismatch between constellix and config):
Failing test-case (no catch-all pool is given, the API request fails, because no "World" record is constructed at all):
Error message for this test-case: