We shipped an experimental update-flag endpoint (issue) and later decided to stabilise options A and B paths onto a new /api/__future__/environment/{key}/features/{id}/ (C) option (issue).
The code for the previous implementation still remains.
Acceptance criteria
- Code currently depending on any components of the old update-flag is adjusted to either break the dependency, or reroute it to option C.
- All the code that power the old update-flag, i.e. both options A and B, is deleted.
We shipped an experimental
update-flagendpoint (issue) and later decided to stabilise options A and B paths onto a new/api/__future__/environment/{key}/features/{id}/(C) option (issue).The code for the previous implementation still remains.
Acceptance criteria