Multi-Region: Apigee deployment failures for some OAS policies

The issue with Apigee has been resolved for all affected users as of Thursday, 2023-06-29 14:15 US/Pacific. We thank you for your patience while we worked on resolving the issue.

Summary: Multi-Region: Apigee deployment failures for some OAS policies Description: Mitigation work is currently underway and our engineering team is currently validating the fix. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-06-29 16:00 US/Pacific. Diagnosis: Customers with an existing revision with an affected OAS spec will have deployment failures, which would result in a runtime traffic failure. Workaround: Customers should disable the OAS policy.

Summary: Multi-Region: Apigee deployment failures for some OAS policies Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-06-29 12:45 US/Pacific. Diagnosis: Customers with an existing revision with an affected OAS spec will have deployment failures, which would result in a runtime traffic failure. Workaround: Customers should disable the OAS policy.

Summary: Multi-Region: Apigee deployment failures for some OAS policies Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-06-29 10:45 US/Pacific. Diagnosis: Customers with an existing revision with an affected OAS spec will have deployment failures, which would result in a runtime traffic failure. Workaround: Customers should disable the OAS policy.

Summary: us-east1: Apigee unable to deploy proxy with OAS Description: We are experiencing an issue with Apigee. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-06-29 09:45 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Customers with an existing revision with an affected OAS spec will have deployment failures, which would result in a runtime traffic failure. Workaround: Customers should disable the OAS policy.