Add acceptance test for file based service bindings on Windows #1437
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 is this change about?
Added an acceptance test for validating file based service bindings on windows diego cells. The test will run if include_windows is enabled. I decided to re-use the catnip application for this test, since it is already adapted for such a test. That's why we build an catnip.exe. The test itself is the same as: https://github.com/cloudfoundry/cf-acceptance-tests/blob/main/file_based_service_bindings/file_based_service_bindings.go just tweaked a bit.
Please provide contextual information.
Follow up to cloudfoundry/community#901 and #1374.
What version of cf-deployment have you run this cf-acceptance-test change against?
v46.5.0 with modified capi and diego releases
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?
CATs should validate common operator workflows.
CATs is not a regression test suite.
CATs is run by every component team to validate their releases before promotion.
How many more (or fewer) seconds of runtime will this change introduce to CATs?
~ 1 minute for the whole test
What is the level of urgency for publishing this change?