-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Added a flag to specify whether to import groups that already exist…
… in bitbucket along with functionality to import those groups into the terraform state * Changed the error checking when importing an existing group for bitbucket so that the duplicate group error is not thrown * Added two acceptance tests * Updated the ReadMe.md with accurate instructions since the previous ones were not working for us * Updated the Makefile to set the maximum number of files allowed to be open to 1024 since 256 was too few. We called `ulimit -n 1024` to do this for the testacc and testacc-bitbucket targets. * Changed the start-docker-compose.sh to use the bitbucket server environment variable so that it doesn't always refer to localhost * Skipped some testcases that are consistently failing in master branch * Added a version.env file to be used to control the versioning from CICD builds * Set version to 1.4.0 * In the start-docker-compose.sh if the BITBUCKET_SERVER environment variable is not set then use http://localhost:7990 In the start-docker-compose.sh if the BITBUCKET_SERVER environment variable is not set then use http://localhost:7990
- Loading branch information
1 parent
f116e39
commit b3ee8fd
Showing
9 changed files
with
131 additions
and
35 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -45,45 +45,22 @@ See [User Guide](https://gavinbunney.github.io/terraform-provider-bitbucketserve | |
- [Terraform](https://www.terraform.io/downloads.html) 0.12.x | ||
- [Go](https://golang.org/doc/install) 1.11 (to build the provider plugin) | ||
|
||
### Building The Provider | ||
|
||
Clone repository to: `$GOPATH/src/github.com/gavinbunney/terraform-provider-bitbucketserver` | ||
|
||
```sh | ||
$ mkdir -p $GOPATH/src/github.com/terraform-providers; cd $GOPATH/src/github.com/terraform-providers | ||
$ git clone [email protected]:gavinbunney/terraform-provider-bitbucketserver | ||
``` | ||
|
||
Enter the provider directory and build the provider | ||
|
||
```sh | ||
$ cd $GOPATH/src/github.com/gavinbunney/terraform-provider-bitbucketserver | ||
$ make build | ||
``` | ||
|
||
### Developing the Provider | ||
|
||
If you wish to work on the provider, you'll first need [Go](http://www.golang.org) installed on your machine (version 1.11+ is *required*). You'll also need to correctly setup a [GOPATH](http://golang.org/doc/code.html#GOPATH), as well as adding `$GOPATH/bin` to your `$PATH`. | ||
|
||
To compile the provider, run `make build`. This will build the provider and put the provider binary in the `$GOPATH/bin` directory. | ||
Then clone the repository [Terraform provider bitbucket](https://github.com/gavinbunney/terraform-provider-bitbucketserver) | ||
|
||
```sh | ||
$ make bin | ||
... | ||
$ $GOPATH/bin/terraform-provider-bitbucketserver | ||
... | ||
``` | ||
To compile the provider, run `make build`. This will build the provider and put the provider binary in the `$GOPATH/bin` directory. | ||
|
||
In order to test the provider, you can simply run `make test`. | ||
|
||
```sh | ||
$ make test | ||
``` | ||
|
||
In order to run the full suite of Acceptance tests, run `make testacc`. | ||
|
||
*Note:* Acceptance tests create real resources, and often cost money to run. | ||
In order to run the full suite of Acceptance tests, run `make testacc-bitbucket`. Alternatively, you can run the | ||
`scripts/start-docker-compose.sh` to start the Bitbucket docker container, run `make testacc` and then call | ||
`scripts/stop-docker-compose.sh` when done running tests. | ||
|
||
```sh | ||
$ make testacc | ||
``` | ||
*Note:* Acceptance tests create real resources, and often cost money to run if not running locally. |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
#We use semantic versioning: | ||
#version x.y.z | ||
#x is an api version and if breaking api changes are introduced this should change, otherwise it remains constant | ||
#y is a new feature version and this only changes if new features are changed but bugs are not fixed | ||
#z is a patch version that changes if a bug is fixed for a previous feature version. | ||
# See https://semver.org/ for more information | ||
|
||
#To use this file call `source version.env` from a bash terminal | ||
|
||
export BITBUCKET_PROVIDER_VERSION=1.4.0 |