Fixing staging deployment attempt 2 #433
Merged
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.
Fixes #430 ( hopefully )
Changes
poetry lock
instead ofpoetry lock --no-cache
to let poetry upgrade packages which will hopefully allow for the incompatible version issue involvingpyyaml
andcython
( see comment on poetry repo )pyyaml
to6.0.1
which the comment with multiple thumbs ups indicates will fix the incompatibilityDiscussion
poetry.lock
file determines which versions of packages end up being installed and made available to the docker container as theBuild, tag, and push image to Amazon ECR
job runspoetry.lock
file please voice your opinion. I lean towards its fine to letpoetry lock
command do its thing. I did run a fulldocker compose build --no-cache
and site still looks good on my local environmentDiscovery