Øystein Bedin

@etsauer are you ok if the prompts are part of the ansible run? Basically something **similar** to this: https://github.com/redhat-cop/infra-ansible/blob/master/playbooks/prep.yml

@JayKayy Unfortunately, no - it needs to be reproduced (which should be pretty straight forward as it was happening 100% of the time).

@JayKayy I believe so - IIRC it happened with the RHEL 7.3 installs. We had it happen as part of the bigger install/update procedures we do (i.e.: the `install.yml` playbook),...

@etsauer for your two examples, what do you think about an applier inventory like the following? Does this align with what you were thinking? ``` openshift_cluster_content: - object: Machine Autoscaler...

Related Ansible Galaxy role to "get" data: https://galaxy.ansible.com/oybed/openshift_get_resources

@donovanmuller The `openshift-applier` does not support supplying / passing individual parameters, or a runtime override of param files, as this isn't necessarily the use case it is meant for. The...

@etsauer just to outline a few more details from our discussion (and please correct anything that's inaccurate): - The idea is that the container image supports defaults that will look...

This is a "known deficiency" and needs better documentation. In the code, the action is already set to `delete` instead of `create` or `apply` (that's really what the `provision` flag...

BTW: @itewk you mentioned "not being able to use apply". Could you please include a capture of that error in this issue?

Also, here's a BZ @etsauer wrote with more info re: ProjectRequests / namespaces and `delete`: https://bugzilla.redhat.com/show_bug.cgi?id=1537774