pulumi-azuredevops 3.6.0a1737091250__py3-none-any.whl → 3.6.0a1737710622__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (119) hide show
  1. pulumi_azuredevops/__init__.py +64 -0
  2. pulumi_azuredevops/_inputs.py +120 -117
  3. pulumi_azuredevops/area_permissions.py +49 -49
  4. pulumi_azuredevops/branch_policy_auto_reviewers.py +7 -7
  5. pulumi_azuredevops/branch_policy_build_validation.py +7 -7
  6. pulumi_azuredevops/branch_policy_comment_resolution.py +7 -7
  7. pulumi_azuredevops/branch_policy_merge_types.py +7 -7
  8. pulumi_azuredevops/branch_policy_status_check.py +7 -7
  9. pulumi_azuredevops/branch_policy_work_item_linking.py +7 -7
  10. pulumi_azuredevops/build_definition.py +7 -7
  11. pulumi_azuredevops/check_branch_control.py +7 -7
  12. pulumi_azuredevops/check_business_hours.py +7 -7
  13. pulumi_azuredevops/check_exclusive_lock.py +7 -7
  14. pulumi_azuredevops/check_rest_api.py +986 -0
  15. pulumi_azuredevops/feed.py +8 -8
  16. pulumi_azuredevops/feed_permission.py +9 -9
  17. pulumi_azuredevops/feed_retention_policy.py +422 -0
  18. pulumi_azuredevops/get_agent_queue.py +2 -2
  19. pulumi_azuredevops/get_area.py +1 -1
  20. pulumi_azuredevops/get_client_config.py +3 -0
  21. pulumi_azuredevops/get_feed.py +4 -4
  22. pulumi_azuredevops/get_git_repository.py +8 -8
  23. pulumi_azuredevops/get_group.py +4 -4
  24. pulumi_azuredevops/get_groups.py +3 -3
  25. pulumi_azuredevops/get_identity_group.py +3 -0
  26. pulumi_azuredevops/get_identity_groups.py +1 -1
  27. pulumi_azuredevops/get_identity_users.py +5 -5
  28. pulumi_azuredevops/get_pool.py +14 -2
  29. pulumi_azuredevops/get_pools.py +3 -3
  30. pulumi_azuredevops/get_project.py +32 -0
  31. pulumi_azuredevops/get_projects.py +4 -4
  32. pulumi_azuredevops/get_repositories.py +7 -3
  33. pulumi_azuredevops/get_securityrole_definitions.py +4 -4
  34. pulumi_azuredevops/get_service_endpoint_azure_rm.py +5 -5
  35. pulumi_azuredevops/get_service_endpoint_github.py +6 -6
  36. pulumi_azuredevops/get_service_principal.py +153 -0
  37. pulumi_azuredevops/get_serviceendpoint_azurecr.py +1 -1
  38. pulumi_azuredevops/get_serviceendpoint_bitbucket.py +6 -6
  39. pulumi_azuredevops/get_serviceendpoint_npm.py +3 -3
  40. pulumi_azuredevops/get_serviceendpoint_sonarcloud.py +2 -2
  41. pulumi_azuredevops/get_team.py +4 -3
  42. pulumi_azuredevops/get_teams.py +2 -3
  43. pulumi_azuredevops/get_users.py +5 -9
  44. pulumi_azuredevops/git.py +7 -7
  45. pulumi_azuredevops/git_permissions.py +14 -21
  46. pulumi_azuredevops/git_repository_file.py +7 -14
  47. pulumi_azuredevops/group.py +21 -7
  48. pulumi_azuredevops/group_entitlement.py +16 -20
  49. pulumi_azuredevops/group_membership.py +35 -50
  50. pulumi_azuredevops/iterative_permissions.py +34 -34
  51. pulumi_azuredevops/library_permissions.py +75 -75
  52. pulumi_azuredevops/outputs.py +129 -102
  53. pulumi_azuredevops/pipeline_authorization.py +7 -7
  54. pulumi_azuredevops/pool.py +4 -4
  55. pulumi_azuredevops/project.py +114 -63
  56. pulumi_azuredevops/project_features.py +87 -45
  57. pulumi_azuredevops/project_permissions.py +7 -7
  58. pulumi_azuredevops/project_pipeline_settings.py +28 -35
  59. pulumi_azuredevops/project_tags.py +263 -0
  60. pulumi_azuredevops/pulumi-plugin.json +1 -1
  61. pulumi_azuredevops/queue.py +7 -14
  62. pulumi_azuredevops/repository_policy_author_email_pattern.py +21 -14
  63. pulumi_azuredevops/repository_policy_max_file_size.py +7 -7
  64. pulumi_azuredevops/resource_authorization.py +35 -35
  65. pulumi_azuredevops/service_endpoint_artifactory.py +24 -18
  66. pulumi_azuredevops/service_endpoint_aws.py +2 -2
  67. pulumi_azuredevops/service_endpoint_azure_ecr.py +13 -15
  68. pulumi_azuredevops/service_endpoint_azure_rm.py +25 -25
  69. pulumi_azuredevops/service_endpoint_bit_bucket.py +2 -2
  70. pulumi_azuredevops/service_endpoint_docker_registry.py +2 -2
  71. pulumi_azuredevops/service_endpoint_generic.py +2 -2
  72. pulumi_azuredevops/service_endpoint_generic_git.py +4 -8
  73. pulumi_azuredevops/service_endpoint_git_hub.py +15 -2
  74. pulumi_azuredevops/service_endpoint_git_hub_enterprise.py +15 -2
  75. pulumi_azuredevops/service_endpoint_kubernetes.py +23 -23
  76. pulumi_azuredevops/service_endpoint_npm.py +4 -4
  77. pulumi_azuredevops/service_endpoint_pipeline.py +4 -4
  78. pulumi_azuredevops/service_endpoint_service_fabric.py +48 -9
  79. pulumi_azuredevops/service_endpoint_sonar_cloud.py +11 -11
  80. pulumi_azuredevops/service_endpoint_sonar_qube.py +11 -11
  81. pulumi_azuredevops/service_endpoint_ssh.py +2 -6
  82. pulumi_azuredevops/service_principal_entitlement.py +386 -0
  83. pulumi_azuredevops/serviceendpoint_argocd.py +2 -2
  84. pulumi_azuredevops/serviceendpoint_azure_service_bus.py +2 -2
  85. pulumi_azuredevops/serviceendpoint_checkmarx_one.py +627 -0
  86. pulumi_azuredevops/serviceendpoint_checkmarx_sast.py +575 -0
  87. pulumi_azuredevops/serviceendpoint_checkmarx_sca.py +674 -0
  88. pulumi_azuredevops/serviceendpoint_dynamics_lifecycle_services.py +2 -2
  89. pulumi_azuredevops/serviceendpoint_externaltfs.py +63 -11
  90. pulumi_azuredevops/serviceendpoint_gcp_terraform.py +2 -2
  91. pulumi_azuredevops/serviceendpoint_incomingwebhook.py +2 -2
  92. pulumi_azuredevops/serviceendpoint_jenkins.py +2 -2
  93. pulumi_azuredevops/serviceendpoint_jfrog_artifactory_v2.py +18 -18
  94. pulumi_azuredevops/serviceendpoint_jfrog_distribution_v2.py +18 -18
  95. pulumi_azuredevops/serviceendpoint_jfrog_platform_v2.py +18 -18
  96. pulumi_azuredevops/serviceendpoint_jfrog_xray_v2.py +18 -18
  97. pulumi_azuredevops/serviceendpoint_maven.py +2 -2
  98. pulumi_azuredevops/serviceendpoint_nexus.py +2 -2
  99. pulumi_azuredevops/serviceendpoint_nuget.py +2 -2
  100. pulumi_azuredevops/serviceendpoint_octopusdeploy.py +2 -2
  101. pulumi_azuredevops/serviceendpoint_permissions.py +40 -40
  102. pulumi_azuredevops/serviceendpoint_snyk.py +2 -2
  103. pulumi_azuredevops/serviceendpoint_visualstudiomarketplace.py +4 -6
  104. pulumi_azuredevops/servicehook_permissions.py +51 -51
  105. pulumi_azuredevops/servicehook_storage_queue_pipelines.py +4 -4
  106. pulumi_azuredevops/tagging_permissions.py +49 -49
  107. pulumi_azuredevops/team.py +76 -56
  108. pulumi_azuredevops/team_administrators.py +83 -56
  109. pulumi_azuredevops/team_members.py +56 -49
  110. pulumi_azuredevops/variable_group.py +4 -2
  111. pulumi_azuredevops/variable_group_permissions.py +75 -75
  112. pulumi_azuredevops/wiki.py +15 -2
  113. pulumi_azuredevops/wiki_page.py +2 -2
  114. pulumi_azuredevops/work_item_query_permissions.py +7 -7
  115. {pulumi_azuredevops-3.6.0a1737091250.dist-info → pulumi_azuredevops-3.6.0a1737710622.dist-info}/METADATA +1 -1
  116. pulumi_azuredevops-3.6.0a1737710622.dist-info/RECORD +148 -0
  117. pulumi_azuredevops-3.6.0a1737091250.dist-info/RECORD +0 -140
  118. {pulumi_azuredevops-3.6.0a1737091250.dist-info → pulumi_azuredevops-3.6.0a1737710622.dist-info}/WHEEL +0 -0
  119. {pulumi_azuredevops-3.6.0a1737091250.dist-info → pulumi_azuredevops-3.6.0a1737710622.dist-info}/top_level.txt +0 -0
