Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

About ENV_VARS #68

Closed
cafkafk opened this issue Jul 29, 2023 · 2 comments
Closed

About ENV_VARS #68

cafkafk opened this issue Jul 29, 2023 · 2 comments

Comments

@cafkafk
Copy link
Member

cafkafk commented Jul 29, 2023

Currently, the environment variables retain their old name, EXA_.

If no one sees an issue with this, I'll change it to EZA_ in the foreseable future. Zetta wil probably remain backwards compatible.

@cafkafk cafkafk pinned this issue Jul 29, 2023
@sbatial
Copy link
Collaborator

sbatial commented Jul 29, 2023

Voting to keep both (at least for some time), if it isn't a MAJOR pain.
Just because it would be an annoying break imo

@cafkafk
Copy link
Member Author

cafkafk commented Jul 29, 2023

Voting to keep both (at least for some time), if it isn't a MAJOR pain. Just because it would be an annoying break imo

It really isn't any major pain to me, I don't use them ¯_(ツ)_/¯

Keeping both seem like a fine enough solution for now.

@cafkafk cafkafk added help wanted Extra attention is needed good first issue Good for newcomers community › discussion and removed help wanted Extra attention is needed good first issue Good for newcomers labels Jul 30, 2023
@eza-community eza-community locked and limited conversation to collaborators Aug 4, 2023
@cafkafk cafkafk converted this issue into discussion #110 Aug 4, 2023
@cafkafk cafkafk unpinned this issue Aug 4, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

2 participants