Release Atlas 0.6.2: external Photon readiness and coverage - #58
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Atlas 0.6.1 can report an external Photon as down when its container record is stale, even while Photon responds successfully. Atlas 0.6.2 checks the configured Photon's live
/statusendpoint for geocoding readiness. Operators can declare external Photon coverage withPHOTON_COVERAGE_REGIONSwhen Atlas cannot inspect the imported dataset; local provenance takes precedence. The release also includes the already merged Valhalla coverage declaration.Validation:
mix precommit(803 tests, 0 failures), deployment config tests, both Compose configurations, and release-note parser.