You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
→ helm gcs push staging-model-template-0-1-0.tgz bi-staging --force
→ helm repo up
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bi-staging" chart repository
Update Complete. ⎈Happy Helming!⎈
→ helm fetch bi-staging/staging-model-template-0-1-0
Error: chart "staging-model-template-0-1-0" matching not found in bi-staging index. (try 'helm repo update'): no chart name found
→ helm gcs push staging-model-template-0-1-0.tgz bi-staging
Error: chart staging-model-template-0-1-0 already indexed. Use --force to still upload the chart
→ helm search repo bi-staging
No results found
See - it is indexed when you try to push, but it is not when you try to fetch/update/search.
When viewing the GCS bucket, the .tgz is there, along with an index.yaml as follows:
Note: Just for privacy on a public post, I removed the digest variable and changed the bucket name to gs://HIDDEN. The information is correct on the real bucket
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Example:
See - it is indexed when you try to push, but it is not when you try to fetch/update/search.
When viewing the GCS bucket, the
.tgz
is there, along with anindex.yaml
as follows:Note: Just for privacy on a public post, I removed the
digest
variable and changed the bucket name togs://HIDDEN
. The information is correct on the real bucketIs this a caching issue related to #44 ? What is happening to cause this? How would it be resolved?
The text was updated successfully, but these errors were encountered: