Closed Bug 1838456 Opened 2 years ago Closed 2 years ago

new s3 credentials for maven staging

Categories

(Cloud Services :: Operations: Product Delivery, task)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jcristau, Assigned: cvalaas)

References

Details

Hi,

As part of bug 1822248 we're going to need to upload android-components to maven from gecko beetmoverscript instead of mobile beetmoverscript.
We'll start with stage (maven-default.stage.mozaws.net and maven-nightly.stage.mozaws.net)

  • gecko is currently using key id AKIASCFACX26ZEQA2XUW to upload to maven2/org/mozilla/geckoview/ on maven-default-s3-upload-bucket-13gy5ufwa3qv. We'll want that key to additionally upload to maven2/org/mozilla/components/ in the same bucket, can you verify whether that is allowed, and add it if not?

  • gecko currently doesn't have credentials for the maven-nightly-stage-s3-upload-bucket bucket. mobile uses key id AKIASCFACX267F3OCIVZ.
    Can we get a new id/key pair for uploads to maven2/org/mozilla/components/ in that bucket?

Thanks!

Flags: needinfo?(cvalaas)

Okay, I've updated AKIASCFACX26ZEQA2XUW to allow .../components/*
More to come...

Flags: needinfo?(cvalaas)

I'm confused as to the second bullet. Do you want the permissions in AKIASCFACX267F3OCIVZ (write to maven-nightly-stage-s3-upload-bucket .../components) applied to the AKIASCFACX26ZEQA2XUW account? Along with the permission I added in bullet 1?

Flags: needinfo?(jcristau)

Or wait, you want a new id/key for that, right?

Right, I'd like a new key/id for maven-nightly-stage-s3-upload-bucket maven2/org/mozilla/components/*. Thanks!

Flags: needinfo?(jcristau)

New key created. Will send creds via wormhole.

I think we're all good here, beetmover to maven-nightly-stage is working for gecko.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Assignee: nobody → cvalaas
You need to log in before you can comment on or make changes to this bug.