update qdrant registry metadata #123
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please review this update to the registry.
The Qdrant connector is located here.
Open Questions:
I have pointed the package URI at the source code's .tar.gz file, which I performed a SHA256 hash on. Is this the correct thing to hash and point at?
Some of the environment variables declared in my
connector-metadata.yamlare optional. Is there a way to declare that to the CLI or will it ask for all of them?Have I correctly specified the "update" command in the connector-metadata and does it work? Will need to test this with the new beta CLI workflow.