Skip to content

Update Docker Hub deployment for all Community Edition service repositories #9

@Exairnous

Description

@Exairnous

In order for the Hubs Foundation to provide the code from the repositories for use by Community Edition instances (and our own instance), the workflows to build the Community Edition services, along with the staging/prod environments and the Docker Hub password secret in each repository, need to be updated.

Workflow changes to make in each repository

The path to the turkeyGitops workflow needs to be updated to use Hubs-Foundation instead of mozilla.
The registry needs to be updated to use hubsfoundation instead of mozillareality.

Note: if you need to create the workflow, you can base it off of https://github.com/Hubs-Foundation/nearspark/blob/master/.github/workflows/nearspark.yml (make sure to remember to update both the file name and the name parameter in the file).

Environment Settings to update in each repository

The turkeyGitops workflow utilizes the staging and prod environments in each repository to control whether beta and stable Docker images are created in addition to dev images. The following settings should be utilized for these environments:

  • Deployment protection rules
    • Required reviewers
      • Add up to 5 more reviewers
      • Hubs-Foundation/operations
      • Prevent self-review
    • Wait timer
  • Allow administrators to bypass configured protection rules

Important: save the protection rules before making any other changes.

Deployment branches and tags - Selected branches and tags
hotfix/**
master

Note: some repositories may have the default branch named as main instead of master so use whichever name corresponds with the default branch of the repository.

Secrets to update in each repository

The turkeyGitops workflow utilizes the DOCKER_HUB_PWD Action Secret in each repository to log into Docker Hub. The Hubs Foundation's Docker Hub token should be used for it.

Repositories to update:

Note: ensure that the environment settings and secrets have been updated, in addition to the workflow, before marking a repository as updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Tracking IssueLabel for issues that are used as a central place to coordinate larger pieces of work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions