Rename master branch to main (#427)

* rename master to main
* update links

Author: vbauzys

.changes/README.md

@@ -24,7 +24,7 @@ After a release, the changelog will be initialized with the following template:
 ```
     ## $VERSION (Unreleased)
 
-    Changes in progress for v$VERSION are available at [.changes/v$VERSION](https://github.com/vmware/go-vcloud-director/tree/master/.changes/v$VERSION) until the release.
+    Changes in progress for v$VERSION are available at [.changes/v$VERSION](https://github.com/vmware/go-vcloud-director/tree/main/.changes/v$VERSION) until the release.
 ```
 
 Run `.changes/init.sh version` to get the needed text

.changes/init.sh

@@ -21,6 +21,6 @@ echo ""
 echo ""
 echo "## $VERSION (Unreleased)"
 echo ""
-echo "Changes in progress for v$VERSION are available at [.changes/v$VERSION](https://github.com/vmware/go-vcloud-director/tree/master/.changes/v$VERSION) until the release."
+echo "Changes in progress for v$VERSION are available at [.changes/v$VERSION](https://github.com/vmware/go-vcloud-director/tree/main/.changes/v$VERSION) until the release."
 echo ""
 

.drone.yml

@@ -19,4 +19,4 @@ publish:
     server: https://coverage.vmware.run
     token: $$COVERAGE_TOKEN
     when:
-      branch: master
+      branch: main

CHANGELOG.md

@@ -1,6 +1,6 @@
 ## 2.15.0 (TBC)
 
-Changes in progress for v2.15.0 are available at [.changes/v2.15.0](https://github.com/vmware/go-vcloud-director/tree/master/.changes/v2.15.0) until the release.
+Changes in progress for v2.15.0 are available at [.changes/v2.15.0](https://github.com/vmware/go-vcloud-director/tree/main/.changes/v2.15.0) until the release.
 
 ## 2.14.0 (January 7, 2022)
 

CODE_OF_CONDUCT.md

@@ -30,4 +30,4 @@ an issue or PR.
 
 **Attribution**
 
-This Code of Conduct is adapted from the VMware Clarity project, available at this page: https://github.com/vmware/clarity/blob/master/CODE_OF_CONDUCT.md
+This Code of Conduct is adapted from the VMware Clarity project, available at this page: https://github.com/vmware/clarity/blob/next/docs/CODE_OF_CONDUCT.md

CODING_GUIDELINES.md

@@ -115,7 +115,7 @@ func (client *Client) ExecuteRequestWithCustomError(pathURL, requestType, conten
 In addition to saving code and time by reducing the boilerplate, these functions also trigger debugging calls that make the code 
 easier to monitor.
 Using any of the above calls will result in the standard log i
-(See [LOGGING.md](https://github.com/vmware/go-vcloud-director/blob/master/util/LOGGING.md)) recording all the requests and responses
+(See [LOGGING.md](https://github.com/vmware/go-vcloud-director/blob/main/util/LOGGING.md)) recording all the requests and responses
 on demand, and also triggering debug output for specific calls (see `enableDebugShowRequest` and `enableDebugShowResponse`
 and the corresponding `disable*` in `api.go`).
 
@@ -479,4 +479,4 @@ When the tenant context is not needed (system administration calls), we just pas
 
 ## Testing
 
-Every feature in the library must include testing. See [TESTING.md](https://github.com/vmware/go-vcloud-director/blob/master/TESTING.md) for more info.
+Every feature in the library must include testing. See [TESTING.md](https://github.com/vmware/go-vcloud-director/blob/main/TESTING.md) for more info.

CONTRIBUTING.md

@@ -31,7 +31,7 @@ contributors.  Typical contribution flow steps are:
 - Update Go modules files `go.mod` and `go.sum` if you're changing dependencies.
 - Fetch changes from upstream and resolve any merge conflicts so that your topic branch is up-to-date
 - Push all commits to the topic branch in your forked repo
-- Submit a pull request to merge topic branch commits to upstream master
+- Submit a pull request to merge topic branch commits to upstream main
 
 If this process sounds unfamiliar have a look at the
 excellent [overview of collaboration via pull requests on
@@ -102,11 +102,11 @@ the fork up to date. More on that shortly.
 
 ### Make Changes and Commit
 
-Start a new topic branch from the current HEAD position on master and
+Start a new topic branch from the current HEAD position on main and
 commit your feature changes into that branch.  
 
 ``` shell
-git checkout -b foo-api-fix-22 master
+git checkout -b foo-api-fix-22 main
 # (Make feature changes)
 git commit -a --signoff
 git push origin foo-api-fix-22
@@ -131,7 +131,7 @@ them now](https://stackoverflow.com/questions/161813/how-to-resolve-merge-confli
 ``` shell
 git checkout foo-api-fix-22
 git fetch -a
-git pull --rebase upstream master --tags
+git pull --rebase upstream main --tags
 git push --force-with-lease origin foo-api-fix-22
 ```
 
@@ -159,7 +159,7 @@ To contribute your feature, create a pull request by going to the [go-vcloud-dir
 
 Select 'compare across forks' and select imahacker/go-vcloud-director as 'head fork'
 and foo-api-fix-22 as the 'compare' branch.  Leave the base fork as 
-vmware/go-vcloud-director and master. 
+vmware/go-vcloud-director and main. 
 
 ### Wait...
 
@@ -193,7 +193,7 @@ If you need to squash changes into an earlier commit, you can use:
 ``` shell
 git add .
 git commit --fixup <commit>
-git rebase -i --autosquash master
+git rebase -i --autosquash main
 git push --force-with-lease origin foo-api-fix-22
 ```
 

README.md

@@ -1,4 +1,4 @@
-# go-vcloud-director [![Build Status](https://travis-ci.org/vmware/go-vcloud-director.svg?branch=master)](https://travis-ci.org/vmware/go-vcloud-director) [![Coverage Status](https://coveralls.io/repos/vmware/go-vcloud-director/badge.svg?branch=master&service=github)](https://coveralls.io/github/vmware/go-vcloud-director?branch=master) [![GoDoc](https://godoc.org/github.com/vmware/go-vcloud-director?status.svg)](http://godoc.org/github.com/vmware/go-vcloud-director) [![Chat](https://img.shields.io/badge/chat-on%20slack-brightgreen.svg)](https://vmwarecode.slack.com/messages/CBBBXVB16)
+# go-vcloud-director [![GoDoc](https://godoc.org/github.com/vmware/go-vcloud-director?status.svg)](http://godoc.org/github.com/vmware/go-vcloud-director) [![Chat](https://img.shields.io/badge/chat-on%20slack-brightgreen.svg)](https://vmwarecode.slack.com/messages/CBBBXVB16)
 
 This repo contains the `go-vcloud-director` package which implements
 an SDK for vCloud Director. The project serves the needs of Golang
@@ -37,7 +37,7 @@ To show the SDK in action run the example:
 ```
 mkdir ~/govcd_example
 go mod init govcd_example
-go get github.com/vmware/go-vcloud-director/v2@master
+go get github.com/vmware/go-vcloud-director/v2@main
 go build -o example
 ./example user_name "password" org_name vcd_IP vdc_name 
 ```

govcd/edgegateway.go

@@ -1174,7 +1174,7 @@ func (egw *EdgeGateway) UpdateLBGeneralParams(enabled, accelerationEnabled, logg
 }
 
 // GetFirewallConfig retrieves firewall configuration and can be used
-// to alter master configuration options. These are 3 fields only:
+// to alter main configuration options. These are 3 fields only:
 // FirewallConfigWithXml.Enabled, FirewallConfigWithXml.DefaultPolicy.LoggingEnabled and
 // FirewallConfigWithXml.DefaultPolicy.Action
 func (egw *EdgeGateway) GetFirewallConfig() (*types.FirewallConfigWithXml, error) {

govcd/sample_govcd_test_config.yaml

@@ -179,7 +179,7 @@ ova:
   ovfPath: ../test-resources/test_vapp_template_ovf/descriptor.ovf
   #
   # The OVF URL for uploading catalog item for tests.
-  ovfUrl: https://raw.githubusercontent.com/vmware/go-vcloud-director/master/test-resources/test_vapp_template_ovf/descriptor.ovf
+  ovfUrl: https://raw.githubusercontent.com/vmware/go-vcloud-director/main/test-resources/test_vapp_template_ovf/descriptor.ovf
 media:
   # The iso for uploading media item for tests.
   # Default paths are simple iso provided by project