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

Adopt werf images #43

Open
yalosev opened this issue Dec 24, 2024 · 1 comment · May be fixed by #63
Open

Adopt werf images #43

yalosev opened this issue Dec 24, 2024 · 1 comment · May be fixed by #63
Assignees
@juev

Comments

@yalosev
Copy link
Member

yalosev commented Dec 24, 2024 •
edited
Loading

  1. Find main werf.yaml file (in the root of the repository)
  2. Use werf config render imported as lib from here to render
  3. Take all images from WerfConfig and scan their keys like from, artifact and so on
@juev juev self-assigned this Dec 24, 2024
@juev
Copy link
Member

juev commented Jan 10, 2025

If we have an external module that contains its own root werf.yaml file, this will make sense.

But if we run a check on the deckhouse repository, in which the root werf.yaml is located in the root of the repository, checking each module will lead to problems in all modules. How are you supposed to filter the results?

It is possible to change the root werf.yaml file to include only the werf.yaml of a specific module, but it seems that this may lead to errors.

@yalosev

This was referenced Jan 16, 2025
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juev juev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add werf parser deckhouse/dmt
Improve validate werf config deckhouse/dmt
2 participants
@juev @yalosev