Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Set GOOGLE_APPLICATION_CREDENTIALS in the production Docker image | mediawiki/services/push-notifications | master | +5 -2 |
Details
Related Objects
Event Timeline
@Krenair I notice that the BC instances for some services deployed on k8s are using a deployment-docker-<service> naming convention, and others are just using deployment-<service>. Do you know if there's been any discussion or agreement around the naming convention one way or the other?
Looking over some older tasks (primarily T220235), it seems like the deployment-docker- convention was used for a few already-existing services, perhaps as an easy way of distinguishing between VMs running the Dockerized versions of the services and those running the pre-Docker versions. I'll plan to omit the docker- portion and just create deployment-push-notifications01.
I've created deployment-push-notifications01 to host the push-notifications service. TODO: Configure application credentials for interacting with Firebase.
Change 601826 had a related patch set uploaded (by Mholloway; owner: Michael Holloway):
[mediawiki/services/push-notifications@master] Set GOOGLE_APPLICATION_CREDENTIALS in the production Docker image
@Mholloway Will there be some documentation on how you set this up? E.g. the /etc/mediawiki-services-push-notifications/google-application-credentials.json files needs to be placed.
Change 601826 merged by jenkins-bot:
[mediawiki/services/push-notifications@master] Set GOOGLE_APPLICATION_CREDENTIALS in the production Docker image