Adds a preliminary docker-compose support for cloud-harness.
Implemented solution:
The implementation relies on helm templates dedicated for docker-compose.
A new folder can be defined and used for all docker-compose related templates, while a mechanism allows one to define where some files can be generated.
On a general note, all files that needs to be generated from templates and needs to be embedded in containers needs to be generated in a specific directory in the file system.
The generated files are then mounted in the countainer.
How to test this PR:
There is a new option --docker-compose that can be passed as argument of the command line for the harness-deployment command.
This new option will generate in deployment/compose all the templates and specific files for the cloudharness deployment, a deployment/docker-compose.yaml will be produced, and the skaffold.yaml file is modified to target docker-compose for deployment (even if this feature is still not yet supported).
Sanity checks:
[X] The pull request is explicitly linked to the relevant issue(s)
[ X The issue is well described: clearly states the problem and the general proposed solution(s)
[X] From the issue and the current PR it is explicitly stated how to test the current change
[X] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
[X] All the automated test checks are passing
[ ] All the linked issues are included in one milestone
[ ] All the linked issues are in the Review/QA column of the board
[X] All the linked issues are assigned
Breaking changes (select one):
[X] The present changes do not change the preexisting api in any way
[ ] This PR and the issue are tagged as a breaking-change
Possible deployment updates issues (select one):
[X] There is no reason why deployments based on CloudHarness may break after the current update
[ ] This PR and the issue are tagged as alert:deployment
Test coverage (select one):
[ ] Tests for the relevant cases are included in this pr
[ ] The changes included in this pr are out of the current test coverage scope
Documentation (select one):
[ ] The documentation has been updated to match the current changes
[ ] The changes included in this PR are out of the current documentation scope
Closes CH-100
Adds a preliminary docker-compose support for cloud-harness.
Implemented solution: The implementation relies on helm templates dedicated for docker-compose. A new folder can be defined and used for all docker-compose related templates, while a mechanism allows one to define where some files can be generated. On a general note, all files that needs to be generated from templates and needs to be embedded in containers needs to be generated in a specific directory in the file system. The generated files are then mounted in the countainer.
How to test this PR: There is a new option
--docker-composethat can be passed as argument of the command line for theharness-deploymentcommand. This new option will generate indeployment/composeall the templates and specific files for the cloudharness deployment, adeployment/docker-compose.yamlwill be produced, and theskaffold.yamlfile is modified to target docker-compose for deployment (even if this feature is still not yet supported).Sanity checks:
Breaking changes (select one):
breaking-changePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):
Nice to have (if relevant):