oscerd commented on issue #2260:
URL:
https://github.com/apache/camel-kamelets/issues/2260#issuecomment-5448599675
Checked this against current `main` — **it is already resolved**, and can be
closed.
## What happened
`77be42a85` ("Remove Camel-Kamelets-utils since it is now in core") replaced
the dependency line rather than deleting it, leaving a bare list dash that YAML
parses as a null entry:
```diff
dependencies:
- - mvn:org.apache.camel.kamelets:camel-kamelets-utils:4.9.0-SNAPSHOT
+ -
- "camel:core"
```
That is exactly the concern raised here — a null element in
`spec.dependencies` that downstream tooling would have to tolerate.
## It was cleaned up the same day
`acc79e19e`, on 2024-10-11, removed the leftover dashes:
```
acc79e19e Remove Camel-Kamelets-utils since it is now in core
kamelets/aws-ddb-sink.kamelet.yaml | 1 -
1 file changed, 1 deletion(-)
- -
```
## Verified across the whole catalog
Rather than spot-checking, I parsed every Kamelet and inspected
`spec.dependencies` for null or blank entries:
```
kamelets scanned: 250
problems: 0
```
No null entries, no blank strings, and no Kamelet missing the `dependencies`
key entirely. Whatever tooling breakage this would have caused is no longer
reachable from the catalog as it stands.
Closing as already fixed — please reopen if you are seeing an empty element
somewhere I have not looked, for instance in a released artifact rather than
`main`.
---
_Claude Code on behalf of Andrea Cosentino_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
