[tariromukute]

Summary

This pull request introduces support for building and deploying the project as a single bundled application (combining AF Core and the southbound PCF handler into one binary and container), while retaining support for the existing microservice deployment. It also improves build configuration, updates documentation for both modes, and refines configuration management and code structure for easier maintenance and deployment.

Changelog KeepA

[Added] :

• Added a new BUILD_BUNDLED CMake option and logic in CMakeLists.txt to build a single af executable that links AF Core and the PCF handler, with appropriate include directories and linker settings.
• Introduced a top-level Dockerfile to build and package the bundled application, including all dependencies and runtime configuration for containerized deployment.
• Added detailed build and deployment instructions to README.md, covering both microservice and bundled modes, prerequisites, Docker builds, and compose environments.
• Introduced a unified configuration file format (config/af.yaml) for the bundled mode, and restructured af_core/config/af_core.yaml to separate AF Core and PCF handler settings.

[Changed]:

• Refactored af_core/CMakeLists.txt to create a reusable af_core_lib static library, enabling both standalone and bundled builds, and updated include/link targets accordingly.
• Improved spdlog discovery in CMakeLists.txt to first attempt config-based detection for better compatibility.
• Updated af_orchestrator.h to use a typed configuration object and provide access to the configured PCF handler destination, improving maintainability and clarity.
• Updated adapter documentation to reference the correct Docker image repository.

Related Issues

Closing: #15

Checklist

• Code is tested and passes locally
• Documentation is updated if needed
• Follows code style and guidelines [Lint, Guidelines and co will follow if not existing]

[tariromukute]

Note: We need to merge the following first phinetech/phine.af-common#1

[phine-lukas]

No need to fix it within this PR, but I have seen now that we are still using "oai", for example in the log or config path int the containers.

[phine-lukas]

As already discussed:
While testing I was confused by the /northbound folder and it's role in the docker-compose files.
Our finding was that it is a leftover of the initial version where we did not have any example adapters. So we can either move it also to the adapters folder or remove it. I think it should also be removed from docker-compose files if it is not used by any tutorial or runme.

[phineSte]

@phine-lukas Tariro told me you already had a look and last 2 commits were only for house keeping so I approved pro-forma without checking the code

[phine-lukas]

LGTM!