Skip to content

Conversation

@olehermanse
Copy link
Member

  • Moved out build step validation function for reuse
  • Added replace build step
  • Moved code from build to validate to avoid circular imports
  • Added docstrings to build.py and validate.py

Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
I want to start using some validaiton code inside of build.py

This can be problematic due to circular imports (especially the
global constants). Thus, it makes more sense to put the common
code in validate, and say that build depends on validate, not
the other way around.

Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
@olehermanse olehermanse requested a review from larsewi July 3, 2025 13:43
Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
@olehermanse olehermanse requested a review from jakub-nt July 3, 2025 13:58
Copy link
Contributor

@larsewi larsewi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, some minor comments that you can feel free to dismiss

@olehermanse olehermanse merged commit faccb1c into cfengine:master Jul 3, 2025
11 checks passed
@olehermanse olehermanse deleted the replace_more branch July 3, 2025 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants