Skip to content
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.

Feature request: Support deployment configuration #59

Open
ferrandinand opened this issue Jun 3, 2020 · 4 comments
Open

Feature request: Support deployment configuration #59

ferrandinand opened this issue Jun 3, 2020 · 4 comments

Comments

@ferrandinand
Copy link

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

@four43
Copy link

four43 commented Aug 4, 2020

I can try and add this - this seems pretty straight forward. You basically just create a "deployment" (just a name right?) then you can reference it in your pipelines config? Is that your usecase?

@pjroth
Copy link

pjroth commented Aug 9, 2020

Here is some added info in case it's helpful. Perhaps you know this already...

This screenshot is when using the bitbucket UI and you navigate to "Repository Settings"/"Pipelines"/"Deployments". Deployments are just a name but they are associated to an Environment and they have config. The environment API docs also might be needed.

These deployments/environments in my screenshot are the defaults I get when I create a repository via the bitbucket website and enable pipelines also via the website (pipelines config API). I don't know if you create a repository via the API if you get these default deployments/environments.

image

@four43
Copy link

four43 commented Aug 11, 2020

Okay cool, that's how we typically use them too. Pretty straight forward. That's cool you can add some variables. I don't think they had that last time I checked.

I'm waiting on #62 to kind of see how things are sitting with this project. There are some open PRs that would be nice to get merged in. I hate for everyone to have to side-load in a provider. Could be something the community takes over into a community driven one like 0.13 is hyping: https://registry.terraform.io/browse/providers

@a6patch
Copy link

a6patch commented Oct 1, 2020

Not having the deployments and deployment variables is VERY painful. Maintaining a fleet of microservice repos each with a dozen or more deployments (devel, test, qa, staging, prod...for each of 3 countries)...and a handful of important deployment variables makes for a lot of tedious configuration through the UI.

I'd also like to see a data or resource import for pulling in already existing repos, repos variables, deployments, and deployment variables.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants