Skip to content

Conversation

@cabutlermit
Copy link
Contributor

@cabutlermit cabutlermit commented Aug 9, 2024

How this addresses that need:

  • Update the Makefile with the output from mitlib-tf-workloads-ecr
  • Create a new dev-build.yml GitHub Actions workflow using the output from mitlib-tf-workloads-ecr

Side effects of this change:
None.

Relevant ticket(s):

Purpose and background context

After some initial testing by the developer, we are moving the control of the ECR Repository for this function into the hands of Infra through the mitlib-tf-workloads-ecr repository. That repository generates the correct Makefile commands for the developer to push containers to the managed ECR Repository and update the associated Lambda function.

How can a reviewer manually see the effects of these changes?

The developer can use the make commands (make dist-dev & make publish-dev) in the updated Makefile to verify that it is possible to push a container image to the new ECR Repository. The Lambda commands will not work yet since Infra has not yet deployed the Lambda infrastructure.

Includes new or updated dependencies?

NO

Changes expectations for external applications?

NO

What are the relevant tickets?

Developer

  • [n/a] All new ENV is documented in README
  • [n/a] All new ENV has been added to staging and production environments
  • All related Jira tickets are linked in commit message(s)
  • [n/a] Stakeholder approval has been confirmed (or is not needed)

Code Reviewer(s)

  • The commit message is clear and follows our guidelines (not just this PR message)
  • There are appropriate tests covering any new functionality
  • The provided documentation is sufficient for understanding any new functionality introduced
  • Any manual tests have been performed and verified
  • New dependencies are appropriate or there were no changes

Why these changes are being introduced:
After some initial testing by the developer, we are moving the control
of the ECR Repository for this function into the hands of Infra through
the mitlib-tf-workloads-ecr repository. That repository generates the
correct Makefile commands for the developer to push containers to the
managed ECR Repository and update the associated Lambda function.

How this addresses that need:
* Update the Makefile with the output from mitlib-tf-workloads-ecr
* Create a new dev-build.yml GitHub Actions workflow using the output
from mitlib-tf-workloads-ecr

Side effects of this change:
None.

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/IN-1011
@cabutlermit
Copy link
Contributor Author

@jonavellecuerdo
FWIW, the error in the "dev container build and deploy" Action was expected (since the Lambda infrastructure had not yet been deployed).

@jonavellecuerdo jonavellecuerdo merged commit 8cb1d6a into main Aug 16, 2024
@cabutlermit cabutlermit deleted the terraform-updates branch August 19, 2024 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants