As the installer always fetches dna and aenigma on each run of setup, it's hard to develop quick fixes. The workaround is to run setup with -dl -pl, which uses the already fetched versions of the components, thus respects local changes.

I found this after studying the scripts, would be nice to see this documented somewhere.

edit: Also document -ov for debug output?

We need to document field provision limitations on team site collections. Some properties can't be set or updated, it usually comes back with the following exception:

Unknown Exception,_HResult:-2146232832)

I've been attempting to deploy OKD to BYO Infrastructure by setting

openshift_deployment_type: origin
deployment_type: origin

Currently running into the error:

Error reading manifest latest in registry.redhat.io/openshift/origin: unknown: Not Found

I'm assuming there's issues with my configuration but can't seem to find documentation on how to use casl-ansible for an OKD depl

In stage & production environments my customers use helm chart* (yaml based) for deploying containerised application (* https://kubernetes.io/docs/reference/tools/#helm)

Could you create a helm chart deployment package for the provider in order to be aligned with the validation requirements for production usage that my customers have?

• Document how to build the application
• Document how to build the container
• Document how to use openshifter without container

In step 2 you mention that you need to edit the app.yml file. Where is this file?

Edit the app.yml file and then copy it under the proper folder: cp app.yml ./playbooks/roles/discourse/files

One minor complication I found as a newcomer was that I couldnt do fudge on the cmd.exe command line. That requires fudge.ps1 to be in PATH and for .ps1 to be in PATHEXT. Choco can help with those.