8000 wurzel generate: check env · Issue #39 · telekom/wurzel · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

wurzel generate: check env #39

New issue
8000

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

Closed
3 tasks done
merren-fx opened this issue Apr 17, 2025 · 1 comment
Closed
3 tasks done

wurzel generate: check env #39

merren-fx opened this issue Apr 17, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@merren-fx
Copy link
Collaborator

Initial Checks

  • I have searched GitHub for a duplicate issue and I'm sure this is something new
  • I have searched Google & StackOverflow for a solution and couldn't find anything
  • I have read and followed the documentation and still think this is a bug

Description

wurzel generate should, by default, check the environment to see if all the necesseary env vars for each required step is present.

This is no longer the case and needs to be adressed.

Example Code

wurzel generate test:pipeline

Version & Environment

LATEST

@merren-fx merren-fx added the bug Something isn't working label Apr 17, 2025
tweigel-dev added a commit that referenced this issue Apr 17, 2025
tweigel-dev added a commit that referenced this issue Apr 17, 2025
* adapt wurzel for Dockerfile

* validate env settings #39

* group deployment deps together as wurzel[all]
---------
merren-fx pushed a commit that referenced this issue May 8, 2025
* adapt wurzel for Dockerfile


Automatically generated by python-semantic-release

* fix asserts

* create dvc folder if not exist

* validate env settings #39

* drop test wurzel install in dockerfile

* group deployment deps together as wurzel[all]

* add exit 1

* wurzel lint

* install jq static

* remove obsolete activate

---------

Co-authored-by: github-actions <actions@users.noreply.github.com>
@sam-hey
Copy link
Collaborator
sam-hey commented May 16, 2025

Did #36 close this issue? @merren-fx @tweigel-dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants
0