Create OpenTelemetry Demo Light Branch #2195

[arorakanav]

Changes

Please provide a brief description of the changes here.

Merge Requirements

For new features contributions, please make sure you have completed the following
essential items:

• CHANGELOG.md updated to document new feature additions
• Appropriate documentation updates in the docs
• Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: julianocosta89 / name: Juliano Costa (ffb198f)

[julianocosta89]

Hello @arorakanav 👋🏽

Have you seen that we already have a docker-compose.minimal.yml file?

The idea of creating a light version for the demo is about making it easier to configure more or less services that should run.
Ideally in a programmatic way.

I've done some tests using docker profiles at https://github.com/julianocosta89/opentelemetry-demo/blob/docker-add-profiles-to-compose/compose.yaml, but this initial PR was just to test how it would work, without changing anything on the current full/minimal experience.

[arorakanav]

@julianocosta89 i have gone through the minimal file and your PR and comments on the issue to use profiles. with all the knowledge i have been able to gather using profiles will still run dependent services. now while writing this is i think i can remove more dependencies from my file which can give us a light version. i also understand that the requirement to have less code to manage, i will do some more research and see if i can find a more programmable way to solve this issue.

[julianocosta89]

@julianocosta89 i have gone through the minimal file and your PR and comments on the issue to use profiles. with all the knowledge i have been able to gather using profiles will still run dependent services. now while writing this is i think i can remove more dependencies from my file which can give us a light version. i also understand that the requirement to have less code to manage, i will do some more research and see if i can find a more programmable way to solve this issue.

@arorakanav I wonder how different this approach is from the docker-compose.minimal.yml approach?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.

[arorakanav]

@julianocosta89 my idea with this implementation is to further reduce the use of dependent services, and this could replace the minimal configuration. i choose to create a new file just to preserve the integrity of the minimal file.

[arorakanav]

coul not find a programtic way to solve this problem.