Closed Bug 1453513 Opened 7 years ago Closed 5 years ago

deprecate s3 and azure storageTypes

Categories

(Taskcluster :: Services, enhancement, P5)

enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dustin, Unassigned)

References

Details

(copied from https://github.com/taskcluster/taskcluster-queue/issues/248) We should deprecate these two storage types. We should do this as a staged deprecation. I propose: 1. Announce deprecation 2. One month later, add a new mandatory property to the S3 storage type json schema "i-use-deprectated-storage-types": true, which will break users to alert them that the deprecation is happening. They can simply fix this by adding a static property to their API calls 3. One month later, disable the ability to create S3 artifacts This will allow old artifacts to be accessed but no new ones created.
Depends on: 1437461
QA Contact: jhford
Priority: -- → P5
Component: Queue → Services
Assignee: jhford → nobody
QA Contact: jhford

o contraire! We deprecated azure and blob.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.