[GH-ISSUE #617 ] [Bug] 部署到网宿 CDN Pro 时私钥加密错误 #409

Author

Owner

@fudiwei commented on GitHub (Apr 15, 2025):

接口示例脚本里给的是 username+ApiKey，但是 SDK 示例给的是 AccessKey+SecretKey，这是俩完全不同的签名方案。所以我才问你这玩意儿到底该咋加密的。

@fudiwei commented on GitHub (Apr 15, 2025): 接口示例脚本里给的是 username+ApiKey，但是 SDK 示例给的是 AccessKey+SecretKey，这是俩完全不同的签名方案。所以我才问你这玩意儿到底该咋加密的。

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 15, 2025):

接口示例脚本里给的是 username+ApiKey，但是 SDK 示例给的是 AccessKey+SecretKey，这是俩完全不同的签名方案。所以我才问你这玩意儿到底该咋加密的。

SDK 里我看给出了加密方式，这个是时间戳我确认了确实是当前时间，大哥别的还有啥问题不，有的话我问他们技术去。

@Anbool commented on GitHub (Apr 15, 2025): > 接口示例脚本里给的是 username+ApiKey，但是 SDK 示例给的是 AccessKey+SecretKey，这是俩完全不同的签名方案。所以我才问你这玩意儿到底该咋加密的。 SDK 里我看给出了加密方式，这个是时间戳我确认了确实是当前时间，大哥别的还有啥问题不，有的话我问他们技术去。

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 15, 2025):

https://www.wangsu.com/document/api-doc/Overview

你贴的那段脚本，是基于第一种 API 鉴权方式。但是它提供的 SDK，是基于第二种鉴权方式，根本就没有 username 和 ApiKey。

所以你得问问，用 AKSK 这种鉴权方式的话，加密这里这些参数该怎么调整？

我现在是拿 SecretKey 当 APIKey 去生成那个 AES Key 和 iv（你开头贴的那段脚本第 7-10 行，就把传入的 apikey 改成 secretkey），但这么看不对。

@fudiwei commented on GitHub (Apr 15, 2025): > ![Image](https://github.com/user-attachments/assets/9403435e-0a7c-4bfb-8212-e75c40e37afa) > > https://www.wangsu.com/document/api-doc/Overview 你贴的那段脚本，是基于第一种 API 鉴权方式。但是它提供的 SDK，是基于第二种鉴权方式，根本就没有 username 和 ApiKey。所以你得问问，用 AKSK 这种鉴权方式的话，加密这里这些参数该怎么调整？我现在是拿 SecretKey 当 APIKey 去生成那个 AES Key 和 iv（你开头贴的那段脚本第 7-10 行，就把传入的 apikey 改成 secretkey），但这么看不对。

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 15, 2025):

https://www.wangsu.com/document/api-doc/Overview

你贴的那段脚本，是基于第一种 API 鉴权方式。但是它提供的 SDK，是基于第二种鉴权方式，根本就没有 username 和 ApiKey。

所以你得问问，用 AKSK 这种鉴权方式的话，加密这里这些参数该怎么调整？

我现在是拿 SecretKey 当 APIKey 去生成那个 AES Key 和 iv（你开头贴的那段脚本第 7-10 行，就把传入的 apikey 改成 secretkey），但这么看不对。

你看是这个不大哥。

@Anbool commented on GitHub (Apr 15, 2025): > > ![Image](https://github.com/user-attachments/assets/9403435e-0a7c-4bfb-8212-e75c40e37afa) > > https://www.wangsu.com/document/api-doc/Overview > > 你贴的那段脚本，是基于第一种 API 鉴权方式。但是它提供的 SDK，是基于第二种鉴权方式，根本就没有 username 和 ApiKey。 > > 所以你得问问，用 AKSK 这种鉴权方式的话，加密这里这些参数该怎么调整？ > > 我现在是拿 SecretKey 当 APIKey 去生成那个 AES Key 和 iv（你开头贴的那段脚本第 7-10 行，就把传入的 apikey 改成 secretkey），但这么看不对。你看是这个不大哥。 ![Image](https://github.com/user-attachments/assets/4dc6c607-26cb-4cf6-92e2-febff0061222)

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 15, 2025):

我再详细说一遍吧，要是还没明白我也没办法了。

网宿云提供了两种 API 鉴权方案，第一种是 username+ApiKey 生成签名，第二种是 AccessKey+SecretKey 生成签名。

它接口文档里给的 curl 示例，是基于第一种实现的。AES 加密所用到的密钥，是用 ApiKey+当前时间生成出来的。

但它的 SDK，是基于第二种实现的。现在的问题就是，此时 AES 加密用到的秘钥该怎么生成？

API 鉴权是 API 鉴权，是所有接口都需要做的一步。AES 加密是 AES 加密，只有创建证书 privateKey 这一个字段需要加密。只是它 AES 加密所需的参数来自于 API 鉴权，可给的示例只有第一种没有第二种的。

@fudiwei commented on GitHub (Apr 15, 2025): 我再详细说一遍吧，要是还没明白我也没办法了。网宿云提供了两种 API 鉴权方案，第一种是 username+ApiKey 生成签名，第二种是 AccessKey+SecretKey 生成签名。它接口文档里给的 curl 示例，是基于第一种实现的。AES 加密所用到的密钥，是用 ApiKey+当前时间生成出来的。但它的 SDK，是基于第二种实现的。现在的问题就是，此时 AES 加密用到的秘钥该怎么生成？ API 鉴权是 API 鉴权，是所有接口都需要做的一步。AES 加密是 AES 加密，只有创建证书 privateKey 这一个字段需要加密。只是它 AES 加密所需的参数来自于 API 鉴权，可给的示例只有第一种没有第二种的。

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 15, 2025):

确认是不能用 AK/SK 加密证书私钥。证书接口比较特殊，私钥加密只能用 ApiKey。仍可以用 AK/SK 做接口鉴权，但是私钥加密必须用 ApiKey。

这就意味着，必须单独的提供一个使用 Username+ApiKey 加密 privateKey 字段的方式🤣

ApiKey 在 https://console.wangsu.com/account/apiManage 进行创建。

@Anbool commented on GitHub (Apr 15, 2025): 确认是不能用 AK/SK 加密证书私钥。证书接口比较特殊，私钥加密只能用 ApiKey。仍可以用 AK/SK 做接口鉴权，但是私钥加密必须用 ApiKey。这就意味着，必须单独的提供一个使用 Username+ApiKey 加密 privateKey 字段的方式🤣 ApiKey 在 https://console.wangsu.com/account/apiManage 进行创建。

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 17, 2025):

@Anbool 麻烦帮忙验证一下 #627 的 commit 50b48d956f

如果你没有 Node 环境的话直接跑 go 单测用例也行，位于 /internal/pkg/core/deployer/providers/wangsu-cdnpro 目录下。

@fudiwei commented on GitHub (Apr 17, 2025): @Anbool 麻烦帮忙验证一下 #627 的 commit 50b48d956fde3b6d5c90107fa6ac4d9aa8c464be 如果你没有 Node 环境的话直接跑 go 单测用例也行，位于 /internal/pkg/core/deployer/providers/wangsu-cdnpro 目录下。

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 17, 2025):

@fudiwei 大哥，我看了一下代码，是不是少一个 username

@Anbool commented on GitHub (Apr 17, 2025): @fudiwei 大哥，我看了一下代码，是不是少一个 username

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 17, 2025):

@fudiwei 大哥，我看了一下代码，是不是少一个 username

Username 是用来生成请求签名的，现在签名是基于 AK/SK 生成的，也没法同时用两种签名呀。生成 AES 秘钥只需要 ApiKey 和时间戳。

@fudiwei commented on GitHub (Apr 17, 2025): > [@fudiwei](https://github.com/fudiwei) 大哥，我看了一下代码，是不是少一个 username Username 是用来生成请求签名的，现在签名是基于 AK/SK 生成的，也没法同时用两种签名呀。生成 AES 秘钥只需要 ApiKey 和时间戳。

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 17, 2025):

@fudiwei 看上去失败了，好像没有打印具体的接口错误信息

go test -v ./wangsu_cdnpro_test.go -args --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTCERTPATH="/root/1.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTKEYPATH="/root/2.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYID="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYSECRET="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_APIKEY="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ENVIRONMENT="production" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_DOMAIN="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_CERTIFICATEID="脱敏"
=== RUN   TestDeploy
=== RUN   TestDeploy/Deploy
    wangsu_cdnpro_test.go:58: args:
        INPUTCERTPATH: /root/1.pem
        INPUTKEYPATH: /root/2.pem
        ACCESSKEYID: 脱敏
        ACCESSKEYSECRET: 脱敏
        APIKEY: 脱敏
        ENVIRONMENT: production
        DOMAIN: 脱敏
        CERTIFICATEID: 脱敏
        WEBHOOKID: 
    wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input
        failed to execute sdk request 'cdn.UpdateCertificate'
        github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy
                /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154
        command-line-arguments_test.TestDeploy.func1
                /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87
        testing.tRunner
                /usr/local/go/src/testing/testing.go:1792
        runtime.goexit
                /usr/local/go/src/runtime/asm_amd64.s:1700
