Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content modelling/610 change name to Content Block Manager #9507

Merged
merged 4 commits into from
Oct 10, 2024

Conversation

Harriethw
Copy link
Contributor

@Harriethw Harriethw commented Oct 9, 2024

Here we change the name of the service from Content Object Store to Content Block Manager - and while we are here we remove /government/admin from the url.


⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

Follow these steps if you are doing a Rails upgrade.

@Harriethw Harriethw force-pushed the content-modelling/610-change-name branch 2 times, most recently from 3490240 to 3eeb73d Compare October 9, 2024 14:37
@Harriethw Harriethw changed the title Content modelling/610 change name Content modelling/610 change name to Content Block Manager Oct 9, 2024
@Harriethw Harriethw marked this pull request as ready for review October 9, 2024 15:00
@Harriethw Harriethw requested a review from pezholio October 9, 2024 15:00
Copy link
Contributor

@pezholio pezholio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@@ -30,16 +30,16 @@ def edition_params
end

def set_sentry_tags
Sentry.set_tags(engine: "content_object_store")
Sentry.set_tags(engine: "content_block_manager")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ooh, I'll need to tweak the Sentry rules to look for the new tag instead of the old ones to ensure we still get the Slack alerts

@Harriethw Harriethw force-pushed the content-modelling/610-change-name branch from 3eeb73d to 683bd3b Compare October 10, 2024 08:39
this includes routes, engine name, test names etc.
this is not relevant to the Content Block Manager,
so we are just having the endpoint be
`/content-block-manager`.
although it is not good practice to edit past
migrations, we think this is safe to do as it
doesn't change the actual migration, and not
changing it could cause problems/confusion in the
future.
@Harriethw Harriethw force-pushed the content-modelling/610-change-name branch from 683bd3b to f3e4b30 Compare October 10, 2024 09:12
@Harriethw Harriethw enabled auto-merge October 10, 2024 09:14
@Harriethw Harriethw disabled auto-merge October 10, 2024 09:14
@Harriethw Harriethw enabled auto-merge October 10, 2024 09:14
@Harriethw Harriethw merged commit 09cd479 into main Oct 10, 2024
19 checks passed
@Harriethw Harriethw deleted the content-modelling/610-change-name branch October 10, 2024 09:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants