Put Twitter API integrations behind feat flag and turn off
Goal
Deprecate Twitter API integrations in such a way that if their recent decisions on their API are reversed, we can resume normal operation.
What needs to be done
Gate Twitter API integrations behind a feature flag - turn the flag off on deploy for prod.
QA
Test integrations are gated and nothing breaks.
UX/Design
TO BE DISCUSSED RAPIDLY
Mobile
-
Is Mobile Required?
@valentin129 please track this card closely. Feel free to chat with me about it. Confirm with everybody before starting.
Personas
Twitter Sync users
Experiments
Create flag names engine-2503-twitter-apis
- when this is OFF access to the Twitter API is OFF.
Acceptance Criteria
-
Deprecate endpoints that integrate with Twitter API by using Feature flag middleware if they're V3 endpoints else add checks in the endpoints themselves or managers - decide on best strategy based on what presents - do a scan but I think this is the OAuth2 flow for Supermind and possible XPosting. -
Feat flag off other pathways to the API such as the runner, and possibly delegates on boost creation -
Update UI to put references including OAuth2 setup, Xposting setup and settings, Supermind checkbox etc behind the feat flag. -
When flag is OFF access to the API is OFF.
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Ben