Closed Bug 1312423 Opened 9 years ago Closed 9 years ago

ATMO V2: Create API

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P3)

Product:
Cloud Services Graveyard
Component:
Metrics: Pipeline
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: frank, Unassigned)

References

Details

It would be nice to have an ATMO API so that we can build a CLI that people can use to launch clusters and use our service.
Depends on: 1312424
No longer depends on: 1312424
Blocks: 1312424
No longer blocks: 1248688
Priority: -- → P3
Can you clarify how many user you expect for this? I'm asking since adding a public and secure API that effectively only a handful of people use is a lot of technical debt for little time saving.
Flags: needinfo?(fbertsch)
You make a good point - I wouldn't expect there to be lots of users, probably just the power users. Mauro and I were discussing whether this be a bug or on the 2017 roadmap. If you think it's an unreasonable request in the near future we can move it to there, or decide to kill it altogether.
Flags: needinfo?(fbertsch)
:frank Oh yeah, I think having an API is definitely useful once the feature set has settled and we've worked on bug 1312428 to strip out the Mozilla bits. That includes having created a generic software package from atmo that is easy to customize with templates and such that would effectively be atmo (atmo = generic product + templates + configuration). An API fits the feature set of such a product way better and could be done in that next phase in 2017, agreed. Let's keep the ticket open until then.
Moved to https://github.com/mozilla/telemetry-analysis-service/issues/197
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.