EES-XXXX - enabling Public Data DB connection on Dev for Admin and Publisher #4927
Conversation
This file contains 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
N-moh
approved these changes
Jun 5, 2024
duncan-at-hiveit
deleted the
EES-XXXX-allow-public-data-db-connection-on-dev
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR will allow Admin and Publisher to start using the Public Data DB connection on Dev.
As far as Admin goes, it'll use this endpoint for populating part of the Release Checklist (to make sure that there are no non-complete Public API Data Set imports) as well as dedicated Public API work like the new tab, and as far as Publisher goes, it'll use this connection to publish Data Sets along with the Releases / amendments as they go live.