feat: set 3 datasets to staging only - #194
Merged
Merged
Conversation
tombrooks248
force-pushed
the
feat/document-etc-staging-only
branch
from
June 22, 2026 14:05
97982a7 to
e49fdeb
Compare
tombrooks248
marked this pull request as ready for review
June 22, 2026 14:15
tombrooks248
changed the base branch from
fix/rename-availability-to-environment
to
main
June 22, 2026 14:23
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
Set
to only be available in staging and development
Why
Currently these 4 datasets (formed into 3 collections) exist as dags in DEV, STAGING and PROD, but there is some odd hard coding which prevents them from being included in the scheduled overnight pipeline run in PROD.
This hard coding was added a while ago when it became obvious that running these pipelines would take many hours , too long to be included in nightly pipeline run.
This change will make the dags only appear in DEV and STAGING and so will enable a future PR to remove the hardcoding. But also enable the pipelines to be tested in DEV/STAGING and possible improved for future use and promotion to PROD.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
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?