--- FAIL: TestDeploy (5.07s)
    --- FAIL: TestDeploy/Deploy (5.07s)
FAIL
FAIL    command-line-arguments  5.073s
FAIL

@Anbool commented on GitHub (Apr 17, 2025): @fudiwei 看上去失败了，好像没有打印具体的接口错误信息 ```shell go test -v ./wangsu_cdnpro_test.go -args --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTCERTPATH="/root/1.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTKEYPATH="/root/2.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYID="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYSECRET="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_APIKEY="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ENVIRONMENT="production" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_DOMAIN="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_CERTIFICATEID="脱敏" === RUN TestDeploy === RUN TestDeploy/Deploy wangsu_cdnpro_test.go:58: args: INPUTCERTPATH: /root/1.pem INPUTKEYPATH: /root/2.pem ACCESSKEYID: 脱敏 ACCESSKEYSECRET: 脱敏 APIKEY: 脱敏 ENVIRONMENT: production DOMAIN: 脱敏 CERTIFICATEID: 脱敏 WEBHOOKID: wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input failed to execute sdk request 'cdn.UpdateCertificate' github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154 command-line-arguments_test.TestDeploy.func1 /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87 testing.tRunner /usr/local/go/src/testing/testing.go:1792 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1700 --- FAIL: TestDeploy (5.07s) --- FAIL: TestDeploy/Deploy (5.07s) FAIL FAIL command-line-arguments 5.073s FAIL ```

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 17, 2025):

@fudiwei 抱歉，我又仔细的查看了一下控制台，证书的确已经可以上传了，把证书名称从我之前的域名命名改成了certimate_***，目前看已经成功更新了证书，因为我在 shell 看到的是报错，所以执行了四次，目前这个证书从原来的三个版本变成了七个版本，目前第七个版本还尚未部署，这样看来更新证书接口是没有问题的。但不知道为什么单例测试抛出了错误。

@Anbool commented on GitHub (Apr 17, 2025): @fudiwei 抱歉，我又仔细的查看了一下控制台，证书的确已经可以上传了，把证书名称从我之前的域名命名改成了certimate_***，目前看已经成功更新了证书，因为我在 shell 看到的是报错，所以执行了四次，目前这个证书从原来的三个版本变成了七个版本，目前第七个版本还尚未部署，这样看来更新证书接口是没有问题的。但不知道为什么单例测试抛出了错误。

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 17, 2025):

@fudiwei 看上去失败了，好像没有打印具体的接口错误信息

go test -v ./wangsu_cdnpro_test.go -args --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTCERTPATH="/root/1.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTKEYPATH="/root/2.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYID="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYSECRET="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_APIKEY="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ENVIRONMENT="production" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_DOMAIN="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_CERTIFICATEID="脱敏"
=== RUN TestDeploy
=== RUN TestDeploy/Deploy
wangsu_cdnpro_test.go:58: args:
INPUTCERTPATH: /root/1.pem
INPUTKEYPATH: /root/2.pem
ACCESSKEYID: 脱敏
ACCESSKEYSECRET: 脱敏
APIKEY: 脱敏
ENVIRONMENT: production
DOMAIN: 脱敏
CERTIFICATEID: 脱敏
WEBHOOKID:
wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input
failed to execute sdk request 'cdn.UpdateCertificate'
github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy
/root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154
command-line-arguments_test.TestDeploy.func1
/root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87
testing.tRunner
/usr/local/go/src/testing/testing.go:1792
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1700
--- FAIL: TestDeploy (5.07s)
--- FAIL: TestDeploy/Deploy (5.07s)
FAIL
FAIL command-line-arguments 5.073s
FAIL

internal/pkg/vendors/wangsu-sdk/openapi/client.go 第 161 行：

- resp, err := req.Send()
+ resp, err := req.SetDebug(true).Send()

重新跑一下单测，会在控制台打印 HTTP 报文。看一下更新证书那个接口的响应是什么？

