DEVOPS Deep-Dive: API Platform "Deep Launches" Technique with Release Toggles and OAuth2 Scopes
Release Toggles allow incomplete and un-tested codepaths to be shipped to production as latent code which may never be turned on. These are feature flags used to enable trunk-based development for teams practicing Continuous Delivery. They allow in-progress features to be checked into a shared integration branch (e.g. master or trunk) while still allowing that branch to be deployed to production at any time. Release Toggles allow incomplete and un-tested codepaths to be shipped to production as latent code which may never be turned on.
Product Managers may also use a product-centric version of this same approach to prevent half-complete product features from being exposed to their end users. OAuth2 access to the APIs allow the client applications to know which features are enabled through the Token scopes associated with the access_token provided by the API Platform.
This session will show a live demo of Release Toggles in action at UCSF with a Smart-on-FHIR Referrals application and take a deep dive on the Continuous Delivery setup and Mulesoft flows implementation.
- OAuth2: Authorization, Token
- Smart-on-FHIR specification
- Jenkins (optional)
- Mulesoft API and ESB Platform (optional)