This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/go_modules/github.com/hashicorp/terraform-plugin-sdk/v2-2.34.0
in repository 
https://gitbox.apache.org/repos/asf/cloudstack-terraform-provider.git


 discard b4fe3a0  chore(deps): bump github.com/hashicorp/terraform-plugin-sdk/v2
     add b16c94f  chore: protect main branch with mandatory checks (#123)
     add 37ebe49  ci: runs acc test on every change (#127)
     add bf3bcec  Update .asf.yaml (#128)
     add e6bcc74  feat: migrate to terraform plugin framework (#113)
     add 2b04e98  chore(deps): bump github.com/hashicorp/terraform-plugin-sdk/v2

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (b4fe3a0)
            \
             N -- N -- N   
refs/heads/dependabot/go_modules/github.com/hashicorp/terraform-plugin-sdk/v2-2.34.0
 (2b04e98)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .asf.yaml                        |   9 +++
 .github/workflows/acceptance.yml |   6 --
 cloudstack/provider.go           |   4 +-
 cloudstack/provider_test.go      |  82 +++++++++++++++------
 cloudstack/provider_v6.go        | 155 +++++++++++++++++++++++++++++++++++++++
 cloudstack/resources.go          |  23 ++++++
 go.mod                           |   2 +
 go.sum                           |   4 +
 main.go                          |  32 +++++---
 9 files changed, 280 insertions(+), 37 deletions(-)
 create mode 100644 cloudstack/provider_v6.go

Reply via email to