Skip to content

Dev-to-Stage: New ECRs and Maintenance#79

Merged
cabutlermit merged 3 commits intostagefrom
dev
Mar 5, 2026
Merged

Dev-to-Stage: New ECRs and Maintenance#79
cabutlermit merged 3 commits intostagefrom
dev

Conversation

@cabutlermit
Copy link
Contributor

@cabutlermit cabutlermit commented Mar 5, 2026

Developer Checklist

  • The README contains any additional info needed outside of the terraform docs generated
  • Any special variables have values configured in AWS SSM
  • Stakeholder approval has been confirmed (or is not needed)

What does this PR do?

  • Update to AWS Provider v6.x (and update the code to address issues that this raised)
  • Create an ECR Repository for the forked quepid app that DiscoEng is testing
  • Create and ECR Repository for the timdex-semantic-builder that DiscoEng will be using as part of the USE project
  • Reorganize up the DSC and DSS code into one DSO file to align with the overall DSO architecture

Helpful background context

This groups together some basic maintenance and two new ECRs for applications for DiscoEng that will run in AWS.

What are the relevant tickets?

Requires Database Migrations?

NO

Includes new or updated dependencies?

YES: Updated AWS Provider requirement from v5.x to v6.x

Why these changes are being introduced:
As we make changes to repositories we are trying to update to the
AWS Provider v6.x.

How this addresses that need:
* Update to AWS Provider 6.x in the root as well as in the embedded
module
* Update the data.aws_region.current output from .name to .region since
the .name output is now deprecated
* Run `terraform init -upgrade` to update the .terraform.lock.hcl file

Side effects of this change:
None.
This removes the separate dsc_ and dss_ files
and puts all the DSS & DSC code together under
one dso_ecrs.tf file. This aligns with how we have
the timdex related ECRs all in one timdex_ecrs.tf
file.
Quepid is an open-source tool that DiscoEng is currently testing in
Heroku. We are interested in running this application in AWS instead
of Heroku. We have a local fork of the opensource repository that we
will be using to build our custom version of quepid.

Timdex-semantic-builder is a new Lambda function that related to the
embeddings work for TIMDEX.

Related Jira tickets:
* https://mitlibraries.atlassian.net/browse/IN-1664
* https://mitlibraries.atlassian.net/browse/USE-428
@cabutlermit cabutlermit marked this pull request as ready for review March 5, 2026 21:16
@cabutlermit cabutlermit requested a review from a team as a code owner March 5, 2026 21:16
Copy link
Contributor

@tim-rix tim-rix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything looks OK to me

@cabutlermit cabutlermit merged commit f3efb04 into stage Mar 5, 2026
5 checks passed
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.

2 participants