Dev-to-Stage: Add ECR Repository for marimo-launcher#65
Merged
cabutlermit merged 2 commits intostagefrom Aug 15, 2025
Merged
Conversation
Why these changes are being introduced: Routine maintenance before updating infrastructure. How this addresses that need: * Update third-party dependencies in pre-commit configuration * Update AWS Provider to 5.100 Side effects of this change: None.
Why these changes are being introduced: MVP for running marimo notebooks in AWS as on-demand Fargate tasks. This builds the necessary infrastructure for storing the container image. How this addresses that need: * Create the ECR repository and associated resources Side effects of this change: None. Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/IN-1416
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Developer Checklist
What does this PR do?
pre-commitand AWS Provider)Helpful background context
Graham and Christopher are working on an MVP for running marimo notebooks in AWS with on-demand "run" access for stakeholders (especially for marimo notebooks that need to access data stored in AWS).
What are the relevant tickets?
Requires Database Migrations?
NO
Includes new or updated dependencies?
NO