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.

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

Support for private Hex packages #23

Open
cdcme opened this issue Apr 6, 2019 · 0 comments
Open

Support for private Hex packages #23

cdcme opened this issue Apr 6, 2019 · 0 comments

Comments

@cdcme
Copy link

cdcme commented Apr 6, 2019

If a private hex package is being used (documented here https://hex.pm/docs/private), the deployment currently fails. Seems like there needs to be a way to pass in a hash and then call mix hex.organization auth acme --key THE_HASH if a key is specified somewhere, maybe in the app.yaml file?

Step #1: Failed to fetch record for 'hexpm:foo/foo' from registry (using cache instead)
Step #1: This could be because the package does not exist, it was spelled incorrectly or you don't have permissions to it
Step #1: ** (Mix) Unknown package foo in lockfile
Step #1: The command '/bin/sh -c mix do deps.get, deps.compile, compile' returned a non-zero code: 1
Finished Step #1
ERROR
ERROR: build step 1 "gcr.io/cloud-builders/docker:latest" failed: exit status 1
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

No branches or pull requests

1 participant