Sean Sullivan

I think the general example is that the playbooks stay, however I am thinking of removing the job launch aspect of them, and/or just having it invoke dispatch.

@vvaldez and that is exactly what was intended by the playbooks repo, was a starting point for people, and once they grew comfortable that they move away from it to...

So after discussion here and internally I am going to put the following up for a vote. 1. We simplify the playbooks to invoke the normal configuration roles, and remove...

I do think we need to update the roles readmes and test with up to date examples, Should that be the standard, No examples, but every role has a tested...

2nded on this, would have loved the headers 3 years ago when using this for figuring out scaling and forks.

if anyone is wondering, at least for 0.15.0, change line 82 to this $(KUSTOMIZE) build config/default | minikube kubectl -- apply -f - as Davidffry said, this change makes it...

it should match this as empty string, yes https://github.com/redhat-cop/controller_configuration/blob/a79f987765ae7d6ba5763c6d45c56ea7d325ec3f/roles/job_templates/tasks/main.yml#L17C145-L17C145 Funnily enough the job template api/v2/job_templates OPTIONS lists it as "", however workflow_job_template OPTIONS lists it as null.

@jorgenspange This was my fix, doesn't solve inside navigator, but solves with AAP controller https://www.redhat.com/architect/ansible-execution-environment-automated-build

Closing this issue as it is now resolved by the above merge

we have had hit or miss on doing this inside the redhat_cop playbooks, as customers seem to think it is the ONLY way to use the collection/roles, but that is...