@fudiwei commented on GitHub (Apr 17, 2025): > [@fudiwei](https://github.com/fudiwei) 看上去失败了，好像没有打印具体的接口错误信息 > > go test -v ./wangsu_cdnpro_test.go -args --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTCERTPATH="/root/1.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_INPUTKEYPATH="/root/2.pem" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYID="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ACCESSKEYSECRET="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_APIKEY="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_ENVIRONMENT="production" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_DOMAIN="脱敏" --CERTIMATE_DEPLOYER_WANGSUCDNPRO_CERTIFICATEID="脱敏" > === RUN TestDeploy > === RUN TestDeploy/Deploy > wangsu_cdnpro_test.go:58: args: > INPUTCERTPATH: /root/1.pem > INPUTKEYPATH: /root/2.pem > ACCESSKEYID: 脱敏 > ACCESSKEYSECRET: 脱敏 > APIKEY: 脱敏 > ENVIRONMENT: production > DOMAIN: 脱敏 > CERTIFICATEID: 脱敏 > WEBHOOKID: > wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input > failed to execute sdk request 'cdn.UpdateCertificate' > github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy > /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154 > command-line-arguments_test.TestDeploy.func1 > /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87 > testing.tRunner > /usr/local/go/src/testing/testing.go:1792 > runtime.goexit > /usr/local/go/src/runtime/asm_amd64.s:1700 > --- FAIL: TestDeploy (5.07s) > --- FAIL: TestDeploy/Deploy (5.07s) > FAIL > FAIL command-line-arguments 5.073s > FAIL internal/pkg/vendors/wangsu-sdk/openapi/client.go 第 161 行： ```diff - resp, err := req.Send() + resp, err := req.SetDebug(true).Send() ``` 重新跑一下单测，会在控制台打印 HTTP 报文。看一下更新证书那个接口的响应是什么？

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 18, 2025):

@fudiwei 接口没有返回响应体，只有响应头。
请求：

GET  /cdn/hostnames/google.com

响应体：

{
   "hostname": "google.com",
   "propertyInProduction": {
      "propertyId": "37683af98f3e",
      "version": 2,
      "certificateId": "1c2a58aa2e3"
   },
   "propertyInStaging": null
}

请求：

PATCH  /cdn/certificates/1c2a58aa2e3

响应头：

STATUS       : 201 Created
PROTO        : HTTP/1.1
RECEIVED AT  : 2025-04-18T01:51:00.082893847Z
TIME DURATION: 2.226002464s
HEADERS      :
        App-Name: portal-ngcdn
        Connection: keep-alive
        Content-Length: 0
        Content-Type: application/json;charset=utf-8
        Date: Fri, 18 Apr 2025 01:51:00 GMT
        Location: https://open.chinanetcenter.com/cdn/certificates/1c2a58aa2e3/versions/8
        Server: openresty/1.11.2.2
        X-Cnc-Process-Time: 2.172
        X-Cnc-Request-Id: 1b10-a5c-4be
        X-Time-Zone: GMT+08:00
        X-Ws-Request-Id: 6801b006_PSxgHK5hq204_1699-333
BODY         :
***** NO CONTENT *****

@Anbool commented on GitHub (Apr 18, 2025): @fudiwei 接口没有返回响应体，只有响应头。请求： ```shell GET /cdn/hostnames/google.com ``` 响应体： ```shell { "hostname": "google.com", "propertyInProduction": { "propertyId": "37683af98f3e", "version": 2, "certificateId": "1c2a58aa2e3" }, "propertyInStaging": null } ``` 请求： ```shell PATCH /cdn/certificates/1c2a58aa2e3 ``` 响应头： ```shell STATUS : 201 Created PROTO : HTTP/1.1 RECEIVED AT : 2025-04-18T01:51:00.082893847Z TIME DURATION: 2.226002464s HEADERS : App-Name: portal-ngcdn Connection: keep-alive Content-Length: 0 Content-Type: application/json;charset=utf-8 Date: Fri, 18 Apr 2025 01:51:00 GMT Location: https://open.chinanetcenter.com/cdn/certificates/1c2a58aa2e3/versions/8 Server: openresty/1.11.2.2 X-Cnc-Process-Time: 2.172 X-Cnc-Request-Id: 1b10-a5c-4be X-Time-Zone: GMT+08:00 X-Ws-Request-Id: 6801b006_PSxgHK5hq204_1699-333 BODY : ***** NO CONTENT ***** ```

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 18, 2025):

应该是判断响应状态码是否为 201，然后取 Location 响应头中的 versions 执行部署就行了。

@Anbool commented on GitHub (Apr 18, 2025): 应该是判断响应状态码是否为 **201**，然后取 **Location** 响应头中的 **versions** 执行部署就行了。

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 18, 2025):

