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

EC2 Pipeline Services Fixes #478

Merged
merged 1 commit into from
Jun 20, 2023
Merged

EC2 Pipeline Services Fixes #478

merged 1 commit into from
Jun 20, 2023

Conversation

CoreyKrewson-NOAA
Copy link
Contributor

Had to fix a couple things that we causing the MRF EC2 pipeline services to fail with the new naming conventions

  1. The service name was too long and causing the lock file creation to fail. Instead of using the service name as a suffix, the code now just uses the initials of all the parts of the service name
  2. Updated the configuration name for the mrf services to be medium_range_mem1 so that it could find the appropriate mapx file in the publish service lambda

@CoreyKrewson-NOAA
fixed configuration name for mrf services
339ed14 
shortened service lock file name because it was too long before and failing
@CoreyKrewson-NOAA CoreyKrewson-NOAA added this to the V2.1.0 milestone Jun 20, 2023
@CoreyKrewson-NOAA CoreyKrewson-NOAA merged commit a5aa300 into ti Jun 20, 2023
@CoreyKrewson-NOAA CoreyKrewson-NOAA deleted the ec2_pipeline_service_fixes branch June 20, 2023 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TylerSchrag-NOAA TylerSchrag-NOAA TylerSchrag-NOAA approved these changes

@shawncrawley shawncrawley Awaiting requested review from shawncrawley

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
V2.1.0
Development

Successfully merging this pull request may close these issues.
2 participants
@CoreyKrewson-NOAA @TylerSchrag-NOAA