oci_devops_repository_setting
This resource provides the Repository Setting resource in Oracle Cloud Infrastructure Devops service. Api doc link for the resource: https://docs.oracle.com/iaas/api/#/en/devops/latest/RepositorySetting
Example terraform configs related to the resource : https://github.com/oracle/terraform-provider-oci/tree/master/examples/devops
Updates the settings for a repository.
Example Usage
resource "oci_devops_repository_setting" "test_repository_setting" {
	#Required
	repository_id = oci_devops_repository.test_repository.id
	#Optional
	approval_rules {
		#Required
		items {
			#Required
			min_approvals_count = var.repository_setting_approval_rules_items_min_approvals_count
			name = var.repository_setting_approval_rules_items_name
			#Optional
			destination_branch = var.repository_setting_approval_rules_items_destination_branch
			reviewers {
				#Required
				principal_id = oci_devops_principal.test_principal.id
			}
		}
	}
	merge_checks {
		#Required
		last_build_succeeded = var.repository_setting_merge_checks_last_build_succeeded
	}
	merge_settings {
		#Required
		allowed_merge_strategies = var.repository_setting_merge_settings_allowed_merge_strategies
		default_merge_strategy = var.repository_setting_merge_settings_default_merge_strategy
	}
}
Argument Reference
The following arguments are supported:
- approval_rules- (Optional) (Updatable) List of approval rules which must be statisfied before pull requests which match the rules can be merged- items- (Required) (Updatable) List of approval rules.- destination_branch- (Optional) (Updatable) Branch name where pull requests targeting the branch must satisfy the approval rule. This value being null means the rule applies to all pull requests
- min_approvals_count- (Required) (Updatable) Minimum number of approvals which must be provided by the reviewers specified in the list before the rule can be satisfied
- name- (Required) (Updatable) Name which is used to uniquely identify an approval rule.
- reviewers- (Optional) (Updatable) List of users who must provide approvals up to the minApprovalsCount specified in the rule. An empty list means the approvals can come from any user.- principal_id- (Required) (Updatable) Pull Request reviewer id
 
 
 
- merge_checks- (Optional) (Updatable) Criteria which must be satisfied to merge a pull request.- last_build_succeeded- (Required) (Updatable) Indicates whether or not a pull request must have a successful build run and no queued builds before it can be merged
 
- merge_settings- (Optional) (Updatable) Enabled and disabled merge strategies for a project or repository, also contains a default strategy.- allowed_merge_strategies- (Required) (Updatable) List of merge strategies which are allowed for a Project or Repository.
- default_merge_strategy- (Required) (Updatable) Default type of merge strategy associated with the a Project or Repository.
 
- repository_id- (Required) Unique repository identifier.
** IMPORTANT ** Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
Attributes Reference
The following attributes are exported:
- approval_rules- List of approval rules which must be statisfied before pull requests which match the rules can be merged- items- List of approval rules.- destination_branch- Branch name where pull requests targeting the branch must satisfy the approval rule. This value being null means the rule applies to all pull requests
- min_approvals_count- Minimum number of approvals which must be provided by the reviewers specified in the list before the rule can be satisfied
- name- Name which is used to uniquely identify an approval rule.
- reviewers- List of users who must provide approvals up to the minApprovalsCount specified in the rule. An empty list means the approvals can come from any user.- principal_id- the OCID of the principal
- principal_name- the name of the principal
- principal_state- The state of the principal, it can be active or inactive or suppressed for emails
- principal_type- the type of principal
 
 
 
- merge_checks- Criteria which must be satisfied to merge a pull request.- last_build_succeeded- Indicates whether or not a pull request must have a successful build run and no queued builds before it can be merged
 
- merge_settings- Enabled and disabled merge strategies for a project or repository, also contains a default strategy.- allowed_merge_strategies- List of merge strategies which are allowed for a Project or Repository.
- default_merge_strategy- Default type of merge strategy associated with the a Project or Repository.
 
Timeouts
The timeouts block allows you to specify timeouts for certain operations:
	* create - (Defaults to 20 minutes), when creating the Repository Setting
	* update - (Defaults to 20 minutes), when updating the Repository Setting
	* delete - (Defaults to 20 minutes), when destroying the Repository Setting
Import
RepositorySettings can be imported using the id, e.g.
$ terraform import oci_devops_repository_setting.test_repository_setting "repositories/{repositoryId}/repositorySettings"