Sync common files from Commonalities r4.2

[camara-release-automation]

Automated sync of code/common/ files from camaraproject/Commonalities at release tag r4.2.

This PR was created by release automation because the cached Commonalities files were out of sync with the declared dependency in release-plan.yaml.

What changed:

• Updated files in code/common/ to match Commonalities r4.2
• Added/updated .sync-manifest.yaml with file integrity hashes

Action required: Review and merge this PR. The /create-snapshot command will be blocked until common files are in sync.

[camara-validation]

CAMARA Validation — PASS

0 errors, 24 warnings, 23 hints | Profile: standard

View full results

[hdamker]

@camaraproject/edge-application-management_codeowners I recommend to merge this PR despite the errors and warnings and then start a new PR (E.g. "Align with Commonalities r4.2"):

• to fix the one error: adding the line x-camara-commonalities: 0.8.0 (the concrete number will be written in the release process)
• replace definitions copied from CAMARA_common.yaml with references, see examples in https://github.com/camaraproject/Commonalities/blob/main/artifacts/api-templates/sample-service.yaml
• address the remaining obvious warnings and hints

See also CAMARA Validation documentation

[JoseMConde]

Hi @hdamker , thanks for the suggestion!
Can we merge even with the errors??

[hdamker]

Hi @hdamker , thanks for the suggestion!
Can we merge even with the errors??

You could, but you shouldn't :-)

I've corrected the one error with da71229 and with that also one of the warnings (there should be no contact field).

Now you can merge and address the warnings in another PR.

[JoseMConde]

We will manage the different warnings in a specific PR.
Thanks a lot @hdamker !!