Missing arguments in azuredevops_project_pipeline_settings

[leighmo]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

We need to be able to set the following arguments in the Project pipeline settings as we leverage modules in other projects that reside outside of the existing project the pipeline is executed from. We also want to disable class build/release pipelines via code and have these checked regularly to make sure they are not being changed.

• "Limit job authorization scope to current project for release pipelines" - Most important
• "Disable creation of classic build and classic release pipelines" - Less important

Thanks

New or Affected Resource(s)

azuredevops_project_pipeline_settings

Potential Terraform Configuration

Untested

References

No

[xuzhang3]

@leighmo "Limit job authorization scope to current project for release pipelines" has been support be resource azuredevops_project_pipeline_settings.enforce_job_scope

[leighmo]

Hi @xuzhang3,

Thanks for the reply. There are two options in the Azure DevOps Pipeline settings.

Limit job authorization scope to current project for non-release pipelines
Non-Release Pipelines can run with collection scoped access tokens unless this option is enabled. With this option enabled, you can reduce the scope of access for all non-release pipelines to the current project.

Limit job authorization scope to current project for release pipelines
Release pipelines can run with collection scoped access tokens unless this option is enabled. With this option enabled, you can reduce the scope of access for all release pipelines to the current project.

The current module covers off the first option "non-release pipelines" but does not address the second option "release pipelines"

Cheers

[ashleyghooper]

Yes, we've been disabling the limit for release pipelines as a manual step and would greatly appreciate being able to do this via TF.

[xuzhang3]

New features will be available after upgrading to v7 API

[xuzhang3]

Disable creation of classic build and classic release pipelines - This configuration cannot be updated via the API.
Issue: microsoft/azure-devops-go-api#133

[citrix-pradeep]

Hi @xuzhang3 , can we have terraform support for [azuredevops_project_pipeline_settings] - Support pipeline general settings for " Disable creation of classic build and classic release pipelines"

[xuzhang3]

@citrix-pradeep SDK does not support these two properties yet.

[arodindev]

@xuzhang3 are there any plans on adding the missing project pipeline settings in near future? This would be very helpful for us.

[xuzhang3]

SDK update PR: microsoft/azure-devops-go-api#193