In an attempt tot solve #61 I wanted to bind a service on my deployment via OPTIONAL_ARGS="-e CCS_BIND_SRV=MyService" (this is an undocumented env variable that is used in the scripts.

But whatever I specify, this variable is always empty. This might be a problem of the IBM Delivery Pipeline, but I wanted to know if someone can confirm this problem.

even setting this variable to something like "a" results in this variable being empty in the script.

Hi there,

I am an IBM Cloud Solution Engineer working directly with IBM clients in the microservices world. So far, the majority of container-based solutions clients go for are those where containers are not publicly exposed since that is one of the bigger advantages with CF solutions. Thus, more than 90% of the containers deployed in BMX (for these client solutions) will not have a public route.

We would like that the option IGNORE_MAPPING_ROUTE is more present in the script/documentation so that clients are aware of this option without needing to dig into the code.

Thanks

If I am deploying a container group I have the possibility to bind that group to an existing service.

Running it on my command line i can do that as follows:

cf ic group create --name my_group -e CCS_BIND_SRV=MyService registry.ng.bluemix.net/my_image

However the group image uses the CCS_BIND_APP parameter to bind the group to an app.

Is there any reason to keep the CCS_BIND_APP parameter for deploying a group? Otherwise I suggest replacing it with the CCS_BIND_SRV parameter.

In the meantime: Is there a workaround for binding services to container groups?