再验证一下 commit 437fea2c1c1fbedf7ce1dcc66bad9db2f329f887

@fudiwei commented on GitHub (Apr 18, 2025): 再验证一下 commit 437fea2c1c1fbedf7ce1dcc66bad9db2f329f887

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 18, 2025):

再验证一下 commit 437fea2

好像同样的错误。

BODY         :
***** NO CONTENT *****
==============================================================================
    wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input
        failed to execute sdk request 'cdn.UpdateCertificate'
        github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy
                /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154
        command-line-arguments_test.TestDeploy.func1
                /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87
        testing.tRunner
                /usr/local/go/src/testing/testing.go:1792
        runtime.goexit
                /usr/local/go/src/runtime/asm_amd64.s:1700
--- FAIL: TestDeploy (3.23s)
    --- FAIL: TestDeploy/Deploy (3.23s)
FAIL
FAIL    command-line-arguments  3.235s
FAIL

@Anbool commented on GitHub (Apr 18, 2025): > 再验证一下 commit [437fea2](https://github.com/usual2970/certimate/commit/437fea2c1c1fbedf7ce1dcc66bad9db2f329f887) 好像同样的错误。 ```shell BODY : ***** NO CONTENT ***** ============================================================================== wangsu_cdnpro_test.go:89: err: wangsu api error: failed to parse response: unexpected end of JSON input failed to execute sdk request 'cdn.UpdateCertificate' github.com/usual2970/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro.(*DeployerProvider).Deploy /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go:154 command-line-arguments_test.TestDeploy.func1 /root/certimate/internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro_test.go:87 testing.tRunner /usr/local/go/src/testing/testing.go:1792 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1700 --- FAIL: TestDeploy (3.23s) --- FAIL: TestDeploy/Deploy (3.23s) FAIL FAIL command-line-arguments 3.235s FAIL ```

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 18, 2025):

再验证一下 commit c21258f192f1ce01c96d60b2cc67d557fa29172a

@fudiwei commented on GitHub (Apr 18, 2025): 再验证一下 commit c21258f192f1ce01c96d60b2cc67d557fa29172a

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 18, 2025):

再验证一下 commit c21258f

测试流程通过了，但是程序会一直处于 INFO waiting for deployment task completion ... 状态，但已经部署完成了。
响应体：

      {
         "id": "2eb7c927-5c5c-67a24bdc8209",
         "name": "部署加速项目“Test-01”的版本12",
         "submissionTime": "2024-03-12T15:03:00Z",
         "finishTime": "2024-03-12T15:06:48Z",
         "status": "succeeded",
         "target": "production",
         "apiRequestId": "309e3eb2f0"
      }

@Anbool commented on GitHub (Apr 18, 2025): > 再验证一下 commit [c21258f](https://github.com/usual2970/certimate/commit/c21258f192f1ce01c96d60b2cc67d557fa29172a) 测试流程通过了，但是程序会一直处于 INFO waiting for deployment task completion ... 状态，但已经部署完成了。响应体： ```json { "id": "2eb7c927-5c5c-67a24bdc8209", "name": "部署加速项目“Test-01”的版本12", "submissionTime": "2024-03-12T15:03:00Z", "finishTime": "2024-03-12T15:06:48Z", "status": "succeeded", "target": "production", "apiRequestId": "309e3eb2f0" } ```

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 18, 2025):

再验证一下 commit c10ceed753 ，然后看一下日志打印的 current status 是什么？

@fudiwei commented on GitHub (Apr 18, 2025): 再验证一下 commit c10ceed75345543cc6d2c669988e826c3d93f3c2 ，然后看一下日志打印的 current status 是什么？

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 19, 2025):

@Anbool Any updates?

@fudiwei commented on GitHub (Apr 19, 2025): @Anbool Any updates?

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 19, 2025):

@Anbool Any updates?

抱歉延迟的更新。看到日志打印了为空。在 2025/04/19 04:16:58 之前就已经部署完成了。

2025/04/19 04:16:04 INFO ssl certificate uploaded certUrl=https://open.chinanetcenter.com/cdn/certificates/1c2a2e3/versions/13
2025/04/19 04:16:09 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:15 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:21 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:27 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:34 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:40 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:46 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:52 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:16:58 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:17:04 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:17:10 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:17:16 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:17:22 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 04:17:28 INFO waiting for deployment task completion (current status: ) ...

