fix: rename availability to environment - #193
Merged
Merged
Conversation
This was referenced Jun 19, 2026
tombrooks248
marked this pull request as ready for review
June 22, 2026 07:52
Ben-Hodgkiss
approved these changes
Jun 22, 2026
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
2 participants
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.
What type of PR is this? (check all applicable)
Description
Rename the
availabilityfield to beenvironmentRemove the migrate-dataset-availability.py as no longer needed.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
QA completed
I ran a script locally to check the rebuilt dataset.csv keeps the same values under the new environment column (116 production, 163 empty) as it was doing before.
I have verified spec changes by running airflow-dags' real DAG-generation logic (get_collections_dict + filter_collections_for_env) locally against both the current spec dataset.csv (availability) and the renamed branch CSV (environment), and confirmed the generated collection→dataset maps are identical across development, staging and production.
The Sister PR in airflow-dags has now been merged and pushed to production. So this one is now safe to merge.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?