docs: make astra vectorize provider key advanced param #2639
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.
Makes the astra vectorize provider key an advanced parameter, as the recommended workflow currently has users storing the key in Astra KMS.
This key would only be used when a user creates the collection via LC or the Data API directly, then uses Langflow with that collection. This is possible, and we're working on ways to simplify that transition, but for now, this is more understandable for users.