This repository was archived by the owner on Oct 27, 2025. It is now read-only.
Hide Content Publisher from publishers attempt two! [WHIT-2520]#3320
Merged
ChrisBAshton merged 1 commit intomainfrom Oct 27, 2025
Merged
Hide Content Publisher from publishers attempt two! [WHIT-2520]#3320ChrisBAshton merged 1 commit intomainfrom
ChrisBAshton merged 1 commit intomainfrom
Conversation
ChrisBAshton
changed the title
ChrisBAshton
force-pushed
the
hide-content-publisher-attempt-two
branch
from
0aab1d4 to
75b6c4b
Compare
GDSNewt
approved these changes
Oct 27, 2025
Quick and dirty way of making Content Publisher unavailable to publishers. We're about to run the migration script to copy all Content Publisher content into Whitehall, and we don't want publishers to then be able to go into Content Publisher and attempt to make edits to a now-migrated document. Follows on from #3318, where we accidentally clobbered the healthcheck endpoints, stopping Content Publisher from starting up! Jira: https://gov-uk.atlassian.net/browse/WHIT-2520
ChrisBAshton
force-pushed
the
hide-content-publisher-attempt-two
branch
from
75b6c4b to
a5a7ff2
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Quick and dirty way of making Content Publisher unavailable to publishers. We're about to run the migration script to copy all Content Publisher content into Whitehall, and we don't want publishers to then be able to go into Content Publisher and attempt to make edits to a now-migrated document.
Follows on from #3318, where we accidentally clobbered the healthcheck endpoints, stopping Content Publisher from starting up!
Jira: https://gov-uk.atlassian.net/browse/WHIT-2520
Follow these steps if you are doing a Rails upgrade.