Sounds good. Thanks for taking the time to discuss this with me. Mike

You can also check out the v208 tag of cf-release, then run the acceptance-tests from src/github.com/cloudfoundry/cf-acceptance-tests Joseph CF Release Integration Team wrote:

Jordan, The Cloud Foundry bosh release comes with an errand called "acceptance_tests" that contains the version of CATs which that version of CF was tested with. You can run these by doing "bosh run

Hi Daniel and Dieu, Finally after much trial and error I finally got it working. I created a user-provided service and then called on it from my application. I've documented the steps for anyone else

Sorry, sounds like escaping is the only option here for an environment variable. If you don't want to escape, I think you could create a user provided service, provide the value through there and

Hi Dieu and Daniel, I did set the environment variable like you suggest Daniel, I should've showed that in my example. I see now that the app wrongly removes the $ characters and the character after

I was unclear on what I am asking, the real question is as follows: What is the best way to run the apps test suite within the CATS on an older version of cloud foundry? (for example I am running

Okay, please let me know if you are able to fix your security group settings and whether the original problem gets resolved. Amit wrote:

Hi Jonas, You'll need to escape the special characters like $. See this tracker story for some background: https://www.pivotaltracker.com/story/show/76655240 -Dieu

It's possible that your shell is escaping the characters, like the '$'. Try `cf set-env appname WORDPRESS_BEARER '1NNKhb5&Nfw$F(wqbqW&9nSeoonwAYz7#j2M1KKY!QU(Wbs(a)8xwjr6Q$hg(IPqcd'`. Note the

Hi all, I am having an issue with an environment variable containing special characters that doesn't seem to picked up correctly by CF. I run `cf set-env appname WORDPRESS_BEARER

jordanicollier(a)gmail.com

`[2015-09-24 15:06:25.24 (UTC)]> cf logout Logging out... OK • Failure [22.809 seconds] Admin

Containers have a default iptables rule for REJECT all traffic. If there is not a security group configured to allow the traffic to the destination, you'll get a connection refused. Security groups

Ok, after more investigating the problem was that network manager was running on the machine and was trying to take control of new network interfaces after they came up, so it would cause problems

My vote on to wait a couple more months. I guess we'll see if anyone else would like more months. Mike

Hi Dieu, many thanks for the technical info. I will consider this factor to add this restriction in the development. Juan Antonio

Thanks Mike. Totally understandable.

Your edge load balancer should be configured to add x-forwarded-for and x-forwarded-proto headers. bren(a)juanantonio.info> wrote:

Separate from this proposal, the CAPI team has stories for spiking on a few different api documentation options for the cloud controller api [1]. Swagger is one of the options we are looking into, but