Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[#742] Missing context for the status service fails deploy to dev #819

Merged
merged 4 commits into from
Apr 22, 2024
Merged

[#742] Missing context for the status service fails deploy to dev #819

merged 4 commits into from
Apr 22, 2024

Commits on Apr 22, 2024

  1. [#742] Create a status-service AWS registry 

    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
    placek committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    e203a74 View commit details
    Browse the repository at this point in the history

  2. [#742] Create a metadata-validation AWS registry 

    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
    placek committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    9aa6ab9 View commit details
    Browse the repository at this point in the history

  3. [#742] Add status service docker image utilization to the deploy 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. 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
    placek committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    fd3df1b View commit details
    Browse the repository at this point in the history

  4. [#742] Add metadata-validation docker image utilization to the deploy… 

    … 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
    placek committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    553fa0e View commit details
    Browse the repository at this point in the history