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

feat: Use separate Literal project for API #166

Merged
merged 1 commit into from
Dec 31, 2024
Merged

Conversation

KevinJBoyer
Copy link
Contributor

Ticket

https://navalabs.atlassian.net/browse/DST-666

Changes

  • Set up new project in Literal
  • Add new secret to AWS Parameter Store, LITERAL_API_KEY_FOR_API
  • If this env variable is set, use it for the Literal client used by the API

Context for reviewers

  • This better isolates usage of the API in preparation for a pilot

Testing

Setting the variable locally, a query via the API appears in the Literal dashboard:
Screenshot 2024-12-31 at 11 43 12 AM
Screenshot 2024-12-31 at 11 43 21 AM

Here is the variable set in the AWS parameter store:
Screenshot 2024-12-31 at 11 43 32 AM

@KevinJBoyer KevinJBoyer requested a review from a team December 31, 2024 16:46
Copy link

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
2820 2518 89% 80% 🟢

New Files

No new covered files...

Modified Files

File Coverage Status
app/src/app_config.py 95% 🟢
app/src/chat_api.py 96% 🟢
TOTAL 95% 🟢

updated for commit: 013c12d by action🐍

@KevinJBoyer KevinJBoyer merged commit 49771a7 into main Dec 31, 2024
10 checks passed
@KevinJBoyer KevinJBoyer deleted the kb/literal-for-api branch December 31, 2024 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants