[PR #327] [MERGED] fixed: instance not found when deploying tencent COS #916

New issue

Closed

opened 2026-03-03 01:06:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 01:06:48 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/certimate-go/certimate/pull/327
Author: @LeoChen98
Created: 11/12/2024
Status: ✅ Merged
Merged: 11/13/2024
Merged by: @usual2970

Base: main ← Head: fix-tencent-cos-instance-not-found

📝 Commits (2)

80caf88 fixed: instance not found when deploying tencent COS
e9b6fb5 fixed: instance possible not found when deploying tencent CLB via SSL api

📊 Changes

2 files changed (+4 additions, -3 deletions)

View changed files

📝 internal/deployer/tencent_clb.go (+1 -1)
📝 internal/deployer/tencent_cos.go (+3 -2)

📄 Description

修复了重构导致腾讯云COS部署时找不到实例的bug
修复了重构导致腾讯云CLB通过SSL接口部署时可能找不到实例的bug

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/certimate-go/certimate/pull/327 **Author:** [@LeoChen98](https://github.com/LeoChen98) **Created:** 11/12/2024 **Status:** ✅ Merged **Merged:** 11/13/2024 **Merged by:** [@usual2970](https://github.com/usual2970) **Base:** `main` ← **Head:** `fix-tencent-cos-instance-not-found` --- ### 📝 Commits (2) - [`80caf88`](https://github.com/certimate-go/certimate/commit/80caf881aed1bce6a1795dbc65cc72b34cb51cad) fixed: instance not found when deploying tencent COS - [`e9b6fb5`](https://github.com/certimate-go/certimate/commit/e9b6fb55ffdac80ae3fc747d72d68d880ed66344) fixed: instance possible not found when deploying tencent CLB via SSL api ### 📊 Changes **2 files changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `internal/deployer/tencent_clb.go` (+1 -1) 📝 `internal/deployer/tencent_cos.go` (+3 -2) </details> ### 📄 Description - 修复了重构导致腾讯云COS部署时找不到实例的bug - 修复了重构导致腾讯云CLB通过SSL接口部署时可能找不到实例的bug --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>