Repository navigation
feat(cynosdb): [135685079] support storage_pay_mode update for tencentcloud_cynosdb_cluster via TransferStoragePrepayToPostpay - #4558
Merged
gitmkn merged 2 commits intoOct 14, 2026
Conversation
…db_cluster via TransferStoragePrepayToPostpay
iac-agent
force-pushed
the
feat/modify-cynosdb-cluster-storage-pay-mode-update
branch
from
October 14, 2026 03:46
dea2ef4 to
d40d5b0
Compare
gitmkn
approved these changes
Oct 14, 2026
gitmkn
deleted the
feat/modify-cynosdb-cluster-storage-pay-mode-update
branch
October 14, 2026 07:16
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support updating the storage_pay_mode field of tencentcloud_cynosdb_cluster. The storage_pay_mode now supports modification from prepaid(1) to postpaid(0) by calling the TransferStoragePrepayToPostpay API (https://cloud.tencent.com/document/product/1003/135369). This is an asynchronous API; after invocation, the returned DealName is used to call DescribeResourcesByDealName to perform async waiting, following the same pattern as the create module.