Implement bundling for split up artifact files

[caubut-charter]

Problem description
We will be splitting out some files to make it easier to maintain but need to bundle the files into a final spec or spec(s).

Expected action
CI or git hook to do the bundling. Partial towards CI (or both) since a git hook can be disabled with --no-verify.

Additional context
Looking into splitting up the API to both reduce the number of 501s and to make it easier to maintain as the file is getting quite large.

[caubut-charter]

Done in https://github.com/camaraproject/NetworkAccessManagement/tree/85-alpha-release-candidate but CI needs to be worked.

[hdamker]

@clundie-CL @caubut-charter see my last comment on camaraproject/Commonalities#577: Validation and Release Automation is ready for refs and bundling. But the structure is different then in your structure as done in #115 does not reflect the implemented structure: the common files from Commonalities will land (automated) in code/common (so common parallel to API_definitions). I would recommend the same for modules (but that is not enforced, as the RA and Validation does not know about these files and directories as of now).

Important is that you don't copy the common files from Commonalities manually but you must leave that to the automation.

[clundie-CL]

@hdamker Thanks for the update, I'm jumping on preparing the NAM API for Sync Release and will be opting in to leveraging this additional automation.

Ok, sounds like some things have changed on this front. I need to remove the checked in copy of CAMARA_common.yaml from the repo since this will by automated, but I guess where does that leave local/development workspaces? It's on the onus of the developer to maintain their local-only copy of the relevant CAMARA_common.yaml (or other artifact) so that API can be bundled locally, but not to be checked in. So the idea is to have a .gitignored CAMARA_common.yaml in our local workspace?

I would recommend the same for modules (but that is not enforced, as the RA and Validation does not know about these files and directories as of now).

I don't follow. These are domain/API specific schemas, where else would they live except the repo?

[clundie-CL]

@hdamker Oh I see what you meant now. The common/ and modules/ moved up a layer under code/. I suppose it doesn't matter if we have CAMARA_common.yaml checked in then, the automation will just copy over it and then ensure validation is happy.

[hdamker]

@hdamker Oh I see what you meant now. The common/ and modules/ moved up a layer under code/. I suppose it doesn't matter if we have CAMARA_common.yaml checked in then, the automation will just copy over it and then ensure validation is happy.

@clundie-CL The automation will create a PR which you will merge into main. So the files are checked in. They just come together with a manifest.yaml which the validation uses to check that the files are the right ones and not changed.