@Anbool commented on GitHub (Apr 19, 2025): > [@Anbool](https://github.com/Anbool) Any updates? 抱歉延迟的更新。看到日志打印了为空。在 **2025/04/19 04:16:58** 之前就已经部署完成了。 ```shell 2025/04/19 04:16:04 INFO ssl certificate uploaded certUrl=https://open.chinanetcenter.com/cdn/certificates/1c2a2e3/versions/13 2025/04/19 04:16:09 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:15 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:21 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:27 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:34 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:40 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:46 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:52 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:16:58 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:17:04 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:17:10 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:17:16 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:17:22 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 04:17:28 INFO waiting for deployment task completion (current status: ) ... ```

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 19, 2025):

为啥 status 是空呢…… 😕

@Anbool 日志里 sdk request 'cdn.GetDeploymentTaskDetail' 这条展开看一下 response 是啥？

如果你是跑的单测的话这个日志级别是 DEBUG 不会显示在控制台上，你可以修改 internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go 第 204 行，将 d.logger.Debug(...) 改为 d.logger.Info(...)

@fudiwei commented on GitHub (Apr 19, 2025): 为啥 status 是空呢…… 😕 @Anbool 日志里 `sdk request 'cdn.GetDeploymentTaskDetail'` 这条展开看一下 response 是啥？ --- 如果你是跑的单测的话这个日志级别是 DEBUG 不会显示在控制台上，你可以修改 internal/pkg/core/deployer/providers/wangsu-cdnpro/wangsu_cdnpro.go 第 204 行，将 `d.logger.Debug(...)` 改为 `d.logger.Info(...)`

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 19, 2025):

就返回了以下内容

2025/04/19 14:59:56 INFO waiting for deployment task completion (current status: ) ...
2025/04/19 15:00:02 INFO sdk request 'cdn.GetDeploymentTaskDetail' taskId="" response="&{baseResponse:{RequestId:0xc0002043a0 Code:<nil> Message:<nil>} Id: Name: Target: Actions:[] Status: StatusDetails: SubmissionTime: FinishTime: ApiRequestId:}"

@Anbool commented on GitHub (Apr 19, 2025): 就返回了以下内容 ```shell 2025/04/19 14:59:56 INFO waiting for deployment task completion (current status: ) ... 2025/04/19 15:00:02 INFO sdk request 'cdn.GetDeploymentTaskDetail' taskId="" response="&{baseResponse:{RequestId:0xc0002043a0 Code:<nil> Message:<nil>} Id: Name: Target: Actions:[] Status: StatusDetails: SubmissionTime: FinishTime: ApiRequestId:}" ```

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 20, 2025):

😵‍💫 为啥都是空……

@Anbool 这个不是 Response Body 吗？

@fudiwei commented on GitHub (Apr 20, 2025): 😵‍💫 为啥都是空…… > ![Image](https://github.com/user-attachments/assets/230cdba7-3f65-49e0-abff-e4320634ddf5) @Anbool 这个不是 Response Body 吗？

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 20, 2025):

@fudiwei 大哥，你可以给我一个邮箱不，我把 Key 都发给你，你调试看看可能比较快？

@Anbool commented on GitHub (Apr 20, 2025): @fudiwei 大哥，你可以给我一个邮箱不，我把 Key 都发给你，你调试看看可能比较快？

kerem commented

Author

Owner

@Anbool commented on GitHub (Apr 20, 2025):

已发送，请查收。测试域名直接操作，不需要我二次确认。此外所需的 API 访问权限都已经开通了。另外最好是在控制台引导用户在使用之前先检查 API 权限是否已经开通，避免后期造成不必要的 issues，大部分 API 权限可以在 https://apiexplorer.wangsu.com/apiexplorer/overview 门户直接开通和查看。辛苦了！

@Anbool commented on GitHub (Apr 20, 2025): 已发送，请查收。测试域名直接操作，不需要我二次确认。此外所需的 API 访问权限都已经开通了。另外最好是在控制台引导用户在使用之前先检查 API 权限是否已经开通，避免后期造成不必要的 issues，大部分 API 权限可以在 https://apiexplorer.wangsu.com/apiexplorer/overview 门户直接开通和查看。辛苦了！

kerem commented

Author

Owner

@fudiwei commented on GitHub (Apr 21, 2025):

@Anbool 感谢提供测试环境，问题已修复。记得重置 AK/SK，以免数据泄露。

@fudiwei commented on GitHub (Apr 21, 2025): @Anbool 感谢提供测试环境，问题已修复。记得重置 AK/SK，以免数据泄露。

kerem commented