We chose to use the rails command rather than the API to avoid having to create a service user and API key, but since we'll likely need to do this for the apt-staging work, that gets rid of that reason

In T352433#9371609, @eoghan wrote:

We chose to use the rails command rather than the API to avoid having to create a service user and API key, but since we'll likely need to do this for the apt-staging work, that gets rid of that reason

Yes that was quite a nice solution without the need of a dedicated API key. Maybe the command also just changed a bit and we have to modify the gitlab-rails call slightly? Do you have any resources or docs about the BroadcastMessage.create() call which might help troubleshooting this?

I'd like to say it was some excellent documentation to find it, but I mostly just took a look around the source code to follow the path of an API call to the public API. It does look like they just moved the class though (found by searching for the BroadcastMessage class in the source), so now it is System::BroadcastMessage. I can prepare a patch for this.

Change 980377 had a related patch set uploaded (by EoghanGaffney; author: EoghanGaffney):

[operations/puppet@production] [gitlab] Update BroadcastMessage class to new namespace

https://gerrit.wikimedia.org/r/980377

Change 980377 merged by EoghanGaffney:

[operations/puppet@production] [gitlab] Update BroadcastMessage class to new namespace

https://gerrit.wikimedia.org/r/980377