Released a beta version of API Gateway. To provide feedback or to log issues with this release, see Getting support

## Announcement Released a beta version of API Gateway. To provide feedback or to log issues with this release, see [Getting support](https://cloud.google.com/api-gateway/docs/getting-support). ## Feature Newly created gateways have an updated default hostname pattern: `https://GATEWAY_ID-HASH.REGION_CODE.gateway.dev` where **GATEWAY\_ID** is the name of the gateway, **HASH** is the unique hash code generated when you deployed the gateway, and **REGION\_CODE** is the code for the Google Cloud region where the gateway is deployed. For more information, see [Deploying an API to a gateway](https://cloud.google.com/api-gateway/docs/deploying-api). ## Feature The API Gateway API is now publicly visible. Allowlisting is no longer required to view or enable the API in your Google Cloud project. Deprecated fields are no longer present in alpha versions of the API and the [API Gateway UI](https://console.cloud.google.com/api-gateway) utilizes the beta API. ## Feature API Gateway is added to the `gcloud beta` command group. Alpha users and trusted testers should upgrade to the latest `gcloud` release to access the API Gateway beta command group. ## Feature An updated [REST API reference](https://cloud.google.com/api-gateway/docs/reference/rest) for the `v1beta` version is available. ## Issue Projects with gateways created between July 14, 2020 and August 6, 2020 may encounter an issue when new gateways are created with the beta API. The `*gateway.dev` hostname of the new gateway may return a `404` error response. A resolution to this issue is in progress. In the meantime, we recommend creating or using a new Google Cloud project when using the beta API. ## Issue Gateways created during alpha with `*.run.app` hostnames (created prior to July 14, 2020) will be turned down shortly after the beta release. We recommend creating new gateways using the `v1beta` API. Gateways created with the beta API will have `*.gateway.dev` hostnames. ## Issue API configs created prior to June 2, 2020 can no longer be deployed to gateways. These configs will be deleted through an internal process. ## Issue API Gateway built-in IAM roles are not initially visible. As a result, management permissions are not displayed on the permissions panel within the [API Gateway UI](https://console.cloud.google.com/api-gateway). However, permissions to manage API Gateway resources can be granted as expected via Project Owner, Editor, and Viewer roles. A resolution to this issue is in progress. ## Issue API Gateway does not support custom IAM roles. A resolution to this issue is in progress. ## Issue When creating an API config, and in particular the _first_ config for a new service, the operation may take several minutes to complete as the config is propagated to downstream systems. Creation of a complex API config could take up to ten minutes to complete successfully.