Closed smarnach closed 1 year ago
You should have merge rights sven
Just request a merge if that is not the case.
I will say that my experience has been that Fridays are best to avoid big changes on unless there are weekend resources available, in case the cjange causes breakage
On Fri, Jan 13, 2023, 5:50 AM Sven Marnach @.***> wrote:
Mozilla wants to move the static content storage for the publicsuffix.org website and the list from S3 to Googe Cloud Storage. We would also like to start using GitHub Actions to sync the files.
@Flipez https://github.com/Flipez will file a pull request with the Actions workflow. I already added the bucket name and some project identifiers as secrets in the repository settings. (They aren't actually secrets, but we'd prefer to keep them private.) We will use workload identity federation to authenticate to GCP, so we won't need any GCP access keys in the secrets.
Once these workflows are working as expected, I will drop my permissions on the repositories again.
— Reply to this email directly, view it on GitHub https://github.com/publicsuffix/publicsuffix.org/issues/33, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACQTJMB7EZYWUOFP3HUZ3LWSFMRDANCNFSM6AAAAAAT2NZUTI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Thanks, @dnsguru! I filed this ticket for transparency, and to give you or other a chance to comment. Merging the PR is not a major change. The actual change if we start actually using the new backend bucket. Until then the site is still served from the S3 origin.
Mozilla wants to move the static content storage for the publicsuffix.org website and the list from S3 to Googe Cloud Storage. We would also like to start using GitHub Actions to sync the files.
@Flipez will file a pull request with the Actions workflow. I already added the bucket name and some project identifiers as secrets in the repository settings. (They aren't actually secrets, but we'd prefer to keep them private.) We will use workload identity federation to authenticate to GCP, so we won't need any GCP access keys in the secrets.
Once these workflows are working as expected, I will drop my permissions on the repositories again.