Madhu Kanoor

@eriknelson When I tried looking at the docker logs I see the following error message ``` time="2018-03-09T19:43:22.900485289Z" level=error msg="OpenShift access denied: User \"system:anonymous\" cannot update imagestreams/layers.image.openshift.io in project \"openshift\"" go.version=go1.9.2...

@dymurray SyncingCatalog Error syncing catalog from ServiceBroker. Error reconciling ClusterServiceClass (K8S: "ab69b2bb5a3b1fe973ce05af20ba5047" ExternalName: "localregistry-cfme_rhev-apb") (broker "ansible-service-broker"): ClusterServiceClass.servicecatalog.k8s.io "ab69b2bb5a3b1fe973ce05af20ba5047" is invalid: spec.externalName: Invalid value: "localregistry-cfme_rhev-apb": a DNS-1123 subdomain must consist of...

The Open Service Broker API spec has restrictions on names. https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md e.g. name* string The CLI-friendly name of the plan. MUST only contain lowercase characters, numbers and hyphens (no spaces)....

Another issue is the parameter names used internally by the APB "_apb_plan_id":"default", "_apb_service_class_id":"7a531cb95ab6e6fdeae1fc7211474d9c", "_apb_service_instance_id":"1039b299-f131-4bca-a701-6faa8c876d6d" "namespace": "My Project" If the user created a parameter called namespace they won't know its reserved...

@cschlack I think rugged uses the callback paradigm for credentials, so that you can hook it into a UI and keep asking the user for userid/password in case he enters...

https://github.com/libgit2/rugged/pull/571

@ffalor We don't have full Jinja2 support in the rulebook. In your case you should be able to change the rulebook to ``` sources: - crowd strike.falcon.eventstream: falcon_client_id: "{{ FALCON_CLIENT_ID...

The env var name is passed via the command line and collected into a variable pool which is later used in substitution. ``` ansible-rulebook -i inventory.yml --rulebook rulebooks/event_stream_example.yml --env-vars FALCON_CLIENT_ID,FALCON_CLIENT_SECRET`...

@dhaustein I think we should also ensure that all the source plugins that we ship in [ansible.eda](https://github.com/ansible/event-driven-ansible/tree/main/extensions/eda/plugins/event_source) collection work with the slim image and all dependencies are satisfied.

> > @dhaustein I think we should also ensure that all the source plugins that we ship in [ansible.eda](https://github.com/ansible/event-driven-ansible/tree/main/extensions/eda/plugins/event_source) collection work with the slim image and all dependencies are satisfied....