-
Notifications
You must be signed in to change notification settings - Fork 552
feat: allow for using CRUSH_ prefixed env-vars without clobbering default env vars #391
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
Conversation
…obbering AWS env vars
All contributors have signed the CLA ✍️ ✅ |
I have read the Contributor License Agreement (CLA) and hereby sign the CLA. |
hey @kujtimiihoxha , I made the CRUSH_ prefix logic generic as discussed. |
@taigrr do you think its worth adding this in the docs? |
Yeah, should be added to docs, as you see fit |
I think we could do this in |
Could! This works for me if there's a better way please go for it |
hey @kujtimiihoxha any updates on the plans for this? Hoping to deploy next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
talked to @caarlos0 about the implications of doing this another way and I think for now this is OK
…ault env vars (charmbracelet#391) * feat: allow for using CRUSH_ prefixed env-vars for bedrock without clobbering AWS env vars * feat: make the CRUSH_ prefix generic
Describe your changes
Add ability to push/pop
CRUSH_
-prefixed env vars for anthropic/bedrock.CONTRIBUTING.md
Basically, when developing actively on AWS, we might want to use crush in our AWS environment using credentials that are not the same as the credentials that are used for the bedrock instance.
This PR adds a function that allows for Push/Pop of the relevant
AWS_*
env vars when running in bedrock mode