GCP API 网关创建失败并出现内部服务器错误

如何解决GCP API 网关创建失败并出现内部服务器错误

我正在尝试自动创建 api-config 和 api-gateway,以使用 terraform 公开云运行服务。直到昨天它运行良好,并且 api-gateway 正在为流量提供服务。 但是考虑到大量请求访问 API 网关,我决定将读取请求的配额增加到更高的数字,这就是我修改 openapi swagger 文件以添加我的 API 配额的时候。

它在一段时间内运行良好,但现在当我触发我的管道时,它因内部服务器错误而失败。我也尝试使用云命令来创建一个详细程度设置为 DEBUG 的 API 网关,但找不到任何有用的东西。 使用 openapi 文件创建了 api 和 API 配置,但 API 网关的创建已停止...出现内部服务器错误。

附上我的 openapi 文件以供参考。:

swagger: "2.0"
info:
  version: 1.0.0
  title: Offer api
  description: API to get personalized offrs
produces:
- application/json
schemes:
- https
x-google-management:
  metrics:
    # Define a metric for read requests.
    - name: "read-requests"
      displayName: "Read requests"
      valueType: INT64
      metricKind: DELTA
  quota:
    limits:
      # Define the limit or the read-requests metric.
      - name: "read-limit"
        metric: "read-requests"
        unit: "1/min/{project}"
        values:
          STANDARD: 20000
paths:
  /offers: #/{deviceID}/{restaurantID}:
    get:
      description: get personalized offers
      operationId: app.get_offers
      x-google-backend:
        address: ${backend_address}
      parameters:
      - name: deviceID
        in: header
        required: True
        type: string
      - name: storeID
        in: header
        required: True
        type: string
      x-google-quota:
        metricCosts:
          "read-requests": 1
      security:
      - APIKeyHeader: []
      responses:
        200:
          description: Successful Operation
          schema:
            $ref: '#/definitions/APIResponse'
          #headers:
          #   Content-Type:
          #     schema:
          #       type: string
          #   Content-Encoding?:
          #     schema:
          #       type: string
          #  mcd-apiversion:
          #    type: string
          #   mcd-uuid:
          #     schema:
          #       type: string
          #   Cache-Control?:
          #     schema:
          #       type: string
          #   ETag:
          #     schema:
          #       type: string
        400:
          description: Bad Request - Invalid ID Supplied
          schema:
            $ref: '#/definitions/APIErrorResponse'
          # headers:
          #   Content-Type:
          #     schema:
          #       type: string
          #   Content-Encoding?:
          #     schema:
          #       type: string
        # 401:
        #   description: "Not Authorized - API KEY is invalid"
        #   content:
        #     application/json:
        #       schema:
        #         $ref: "#/responses/UnauthorizedError"
        404:
          description: "Resource not available - ID not found"
          schema:
            $ref: '#/definitions/APIErrorResponse'
          # headers:
          #   Content-Type:
          #     type: "string"
          #   Content-Encoding?:
          #     type: "string"
        415:
          description: "Unsupported media Type. Please check the content type in request"
          schema:
            $ref: '#/definitions/APIErrorResponse'
          # headers:
          #   Content-Type:
          #     type: "string"
          #   Content-Encoding?:
          #     type: "string"
        500:
          description: "Internal Server Error. Please refer logs for further details."
          schema:
            $ref: '#/definitions/APIErrorResponse'
          # headers:
          #   Content-Type:
          #     type: "string"
          #   Content-Encoding?:
          #     type: "string"
        503:
          description: "Service is unavailable. Please try after some time"
          schema:
            $ref: '#/definitions/APIErrorResponse'
          # headers:
          #   Content-Type:
          #     type: "string"
          #   Content-Encoding?:
          #     type: "string"
definitions:
  APIResponse:
    type: object
    required:
    - customerID
    - coupon
    properties:
      customerID:
        type: string
        example: "0000"
      coupon:
        type: string
        example: "Christmas100"
  APIErrorResponse:
    type: object
    required:
    - code
    - message
    properties:
      code:
        type: integer
      type:
        type: string
      message:
        type: string
      path:
        type: string
      service:
        type: string
      property:
        type: string
securityDefinitions:
  # This section configures basic authentication with an API key.
  APIKeyHeader:
    type: apiKey
    name: x-api-key   
    in: header

编辑 问题已解决。但似乎还有更多内容,有人知道如何定义每天请求的配额吗?从 GCP 文档中,我可以发现我们可以定义每分钟的请求数。(读取和写入)但是有没有办法为我们的 API 定义每天的请求数限制?

解决方法

不可能,因为 GCP 中唯一支持的 openapi 配额单位是 1/min/{project} as mentioned here

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-