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.

Sign up for GitHub

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

Jump to bottom

PROJECT_ID should be exposed as an env value just like INFISICAL_TOKEN #2912

Open
adelowo opened this issue Dec 21, 2024 · 0 comments · May be fixed by #2959
Open

PROJECT_ID should be exposed as an env value just like INFISICAL_TOKEN #2912

adelowo opened this issue Dec 21, 2024 · 0 comments · May be fixed by #2959
Labels
good first issue Good for newcomers

Comments

@adelowo
Copy link
Contributor

adelowo commented Dec 21, 2024

Feature description

When using the cli, INFISICAL_TOKEN is available, this makes sense for automation,ci/cd pipelines but now there is also another projectId required in the cli options too

CleanShot 2024-12-21 at 23 14 38

Why would it be useful?

complete automation of CI/CD pipelines. I'd love to set up all envs and it just works rather than tons of cli flags and switches

Additional context
@akhilmhdh akhilmhdh added the good first issue Good for newcomers label Jan 7, 2025
@vincent0426 vincent0426 linked a pull request Jan 9, 2025 that will close this issue
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: allow users to expose project ID as env vincent0426/infisical
2 participants
@adelowo @akhilmhdh