Run DB script before starting other containers 17/89417/1
authorJim Hahn <jrh3@att.com>
Mon, 3 Jun 2019 19:00:08 +0000 (15:00 -0400)
committerBilal A <bilal@research.att.com>
Wed, 5 Jun 2019 17:37:47 +0000 (17:37 +0000)
commite57042c32af6b290186f8f7dce25e5968056c8ff
tree79d3036e6aac2d518f1adca98143792f3eaa33b1
parent1e0b621a2449411fcd0e5f2cce247170b6d12bd7
Run DB script before starting other containers

The other containers were starting before their user names had
been added to the DB.  Consequently, they were aborting at start-up.
Modified the various setup.sh scripts to run the DB-init script
before starting the remaing containers.
Also add start_all to start the containers and wait for the ports
to start listening, eliminating the need for the "curl" tests in
the setup.sh scripts.
Also removed version numbers from some yml files.

Change-Id: Idd9ff81b3ab4a78926b644f22360c9222afe82d5
Issue-ID: POLICY-1829
Signed-off-by: Jim Hahn <jrh3@att.com>
plans/policy/apex-pdp/setup.sh
plans/policy/api/setup.sh
plans/policy/api/teardown.sh
plans/policy/pap/setup.sh
plans/policy/pap/teardown.sh
plans/policy/xacml-pdp/setup.sh
scripts/policy/docker-compose-api.yml
scripts/policy/docker-compose-pap.yml
scripts/policy/policy-apex-pdp/docker-compose-apex.yml
scripts/policy/policy-xacml-pdp/docker-compose-pdpx.yml