pulumi_azuredevops/team_administrators.py CHANGED
@@ -25,17 +25,18 @@ class TeamAdministratorsArgs:
25
25
  mode: Optional[pulumi.Input[str]] = None):
26
26
  """
27
27
  The set of arguments for constructing a TeamAdministrators resource.
28
- :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define adminitrators of the team.
28
+ :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define administrators of the team.
29
29
 
30
- > NOTE: It's possible to define team administrators both within the
31
- > `Team` resource via the `administrators` block and by using the
32
- > `TeamAdministrators` resource. However it's not possible to use
33
- > both methods to manage team administrators, since there'll be conflicts.
30
+ > **NOTE** It's possible to define team administrators both within the
31
+ `Team` resource via the `administrators` block and by using the
32
+ `TeamAdministrators` resource. However it's not possible to use
33
+ both methods to manage team administrators, since there'll be conflicts.
34
34
  :param pulumi.Input[str] project_id: The Project ID.
35
35
  :param pulumi.Input[str] team_id: The ID of the Team.
36
- :param pulumi.Input[str] mode: The mode how the resource manages team administrators.
37
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
38
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
36
+ :param pulumi.Input[str] mode: The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
37
+
38
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
39
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
39
40
  """
40
41
  pulumi.set(__self__, "administrators", administrators)
