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

Vector DB Support: download automatically the AstraDB secure bundle #377

Merged
merged 2 commits into from
Sep 8, 2023

Conversation

eolivelli
Copy link
Member

@eolivelli eolivelli commented Sep 7, 2023

Summary:

  • now that we can use the Astra DevOps API it is easy to download the Secure bundle automatically
  • the user must provide the "token" and the "database" in the DataSource configuration
  • this works for the query-vector-db, vector-db-sink and the astra-keyspace and cassandra-table assets

configuration.yaml

configuration:
  resources:
    - type: "vector-database"
      name: "AstraDatasource"
      configuration:
        service: "astra"
        clientId: "{{{ secrets.astra.clientId }}}"
        secret: "{{{ secrets.astra.secret }}}"
        token: "{{{ secrets.astra.token }}}"
        database: "{{{ secrets.astra.database }}}"
        environment: "{{{ secrets.astra.environment }}}"

"environment" is by default PROD and it can be PROD, STAGING, DEV, this is a Datastax only thing, because we use the DEV databases.
I would keep it because all DataStax developers are using DEV databases and so it is easier for us to change the value to DEV in our secrets.yaml files and we can set PROD by default in the examples

@NadirJ
Copy link

NadirJ commented Sep 7, 2023

This is Awesome!

@eolivelli eolivelli merged commit 950df4a into main Sep 8, 2023
@eolivelli eolivelli deleted the impl/astra-secure-bundle branch September 8, 2023 05:26
benfrank241 pushed a commit to vectorize-io/langstream that referenced this pull request May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants