Value Statement

Allow provisioning of OpenStack clusters on environments that use a CA without having to perform manual steps for each cluster deployment

Definition of Done for Engineering Story Owner (Checklist)

• OpenStack credentials have a new field for CA which validates appropriately
• If CA value is entered, validation of clouds.yaml checks that the reference to the CA is present (2 formats allowed)
• When creating an OpenStack cluster, the CA stored in the credential is used to create a new Secret that is referred to from the ClusterDeployment spec (clouds.yaml is already embedded in the credentials secret)

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x ] Unit/function tests have been automated and incorporated into the
  build.
• [ x] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [na] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [x] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue. https://issues.redhat.com/browse/ACM-4815
• [x] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [na] The must-gather script has been updated.