41
42
  pulumi.set(__self__, "project_id", project_id)
@@ -47,12 +48,12 @@ class TeamAdministratorsArgs:
47
48
  @pulumi.getter
48
49
  def administrators(self) -> pulumi.Input[Sequence[pulumi.Input[str]]]:
49
50
  """
50
- List of subject descriptors to define adminitrators of the team.
51
+ List of subject descriptors to define administrators of the team.
51
52
 
52
- > NOTE: It's possible to define team administrators both within the
53
- > `Team` resource via the `administrators` block and by using the
54
- > `TeamAdministrators` resource. However it's not possible to use
55
- > both methods to manage team administrators, since there'll be conflicts.
53
+ > **NOTE** It's possible to define team administrators both within the
54
+ `Team` resource via the `administrators` block and by using the
55
+ `TeamAdministrators` resource. However it's not possible to use
56
+ both methods to manage team administrators, since there'll be conflicts.
56
57
  """
57
58
  return pulumi.get(self, "administrators")
58
59
 
@@ -88,9 +89,10 @@ class TeamAdministratorsArgs:
88
89
  @pulumi.getter
89
90
  def mode(self) -> Optional[pulumi.Input[str]]:
90
91
  """
91
- The mode how the resource manages team administrators.
92
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
93
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
92
+ The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
93
+
94
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
95
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
94
96
  """
95
97
  return pulumi.get(self, "mode")
96
98
 
@@ -108,15 +110,16 @@ class _TeamAdministratorsState:
108
110
  team_id: Optional[pulumi.Input[str]] = None):
