Load env variables#1
Open
tech-team-rural-mda wants to merge 4 commits into
Open
Conversation
…into dev/load-env # Conflicts: # README.md # aws_bedrock/S10_load_data_s3.ipynb # aws_bedrock/S20_build_bedrock_knowledgebase.ipynb # aws_bedrock/S30_search_bedrock_knowledgebase.ipynb
This file contains hidden or 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
2 participants
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.
Hi @Numantic-SGodfrey ,
Here's a summary of the updates I have made to the scripts in the @
aws_bedrock/folder...Externalized all hardcoded configuration into the
.envfile — AWS credentials, S3 paths, Bedrock/OpenSearch settings, and local dataset file paths — so the notebooks can run against different environments (e.g., the CORI agent sandbox Knowledge Base) without code changes. Also added traceability columns to the documents data.frame and overwrite detection during S3 uploads (instead of deleting all the documents each time, which does not delete the vector embeddings -- that would require an explicit TRUNCATE).Overall intent: Make the project fully configuration-driven so it can target different AWS environments and datasets without code changes.