Create all necessary artifacts, and deploy AQS 2.0 to staging and production environments.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Stalled | None | T324931 Clean up open RESTBase related tickets | |||
In Progress | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
In Progress | None | T263489 AQS 2.0 | |||
Open | None | T356693 [SPRINT 09][SDS 2.6.4] AQS 2: Complete AQS 2.0 maintainer docs to do’s | |||
Open | Atieno | T318111 <spike>[needs grooming] API services deployment plan for Gerrit | |||
Resolved | None | T288661 Create k8s deployment of AQS 2.0 | |||
Invalid | None | T326699 Route Device Analytics through API Gateway |
Event Timeline
Comment Actions
There is likely overlap between this task and the direction that it looks like T323190: Allow configuration to be conveniently overridden in local development environments is headed.
I feel they should remain separate tasks, just noting for possible synergy.