109
111
  """
110
112
  Input properties used for looking up and filtering TeamAdministrators resources.
111
- :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define adminitrators of the team.
113
+ :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define administrators of the team.
112
114
 
113
- > NOTE: It's possible to define team administrators both within the
114
- > `Team` resource via the `administrators` block and by using the
115
- > `TeamAdministrators` resource. However it's not possible to use
116
- > both methods to manage team administrators, since there'll be conflicts.
117
- :param pulumi.Input[str] mode: The mode how the resource manages team administrators.
118
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
119
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
115
+ > **NOTE** It's possible to define team administrators both within the
116
+ `Team` resource via the `administrators` block and by using the
117
+ `TeamAdministrators` resource. However it's not possible to use
118
+ both methods to manage team administrators, since there'll be conflicts.
119
+ :param pulumi.Input[str] mode: The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
120
+
121
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
122
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
120
123
  :param pulumi.Input[str] project_id: The Project ID.
121
124
  :param pulumi.Input[str] team_id: The ID of the Team.
122
125
  """
@@ -133,12 +136,12 @@ class _TeamAdministratorsState:
133
136
  @pulumi.getter
134
137
  def administrators(self) -> Optional[pulumi.Input[Sequence[pulumi.Input[str]]]]:
135
138
  """
136
- List of subject descriptors to define adminitrators of the team.
139
+ List of subject descriptors to define administrators of the team.
137
140
 
138
- > NOTE: It's possible to define team administrators both within the
139
- > `Team` resource via the `administrators` block and by using the
140
- > `TeamAdministrators` resource. However it's not possible to use
141
- > both methods to manage team administrators, since there'll be conflicts.
141
+ > **NOTE** It's possible to define team administrators both within the
142
+ `Team` resource via the `administrators` block and by using the
143
+ `TeamAdministrators` resource. However it's not possible to use
144
+ both methods to manage team administrators, since there'll be conflicts.
142
145
  """
143
146
  return pulumi.get(self, "administrators")
144
147
 
@@ -150,9 +153,10 @@ class _TeamAdministratorsState:
150
153
  @pulumi.getter
151
154
  def mode(self) -> Optional[pulumi.Input[str]]:
152
155
  """
153
- The mode how the resource manages team administrators.
154
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
155
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
156
+ The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
157
+
158
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
159
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
156
160
  """
157
161
  return pulumi.get(self, "mode")
158
162
 
@@ -196,6 +200,16 @@ class TeamAdministrators(pulumi.CustomResource):
196
200
  team_id: Optional[pulumi.Input[str]] = None,
197
201
  __props__=None):
198
202
  """
203
+ ## *---
204
+
205
+ layout: "azuredevops"
206
+ page_title: "AzureDevops: TeamAdministrators"
207
+ description: |-
208
+ Manages administrators of a team within a project in a Azure DevOps organization.
209
+ ---
210
+
211
+ # TeamAdministrators
212
+
199
213
  Manages administrators of a team within a project in a Azure DevOps organization.
200
214
 
201
215
  ## Example Usage
@@ -236,15 +250,16 @@ class TeamAdministrators(pulumi.CustomResource):
236
250
 
237
251
  :param str resource_name: The name of the resource.
238
252
  :param pulumi.ResourceOptions opts: Options for the resource.
239
- :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define adminitrators of the team.
253
+ :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define administrators of the team.
240
254
 
241
- > NOTE: It's possible to define team administrators both within the
242
- > `Team` resource via the `administrators` block and by using the
243
- > `TeamAdministrators` resource. However it's not possible to use
244
- > both methods to manage team administrators, since there'll be conflicts.
245
- :param pulumi.Input[str] mode: The mode how the resource manages team administrators.
246
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
247
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
255
+ > **NOTE** It's possible to define team administrators both within the
256
+ `Team` resource via the `administrators` block and by using the
257
+ `TeamAdministrators` resource. However it's not possible to use
258
+ both methods to manage team administrators, since there'll be conflicts.
259
+ :param pulumi.Input[str] mode: The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
260
+
261
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
262
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
248
263
  :param pulumi.Input[str] project_id: The Project ID.
249
264
  :param pulumi.Input[str] team_id: The ID of the Team.
250
265
  """
@@ -255,6 +270,16 @@ class TeamAdministrators(pulumi.CustomResource):
255
270
  args: TeamAdministratorsArgs,
256
271
  opts: Optional[pulumi.ResourceOptions] = None):
257
272
  """
273
+ ## *---
274
+
275
+ layout: "azuredevops"
276
+ page_title: "AzureDevops: TeamAdministrators"
277
+ description: |-
278
+ Manages administrators of a team within a project in a Azure DevOps organization.
279
+ ---
280
+
281
+ # TeamAdministrators
282
+
258
283
  Manages administrators of a team within a project in a Azure DevOps organization.
259
284
 
260
285
  ## Example Usage
@@ -352,15 +377,16 @@ class TeamAdministrators(pulumi.CustomResource):
352
377
  :param str resource_name: The unique name of the resulting resource.
353
378
  :param pulumi.Input[str] id: The unique provider ID of the resource to lookup.
354
379
  :param pulumi.ResourceOptions opts: Options for the resource.
355
- :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define adminitrators of the team.
380
+ :param pulumi.Input[Sequence[pulumi.Input[str]]] administrators: List of subject descriptors to define administrators of the team.
381
+
382
+ > **NOTE** It's possible to define team administrators both within the
383
+ `Team` resource via the `administrators` block and by using the
384
+ `TeamAdministrators` resource. However it's not possible to use
385
+ both methods to manage team administrators, since there'll be conflicts.
386
+ :param pulumi.Input[str] mode: The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
356
387
 
357
- > NOTE: It's possible to define team administrators both within the
358
- > `Team` resource via the `administrators` block and by using the
359
- > `TeamAdministrators` resource. However it's not possible to use
360
- > both methods to manage team administrators, since there'll be conflicts.
361
- :param pulumi.Input[str] mode: The mode how the resource manages team administrators.
362
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
363
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
388
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
389
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
364
390
  :param pulumi.Input[str] project_id: The Project ID.
365
391
  :param pulumi.Input[str] team_id: The ID of the Team.
366
392
  """
@@ -378,12 +404,12 @@ class TeamAdministrators(pulumi.CustomResource):
378
404
  @pulumi.getter
379
405
  def administrators(self) -> pulumi.Output[Sequence[str]]:
380
406
  """
381
- List of subject descriptors to define adminitrators of the team.
407
+ List of subject descriptors to define administrators of the team.
382
408
 
383
- > NOTE: It's possible to define team administrators both within the
384
- > `Team` resource via the `administrators` block and by using the
385
- > `TeamAdministrators` resource. However it's not possible to use
386
- > both methods to manage team administrators, since there'll be conflicts.
409
+ > **NOTE** It's possible to define team administrators both within the
410
+ `Team` resource via the `administrators` block and by using the
411
+ `TeamAdministrators` resource. However it's not possible to use
412
+ both methods to manage team administrators, since there'll be conflicts.
387
413
  """
388
414
  return pulumi.get(self, "administrators")
389
415
 
@@ -391,9 +417,10 @@ class TeamAdministrators(pulumi.CustomResource):
391
417
  @pulumi.getter
392
418
  def mode(self) -> pulumi.Output[Optional[str]]:
393
419
  """
394
- The mode how the resource manages team administrators.
395
- - `mode == add`: the resource will ensure that all specified administrators will be part of the referenced team
396
- - `mode == overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
420
+ The mode how the resource manages team administrators. Possible values: `add`, `overwrite`. Defaults to `add`.
421
+
422
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified administrators will be part of the referenced team
423
+ <br> 2. `mode = overwrite`: the resource will replace all existing administrators with the administrators specified within the `administrators` block
397
424
  """
398
425
  return pulumi.get(self, "mode")
399
426
 
pulumi_azuredevops/team_members.py CHANGED
@@ -27,15 +27,16 @@ class TeamMembersArgs:
27
27
  The set of arguments for constructing a TeamMembers resource.
28
28
  :param pulumi.Input[Sequence[pulumi.Input[str]]] members: List of subject descriptors to define members of the team.
29
29
 
30
- > NOTE: It's possible to define team members both within the
31
- > `Team` resource via the `members` block and by using the
32
- > `TeamMembers` resource. However it's not possible to use
33
- > both methods to manage team members, since there'll be conflicts.
30
+ > **NOTE:** It's possible to define team members both within the
31
+ `Team` resource via the `members` block and by using the
32
+ `TeamMembers` resource. However, it's not possible to use
33
+ both methods to manage team members, since there'll be conflicts.
34
34
  :param pulumi.Input[str] project_id: The Project ID.
35
35
  :param pulumi.Input[str] team_id: The ID of the Team.
36
- :param pulumi.Input[str] mode: The mode how the resource manages team members.
37
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
38
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
36
+ :param pulumi.Input[str] mode: The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
37
+
38
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
39
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
39
40
  """
40
41
  pulumi.set(__self__, "members", members)
41
42
  pulumi.set(__self__, "project_id", project_id)
@@ -49,10 +50,10 @@ class TeamMembersArgs:
49
50
  """
50
51
  List of subject descriptors to define members of the team.
51
52
 
52
- > NOTE: It's possible to define team members both within the
53
- > `Team` resource via the `members` block and by using the
54
- > `TeamMembers` resource. However it's not possible to use
55
- > both methods to manage team members, since there'll be conflicts.
53
+ > **NOTE:** It's possible to define team members both within the
54
+ `Team` resource via the `members` block and by using the
55
+ `TeamMembers` resource. However, it's not possible to use
56
+ both methods to manage team members, since there'll be conflicts.
56
57
  """
57
58
  return pulumi.get(self, "members")
58
59
 
@@ -88,9 +89,10 @@ class TeamMembersArgs:
88
89
  @pulumi.getter
89
90
  def mode(self) -> Optional[pulumi.Input[str]]:
90
91
  """
91
- The mode how the resource manages team members.
92
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
93
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
92
+ The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
93
+
94
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
95
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
94
96
  """
95
97
  return pulumi.get(self, "mode")
96
98
 
@@ -110,13 +112,14 @@ class _TeamMembersState:
110
112
  Input properties used for looking up and filtering TeamMembers resources.
111
113
  :param pulumi.Input[Sequence[pulumi.Input[str]]] members: List of subject descriptors to define members of the team.
112
114
 
113
- > NOTE: It's possible to define team members both within the
114
- > `Team` resource via the `members` block and by using the
115
- > `TeamMembers` resource. However it's not possible to use
116
- > both methods to manage team members, since there'll be conflicts.
117
- :param pulumi.Input[str] mode: The mode how the resource manages team members.
118
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
119
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
115
+ > **NOTE:** It's possible to define team members both within the
116
+ `Team` resource via the `members` block and by using the
117
+ `TeamMembers` resource. However, it's not possible to use
118
+ both methods to manage team members, since there'll be conflicts.
119
+ :param pulumi.Input[str] mode: The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
120
+
121
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
122
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
120
123
  :param pulumi.Input[str] project_id: The Project ID.
121
124
  :param pulumi.Input[str] team_id: The ID of the Team.
122
125
  """
@@ -135,10 +138,10 @@ class _TeamMembersState:
135
138
  """
136
139
  List of subject descriptors to define members of the team.
137
140
 
138
- > NOTE: It's possible to define team members both within the
139
- > `Team` resource via the `members` block and by using the
140
- > `TeamMembers` resource. However it's not possible to use
141
- > both methods to manage team members, since there'll be conflicts.
141
+ > **NOTE:** It's possible to define team members both within the
142
+ `Team` resource via the `members` block and by using the
143
+ `TeamMembers` resource. However, it's not possible to use
144
+ both methods to manage team members, since there'll be conflicts.
142
145
  """
143
146
  return pulumi.get(self, "members")
144
147
 
@@ -150,9 +153,10 @@ class _TeamMembersState:
150
153
  @pulumi.getter
151
154
  def mode(self) -> Optional[pulumi.Input[str]]:
152
155
  """
153
- The mode how the resource manages team members.
154
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
155
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
156
+ The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
157
+
158
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
159
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
156
160
  """
157
161
  return pulumi.get(self, "mode")
158
162
 
@@ -238,13 +242,14 @@ class TeamMembers(pulumi.CustomResource):
238
242
  :param pulumi.ResourceOptions opts: Options for the resource.
239
243
  :param pulumi.Input[Sequence[pulumi.Input[str]]] members: List of subject descriptors to define members of the team.
240
244
 
241
- > NOTE: It's possible to define team members both within the
242
- > `Team` resource via the `members` block and by using the
243
- > `TeamMembers` resource. However it's not possible to use
244
- > both methods to manage team members, since there'll be conflicts.
245
- :param pulumi.Input[str] mode: The mode how the resource manages team members.
246
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
247
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
245
+ > **NOTE:** It's possible to define team members both within the
246
+ `Team` resource via the `members` block and by using the
247
+ `TeamMembers` resource. However, it's not possible to use
248
+ both methods to manage team members, since there'll be conflicts.
249
+ :param pulumi.Input[str] mode: The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
250
+
251
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
252
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
248
253
  :param pulumi.Input[str] project_id: The Project ID.
