Skip to content
This repository was archived by the owner on Jun 25, 2024. It is now read-only.

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Expose AnsibleMaxFailPercentage and AnyErrorsFatal
Browse files Browse the repository at this point in the history
This change exposes the Ansible configuration options for
AnsibleMaxFailPercentage and AnsibleAnyErrorsFatal via the Services CRD.
This will be passed to the AnsibleEE pods to tune specific service
failure handling.

Signed-off-by: Brendan Shephard <[email protected]>
bshephar committed Nov 17, 2023
1 parent d73c009 commit a7a5f65
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions api/v1beta1/openstackdataplaneservice_types.go
Original file line number Diff line number Diff line change
@@ -76,6 +76,15 @@ type OpenStackDataPlaneServiceSpec struct {
// OpenStackAnsibleEERunnerImage image to use as the ansibleEE runner image
// +kubebuilder:validation:Optional
OpenStackAnsibleEERunnerImage string `json:"openStackAnsibleEERunnerImage,omitempty" yaml:"openStackAnsibleEERunnerImage,omitempty"`

// AnsibleMaxFailPercentage is used to tune service specific, allowable failure percentages during the Ansible execution
// https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_error_handling.html#setting-a-maximum-failure-percentage
// +kubebuilder:validation:Optional
AnsibleMaxFailPercentage int64 `json:"ansibleMaxFailPercentage,omitempty"`

// AnyErrorsFatal is used to tune service specific, any_errors_fatal
// +kubebuilder:validation:Optional
AnyErrorsFatal bool `json:"anyErrorsFatal,omitempty"`
}

// OpenStackDataPlaneServiceStatus defines the observed state of OpenStackDataPlaneService

0 comments on commit a7a5f65

Please sign in to comment.