The documentation from bitbucket is actually not that good, because it doesn't explain any of the fields in question. However I observed on the bitbucket-cloud instance that the previous implementation lead to errors during imports of deployment configurations into a terraform state.
Steps to reproduce the error:
Create a repository in bitbucket-cloud
Create a deployment for the repository via GUI for Production or Staging (not Test!)
write a terraform module (which exactly matches the deployment) and perform terraform import to import the existing deployment into the terraform state
perform terraform apply and terraform wants to change the resource!
This change reads the rank from the environment_type which is the only valid source if the deployment was created via UI and still a valid source for a deployment which was created via this provider.
The documentation from bitbucket is actually not that good, because it doesn't explain any of the fields in question. However I observed on the bitbucket-cloud instance that the previous implementation lead to errors during imports of deployment configurations into a terraform state.
Steps to reproduce the error:
terraform importto import the existing deployment into the terraform stateterraform applyand terraform wants to change the resource!This change reads the rank from the
environment_typewhich is the only valid source if the deployment was created via UI and still a valid source for a deployment which was created via this provider.Reference: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-deployments/#api-repositories-workspace-repo-slug-environments-environment-uuid-get-response Closes: #186