Skip to content

Change all Cases browser-side clients and UI to handle additive changes #160345

Open

Description

Feature Description

Additive changes can be made to internal HTTP APIs without creating a new major version. Additionally, old browser-side code will be able to run against newer server-side code, resulting in browser-side code needing to adapt to the additive changes made to these HTTP APIs. As a result, browser-side code will need to be updated to handle additive changes, primarily the addition of new response fields and new values added to non-inclusive enums.

Business Value

Facilitates zero downtime rolling upgrades and rollbacks, allowing us to roll-out new features to our users more quickly while they continue to use the system without disruption.

Definition of Done

  • All browser-side code is changed to ignore all unknown response fields
  • Unit tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Feature:CasesCases featureProject:ServerlessWork as part of the Serverless project for its initial releaseProject:Serverless MVPTeam:ResponseOpsLabel for the ResponseOps team (formerly the Cases and Alerting teams)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions