Release pipeline #178
Release pipeline #178
Conversation
# Conflicts: # azuredevops/internal/model/tags.go
# Conflicts: # azuredevops/internal/service/taskagent/data_agent_queue.go # azuredevops/provider.go
# Conflicts: # azuredevops/internal/service/graph/data_group.go
|
Hi 👋 do you continue working on this? |
|
Just curious if this is headed towards being merged? |
|
is there any indication that this will be merged? |
|
The forth person here asking if this is still being worked on and if it will be merged any time soon? 👀 |
|
Also, would be interested 👍🏽 |
|
Yes please, let's have it working. |
|
It seems like release pipelines from an API standpoint have been around for a while. Given this is an official provider, what's the hold up? https://learn.microsoft.com/en-us/rest/api/azure/devops/release/?view=azure-devops-rest-7.0 |
|
Bumping - is this close to implementation? |
|
bump. waiting for this. |
|
Hi this is something most usable we are waiting on it a long time now. |
|
@exocom Do you think this code is ready to be reviewed or you need more time and/or help? |
|
Is there any way we (the community) could help to get this through the finish line? This is a big gap in features for this provider and we would love to see this working. |
All Submissions:
What about the current behavior has changed?
Adding release pipelines
Issue Number: #49
Does this introduce a change to
go.mod,go.sumorvendor/?Does this introduce a breaking change?
Any relevant logs, error output, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Other information
The release pipeline is complex. Many limitations in Terraform were discovered and due to this the syntax is not ideal. For defaults many blocks must be present and empty. Looks terrible, however, there is currently no good way around it.