249
254
  :param pulumi.Input[str] team_id: The ID of the Team.
250
255
  """
@@ -354,13 +359,14 @@ class TeamMembers(pulumi.CustomResource):
354
359
  :param pulumi.ResourceOptions opts: Options for the resource.
355
360
  :param pulumi.Input[Sequence[pulumi.Input[str]]] members: List of subject descriptors to define members of the team.
356
361
 
357
- > NOTE: It's possible to define team members both within the
358
- > `Team` resource via the `members` block and by using the
359
- > `TeamMembers` resource. However it's not possible to use
360
- > both methods to manage team members, since there'll be conflicts.
361
- :param pulumi.Input[str] mode: The mode how the resource manages team members.
362
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
363
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
362
+ > **NOTE:** It's possible to define team members both within the
363
+ `Team` resource via the `members` block and by using the
364
+ `TeamMembers` resource. However, it's not possible to use
365
+ both methods to manage team members, since there'll be conflicts.
366
+ :param pulumi.Input[str] mode: The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
367
+
368
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
369
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
364
370
  :param pulumi.Input[str] project_id: The Project ID.
365
371
  :param pulumi.Input[str] team_id: The ID of the Team.
366
372
  """
@@ -380,10 +386,10 @@ class TeamMembers(pulumi.CustomResource):
380
386
  """
381
387
  List of subject descriptors to define members of the team.
382
388
 
383
- > NOTE: It's possible to define team members both within the
384
- > `Team` resource via the `members` block and by using the
385
- > `TeamMembers` resource. However it's not possible to use
386
- > both methods to manage team members, since there'll be conflicts.
389
+ > **NOTE:** It's possible to define team members both within the
390
+ `Team` resource via the `members` block and by using the
391
+ `TeamMembers` resource. However, it's not possible to use
392
+ both methods to manage team members, since there'll be conflicts.
387
393
  """
388
394
  return pulumi.get(self, "members")
389
395
 
@@ -391,9 +397,10 @@ class TeamMembers(pulumi.CustomResource):
391
397
  @pulumi.getter
392
398
  def mode(self) -> pulumi.Output[Optional[str]]:
393
399
  """
394
- The mode how the resource manages team members.
395
- - `mode == add`: the resource will ensure that all specified members will be part of the referenced team
396
- - `mode == overwrite`: the resource will replace all existing members with the members specified within the `members` block
400
+ The mode how the resource manages team members. Possible values: `add`, `overwrite`. Defaults to `add`.
401
+
402
+ > **NOTE:** 1. `mode = add`: the resource will ensure that all specified members will be part of the referenced team
403
+ <br>2. `mode = overwrite`: the resource will replace all existing members with the members specified within the `members` block
397
404
  """
398
405
  return pulumi.get(self, "mode")
399
406
 
pulumi_azuredevops/variable_group.py CHANGED
@@ -239,6 +239,7 @@ class VariableGroup(pulumi.CustomResource):
239
239
  """
240
240
  ## Example Usage
241
241
 
242
+ ### Basic usage
242
243
  ```python
243
244
  import pulumi
244
245
  import pulumi_azuredevops as azuredevops
@@ -267,7 +268,7 @@ class VariableGroup(pulumi.CustomResource):
267
268
  ])
268
269
  ```
269
270
 
270
- ### With AzureRM Key Vault
271
+ ### Link to AzureRM Key Vault
271
272
 
272
273
  ```python
273
274
  import pulumi
@@ -359,6 +360,7 @@ class VariableGroup(pulumi.CustomResource):
359
360
  """
360
361
  ## Example Usage
361
362
 
363
+ ### Basic usage
362
364
  ```python
363
365
  import pulumi
364
366
  import pulumi_azuredevops as azuredevops
@@ -387,7 +389,7 @@ class VariableGroup(pulumi.CustomResource):
387
389
  ])
388
390
  ```
389
391
 
390
- ### With AzureRM Key Vault
392
+ ### Link to AzureRM Key Vault
391
393
 
392
394
  ```python
393
395
  import pulumi