GONRG-10103: add global log level to services

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• NO

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• NO

What is the current behavior?

Logs are currently configured separately for each service in its configuration.

What is the new/expected behavior?

Logs will configure on global level with possible fine-grained service-level configuration that will override global (if data empty - log_level will take from .global ; otherwise from .data)

Have you added/updated Unit Tests and Integration Tests?

No

Any other useful information

added GC label

added 1 commit

• 4d0e05b5 - Updating NOTICE

Compare with previous version

added 1 commit

• 4a74e2bd - Updating NOTICE

Compare with previous version

added 3 commits

• 4a74e2bd...4fbadde8 - 2 commits from branch master
• 47db45b3 - Merge branch 'master' into 'loglevel'

Compare with previous version

marked this merge request as ready

added 1 commit

• cff07030 - globalloglevel

Compare with previous version

approved this merge request

merged

mentioned in commit 1402d687

changed milestone to %M25 - Release 0.28

Hi, this is a friendly reminder to assign appropriate labels and milestone to your future merge requests. Proper labeling and milestone assignment help us to track and prepare effectively for upcoming milestone releases.