conjurdemos / cloudfoundry-conjur-demo

Demo for Conjur CloudFoundry integration

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Local demo runs correctly on recent version of PCF dev

micahlee opened this issue · comments

Currently, given a recent version of PCF dev:

$ cf version
cf version 6.40.1+85d04488a.2018-10-31
$ cf dev version
CLI: 0.0.11
cf: v4.5.0
cf-mysql: 36.15.0

Then the local demo scripts to not successfully deploy the service broker and demo app.

Closing as won't fix for now. Below are the notes for running the demo with this PCF Dev version info:

cf version 6.40.1+85d04488a.2018-10-31
$ cf dev version
CLI: 0.0.11
cf: v4.5.0
cf-mysql: 36.15.0```

1) It looks like the API endpoint has changed from the script value of `https://api.local.pcfdev.io` to `https://api.dev.cfdev.sh`. This could be a simple update to check for both in the dependencies script. I wanted to call it out though.

2) I ran into an issue where `http://host.pcfdev.io` no longer points correctly to the host machine (where Conjur is running). I did find this issue (https://github.com/cloudfoundry-incubator/cfdev/issues/36) where others had encountered something similar, but this problems seems to be re-introduced with the latest PCF dev version (0.0.11). Switching to the IP address works for me, as the last comment on that issue mentions, but that isn't really a sustainable or portable solution.

3) The demo is using an old version of Conjur Open Source (`0.3.0`). Bumping to `1.0` doesn't work out of the box for me, but I don't know if any of you have already tried and resolved this locally. It's also not clear to me if we should consider switching the demo (or adding an option) to use V5 EE instead of Open Source.