Closed
Bug 1510795
Opened 7 years ago
Closed 6 years ago
Use new AWS account for S3 wireproto cache
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: gps, Assigned: sheehan)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
Currently, the S3 caching is using a bucket in the moz-devservices AWS account. We want to transition to S3 bucket(s) owned by the new AWS account, which Connor is actively standing up.
|
Reporter | |
Updated•7 years ago
|
Assignee: nobody → sheehan
Status: NEW → ASSIGNED
|
Assignee | |
Comment 1•7 years ago
|
||
This commit adds an S3 module which configures buckets for
various hg projects within different regions. As of now,
we only create the clone/pull bundle packages in this module.
In the near future we will add IAM policies to this module that
allow storing wire protocol responses as well.
Pushed by gszorc@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/994670fde7bd
terraform: add s3 module for various S3 buckets r=gps
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 3•7 years ago
|
||
We set up the buckets but still need to start using them in production. Re-opening to track finishing that work.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
|
Assignee | |
Updated•6 years ago
|
Status: REOPENED → RESOLVED
Closed: 7 years ago → 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•