Centralizing Monorepo air configs

[jay-babu]

Is your feature request related to a problem? Please describe.
Is there any recommendations for using air with multiple different services in a monorepo? Currently, each service has its own air.toml configuration. It leads to a lot of refactoring when changing one thing even though it is not that often. There are only slight changes for each config but many things are the same but redefined many times.

Describe the solution you'd like
having one root config and doing something like this would suffice with the key being some name that is defined:
air service1
air service2

Describe alternatives you've considered

1. each service has its own config
2. building a air.toml generation script for each service

Additional context
Add any other context or screenshots about the feature request here.

[mehdignu]

This is an interesting feature, i would work on a PR if it's fine with you.

[xiantang]

@mehdignu #738 could u take a look this issue as well, we can find a common way to support both features

[mehdignu]

@xiantang thanks for the hint, they surely could be unified, i would suggest this structure

[services.auth]
  [services.auth.build]
    cmd = "..."
  [services.auth.log]
    time = true

# Mail Service
[services.mail]
  [services.mail.build]
    cmd = "..."
    bin = "..."
...

[groups]
  # core services 
  core = ["broker", "auth"]
  
  # backend services 
  infrastructure = ["listener", "logger", "mail"]
  
...
  
  # all services
  all = ["broker", "auth", "listener", "logger", "mail"]

[xiantang]

but for #738 we need to manage two processes at the sametime, it will be more complex..

[mehdignu]

what would you suggest? should i start simple by centralizing monorepo air configs first in a PR?

[xiantang]

Can we put this issue on hold for a while? I'm not very sure how many people have this requirement.

[xiantang]

If you want to implement this feature, it should be a large pull request with over 500 lines of code, so the merge will not be very quick.