Missing context for the status service fails deploy to dev #742
Comments
placek
added a commit
that referenced
this issue
Apr 22, 2024
The user story described a situation where the deployment to the Dev environment was failing due to missing context for the status-service. The expected behavior was for the deploy to succeed. In response, a status-service AWS registry was created to address this missing context, ensuring that the deploy to Dev can now successfully utilize the status-service.
placek
added a commit
that referenced
this issue
Apr 22, 2024
The user story indicated that the deployment to the dev environment was failing due to a missing context for the status-service. To address this issue and enable a successful deployment, a status-service AWS registry was created. However, to further enhance the deployment process, a metadata-validation registry has been implemented. This addition ensures that the necessary context is available for the deployment, optimizing the functionality and reliability of the Dev environment.
placek
added a commit
that referenced
this issue
Apr 22, 2024
The user story highlighted the issue of a failed deployment to the dev environment due to a missing context for the status-service. The expected behavior was for the deploy to succeed. To address this, changes were made to incorporate the status-service docker image utilization into the deploy stack. The addition of the status-service AWS registry now ensures that the necessary context is available for the deployment process, moving the build process to the machine where the deploy is performed, allowing for a successful deployment to the dev environment.
placek
added a commit
that referenced
this issue
Apr 22, 2024
… stack The user story highlighted the issue of a failed deployment to the dev environment due to a missing context for the status-service. The expected behavior was for the deploy to succeed. In response to this, changes have been made to integrate the metadata-validation docker image into the deploy stack. By creating the necessary context for the metadata-validation registry, the deployment process can now utilize this image efficiently. The modifications include new files like `Makefile` in `govtool/metadata-validation`, adjustments in `scripts/govtool/Makefile` to incorporate the metadata-validation registry, and changes in `docker-compose.yml.tpl` and `info.mk` to include metadata-validation details for enhanced deployment functionality.
placek
added a commit
that referenced
this issue
Apr 22, 2024
The user story highlighted the issue of a failed deployment to the dev environment due to a missing context for the status-service. The expected behavior was for the deploy to succeed. To address this, changes were made to incorporate the status-service docker image utilization into the deploy stack. The addition of the status-service AWS registry now ensures that the necessary context is available for the deployment process, moving the build process to the machine where the deploy is performed, allowing for a successful deployment to the dev environment.
placek
added a commit
that referenced
this issue
Apr 22, 2024
… stack The user story highlighted the issue of a failed deployment to the dev environment due to a missing context for the status-service. The expected behavior was for the deploy to succeed. In response to this, changes have been made to integrate the metadata-validation docker image into the deploy stack. By creating the necessary context for the metadata-validation registry, the deployment process can now utilize this image efficiently. The modifications include new files like `Makefile` in `govtool/metadata-validation`, adjustments in `scripts/govtool/Makefile` to incorporate the metadata-validation registry, and changes in `docker-compose.yml.tpl` and `info.mk` to include metadata-validation details for enhanced deployment functionality.
placek
added a commit
that referenced
this issue
Apr 22, 2024
…-the-status-service-fails-deploy-to-dev [#742] Missing context for the status service fails deploy to dev
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context & versions
Steps to reproduce
Actual behavior
Deploy fails due to missing status-service context:
unable to prepare context: path "/home/runner/work/govtool/govtool/scripts/govtool/govtool/status-service" not foundExpected behavior
Deploy succeeds.
The text was updated successfully, but these errors were encountered: