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.
Are you submitting this PR against the develop branch?
YES
What is this change about?
Adds test for C2C over TLS, new feature available in diego-release v2.59.0
Please provide contextual information.
cloudfoundry/diego-release#587
What version of cf-deployment have you run this cf-acceptance-test change against?
cf-deployment did not pick up the latest diego-release yet. We have run it with latest cf-deployment and diego-release v2.59.0
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?
We want to make sure C2C is working not just over HTTP but HTTPS as well.
How should this change be described in cf-acceptance-tests release notes?
New test for container to container networking over TLS
How many more (or fewer) seconds of runtime will this change introduce to CATs?
56s
What is the level of urgency for publishing this change?
Tag your pair, your PM, and/or team!
@cloudfoundry/cf-diego