Eric Sauer
Eric Sauer
@mbach04 can you address @lpsantil 's comment above?
@oybed so, with the changes to the role, would that require any changes to existing inventories?
@oybed understood, and I like the approach.
Another use case I would like to see work: cluster1.yml: ``` openshift_login_url: https://console.cluster1.example.com ... ``` cluster2.yml: ``` openshift_login_url: https://console.cluster2.example.com ``` Run: ``` oc login -u bob https://console.cluster1.example.com Password: oc login...
@dstockdreher is this resolved?
@srang good idea. @redhat-cop/cant-contain-this any takers?
@oybed yes that looks perfect
@donovanmuller I think there is one feature in place already that may addres your need. This is the idea of parameter directories. ``` --- openshift_cluster_content: - object: projectrequest content: -...
@ikke-t looking at the doc, I believe what you are saying is that we are including a CAfile in the configuration parameters: ``` openshift_master_named_certificates=[{"certfile": "/path/to/console.ocp-c1.myorg.com.crt", "keyfile": "/path/to/console.ocp-c1.myorg.com.key", "names": ["console.ocp-c1.myorg.com"], "cafile":...
I've found something that works. Not sure if its the most ideal solution. Certfile: ``` apiVersion: v1 kind: Template metadata: creationTimestamp: null name: secure-route objects: - apiVersion: v1 kind: Route...