Move canarie-api configuration for cowbird from proxy to canarie-api config directory#338
Conversation
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1605/Result : failure BIRDHOUSE_DEPLOY_BRANCH : move-canarie-api-template-in-cowbird DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https:// Infrastructure deployment failed. Instance has not been destroyed. @matprov |
fmigneault
left a comment
There was a problem hiding this comment.
The PR is ok, but I suggest we wait until Ouranosinc/CanarieAPI#18 is completed and tagged 1.0.0 to make the version change of the Docker image at the same time.
| of when the canarie-api component was enabled. Since these components can now be enabled separately, the | ||
| configuration has to be moved to ensure that canarie-api configuration files aren't unintentionally mounted | ||
| to a container that is just running an nginx proxy. |
There was a problem hiding this comment.
Add a reference to Ouranosinc/CanarieAPI#18 + mention of requirement CanarieAPI>=1.0.0 to accomplish this.
There was a problem hiding this comment.
Ok if you want. But this PR has nothing to do with that change. It moves a file that I should have moved in #296 and has been raising warning messages ever since nginx can be run without canarie-api in #310.
My vote would be to merge this now since it is entirely independent of Ouranosinc/CanarieAPI#18
There was a problem hiding this comment.
Oh. By "Since these components can now be enabled separately", it thought you were refering to the nginx proxy and canarie-api being enabled separately. If you were refering to the service components of birdhouse-deploy, then you can ignore this comment.
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1633/Result : failure BIRDHOUSE_DEPLOY_BRANCH : move-canarie-api-template-in-cowbird DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-88.rdext.crim.ca Infrastructure deployment failed. Instance has not been destroyed. @matprov |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1632/Result : failure BIRDHOUSE_DEPLOY_BRANCH : move-canarie-api-template-in-cowbird DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-88.rdext.crim.ca Infrastructure deployment failed. Instance has not been destroyed. @matprov |
|
run tests |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1638/Result : failure BIRDHOUSE_DEPLOY_BRANCH : move-canarie-api-template-in-cowbird DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-20.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1179/NOTEBOOK TEST RESULTS |
|
@tlvu can I merge this one? |
Overview
The canarie-api configuration for cowbird was being loaded whenever the proxy component was enabled instead of when the canarie-api component was enabled. Since these components can now be enabled separately, the configuration has to be moved to ensure that canarie-api configuration files aren't unintentionally mounted to a container that is just running an nginx proxy.
Changes
Non-breaking changes
None
Breaking changes
None
Related Issue / Discussion
Additional Information
Links to other issues or sources.