fix(gcloud): deploy fn needs more deps for poetry - Githubissues

talkiq / circleci-orbs

Various CircleCI orbs shared across TalkIQ projects

2 stars 4 forks source link

fix(gcloud): deploy fn needs more deps for poetry #101

Closed jonathan-johnston closed 1 year ago

jonathan-johnston commented 1 year ago

Summary

Our GCF deploy steps have been failing on Poetry installation which is due to Poetry requiring GCC and other headers (ex. Python dev headers).

Checklist

[x] My comments/docstrings/type hints are clear
[x] I've written new tests or this change does not need them
[x] I've tested this manually
[x] The architecture diagrams have been updated, if need be
[x] I've included any special rollback strategies above
[x] Any relevant metrics/monitors/SLOs have been added or modified
[x] I've notified all relevant stakeholders of the change
[x] I've updated .github/CODEOWNERS, if relevant

jonathan-johnston commented 1 year ago

@TheKevJames One day we will deprecate the use of GCFs in our systems and we won't have to worry about this any longer. 😛 The problems that this job has is at least partially attributable to the way that GCF fundamentally works (file structure, requirements.txt, uploading source, etc.) that doesn't hold true for containerized platforms (all these details exist within the Dockerfile instead and CI can be blissfully unaware of said details).