Skip to content

Conversation

@olehermanse
Copy link
Member

No description provided.

The rationale for this is that if there are validation errors,
there is a good chance something is wrong and the build will fail
when it gets to the hub. We want to do what we can to prevent
the hub from having a project it cannot build correctly.

Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
If we introduce stricter validation rules inside modules, I think it's
nice if cfbs update works so it can get the new valid version
and automatically make your cfbs.json valid.

Avoided the partial approach of trying to measure if your cfbs.json
is more valid than before, that can quickly get hairy.

Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
…tion

Example error message:

```
$ cfbs --non-interactive update promise-type-ansible@0.1.0
Error: Assertion failed - assert name == module["name"] (cfbs/validate.py:377)
This is an unexpected error indicating a bug, please create a ticket at:
https://northerntech.atlassian.net/
(Rerun with CFBACKTRACE=1 in front of your command to show the full backtrace)
```

Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
Signed-off-by: Ole Herman Schumacher Elgesem <ole.elgesem@northern.tech>
@olehermanse olehermanse marked this pull request as ready for review July 16, 2025 18:32
@olehermanse olehermanse merged commit 7dd79a8 into cfengine:master Jul 17, 2025
11 checks passed
@olehermanse olehermanse deleted the strict branch July 17, 2025 12:25
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