Error: ensuring plugins index failed - cli migrations
See original GitHub issueWe use a self hosted kubernetes cluster and our services are not allowed to connect to public services eg. github.
It seems that the cli-migrations tool try to download several plugins for the execution.
time="2020-04-21T12:21:10Z" level=fatal msg="ensuring plugins index failed: Get https://github.com/hasura/cli-plugins-index.git/info/refs?service=git-upload-pack: dial tcp 140.82.118.3:443: i/o timeout"
How can I prevent that hasura download things and is still able to execute the migrations? All necessary plugins should be bundled in the cli-migration docker image
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Resolve migration failures | Kibana Guide [master] - Elastic
Migrations will fail if saved objects belong to an unknown saved object type. Unknown saved objects are typically caused by performing manual modifications...
Read more >hasura migrate apply | Hasura GraphQL Docs - Hasura CLI
Apply migrations on the database using the Hasura CLI.
Read more >To v5 from v4 - webpack
This guide aims to help you migrating to webpack 5 when using webpack directly. If you are using a higher level tool to...
Read more >Flyway by Redgate • Database Migrations Made Easy.
This does not help with failed versioned migrations on databases without DDL ... It is your responsibility to ensure the same repeatable migration...
Read more >AWS DMS release notes - AWS Database Migration Service
Fixed an issue where database migration tasks fail with error Could not find relation id … when using PostgreSQL as a source, with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I found solution in your Dockerfile. Append this variables helped. Can you document it somewhere? Or I just did not find it in doc?
@tirumaraiselvan can I get some clarity on this
HASURA_GRAPHQL_SHOW_UPDATE_NOTIFICATION
environment variable? I asked for something similar but my issue is still open. Googling forHASURA_GRAPHQL_SHOW_UPDATE_NOTIFICATION
brings up exactly two results, this issue and a broken dockerhub link, which suggests this did exist at some point. I can’t find anything in your code about it though.