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

requirements.yaml can not reference s3 repo by name #85

Open
drewwells opened this issue Sep 23, 2019 · 0 comments
Open

requirements.yaml can not reference s3 repo by name #85

drewwells opened this issue Sep 23, 2019 · 0 comments
Labels
needs-investigation Requires digging/reproducing, or not obvious how to solve the issue

Comments

@drewwells
Copy link

drewwells commented Sep 23, 2019

I get this error whenever attempting to use an s3 repo inside requirements.yaml

-> % helm dep update
Error: no repository definition for mys3repo. Please add them via 'helm repo add'
Note that repositories must be URLs or aliases. For example, to refer to the stable
repository, use "https://kubernetes-charts.storage.googleapis.com/" or "@stable" instead of
"stable". Don't forget to add the repo, too ('helm repo add').

It does work with full s3 path ie. s3://mys3repo

  - name: somechart
    version: 0.1.0
    repository: "s3://mys3repo/charts"
    condition: somechart.enabled
@hypnoglow hypnoglow added the needs-investigation Requires digging/reproducing, or not obvious how to solve the issue label Nov 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Requires digging/reproducing, or not obvious how to solve the issue
Projects
None yet
Development

No branches or pull requests

2 participants