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

making env vars equivalent to whylogs' #71

Merged
merged 5 commits into from
Dec 4, 2024

Conversation

murilommen
Copy link
Collaborator

whylabs-toolkit relied on a few env vars that conflicted with ones required by whylogs. This PR introduces the ability to use both, while adding a few "will be deprecated soon" warning logs in case the old ones are still being used.

The idea is that this will not break existing code, but also not hard-require different env vars than what is already set in whylogs. The changed env vars were:

ORG_ID -> WHYLABS_DEFAULT_ORG_ID
DATASET_ID -> WHYLABS_DEFAULT_DATASET_ID
WHYLABS_HOST -> WHYLABS_API_ENDPOINT
ANALYZER_ID -> WHYLABS_DEFAULT_ANALYZER_ID
MONITOR_ID -> WHYLABS_DEFAULT_MONITOR_ID

@murilommen murilommen self-assigned this Dec 3, 2024
@murilommen murilommen temporarily deployed to whylabs-toolkit-ci December 3, 2024 21:02 — with GitHub Actions Inactive
@murilommen murilommen merged commit a411c51 into mainline Dec 4, 2024
1 check passed
@murilommen murilommen deleted the dev/murilommen/make-env-vars-equivalent branch December 4, 2024 14:53
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