CLOSED - Source the X509_CA_ENV_FILE in trafficops #3523
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR (Pull Request) do?
When I start up my TO container with trafficvault, the ssl keys aren't added correctly because the environment variables aren't sourced. Every other run file sources the env variables correctly, so I'm using them as a reference.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
rm -rf trafficops/ca
Make sure volumes are removed by checking
docker volume ls
docker-compose build trafficops
variables.env:96: AUTO_SNAPQUEUE_ENABLED=false
docker-compose up -d trafficops trafficvault
docker-compose logs -f trafficops
The trafficops logs should output
exec tail -f /dev/null
and stop. If the logs loop forever it didn't start up correctly.I am running a limited stack, but running the whole stack should also work the same.
If this is a bug fix, what versions of Traffic Ops are affected?
The following criteria are ALL met by this PR