specification class to have optional cloud path s3 - #571
Merged
pooleycodes merged 7 commits intoJul 1, 2026
Conversation
pooleycodes
marked this pull request as ready for review
June 30, 2026 13:49
tombrooks248
approved these changes
Jun 30, 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
This PR migrates Specification to use cloudpathlib.AnyPath so it can load specification files directly from S3 as well as local paths. It also adds pre load to issue-type.csv, this allows async to not have to try and import cloudpathlib as well.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Tested by changing Async to point to this branch and load files using both local and S3.
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.