Feature/light compose profile

[DavidEdell]

This would require the addition of "--profile full" to the compose up commands in non-light deployment instructions and tests.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[BrianSipos]

I was under the impression that the profile stuff was absent from podman, but if it's usable in our RHEL-9 version than this is a good cleanup.

[BrianSipos]

To switch to profiles, if the production deployment needs a specific name it will need to be part of the deployed environment file in puppet/modules/anms/templates/podman-compose-project.env.epp. After some digging it seems that the env option is COMPOSE_PROFILES with a comma-separated list.

[DavidEdell]

It looks like profile support was added last year for podman-compose 1.1.0.

[BrianSipos]

I would also like to get #231 and #234 merged to avoid some other duplication or excess build time.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[DavidEdell]

I updated the README. Do we need to make any related updates in anms-docs, or is that all handled via puppet in those directions? We might want to add some common language to both referring users to the README for development/non-puppet instructions and the product guide for production usage via puppet.