terraform-provider-bitbucket
terraform-provider-bitbucket copied to clipboard
hashicorp
This Terraform provider is archived per our provider archiving process: https://terraform.io/docs/internals/archiving.html
### Terraform Version Terraform v0.12.24 + provider.aws v2.59.0 + provider.bitbucket v1.2.0 ### Affected Resource(s) - bitbucket_repository_variable when `secured = true` ### Terraform Configuration Files ```hcl resource "bitbucket_repository_variable" "foo" { repository...
**Terraform Version** Terraform v0.12.17 **Feature requested** It would be great if the provider could support deployment configurations as it is documented on the API specifications. **Bitbucket API** https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{workspace}/{repo_slug}/deployments_config
### Terraform Version ``` $ terraform version Terraform v0.11.14 + provider.bitbucket v1.2.0 ``` ### Affected Resource(s) Please list the resources as a list, for example: - [bitbucket_repository](https://www.terraform.io/docs/providers/bitbucket/r/repository.html) ### Terraform Configuration...
Add an importer to the `bitbucket_project` resource. Fixes #68
Would be nice if the `bitbucket_project` resource would support importing.
Adding a note about the credentials being possibly configured via environment variables as well. Second commit also includes two typo fixes.
Setting Sensitive to true for `deployment_variable` so Terraform hides values from the CLI output, as they often contain sensitive credentials.
_This issue was originally opened by @saitheexplorer as hashicorp/terraform#14458. It was migrated here as part of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-terraform-0-10/). The original body of the issue is below._ Hey all -...
This is a nice to have so we don't have to initially create our repo in bitbucket. Usually devs create a repo then our ops team helps with setting up...
