Decision Module location metrics

[npalm]

We are exploring the options to add features related to Monitoring and Alerting to tthe module, see #2025 and project.

We are aming to provide an AWS native soltuion that will be a complete opt-in. At this moment we have not a clear picture how to complete feature in the end will look like. But most likely it will consist of one or muliple terraform modules. We also have seen the comlexity of the repository have grown over the time. This raises the question should we start form a new repository of include the features in this repository.

Pro's mono repo:

• One single release, no extra work for maintainers and users to ensure the right version of releases are mathcing.
• Most likely several parts of metrics are in close connected to logic available in the current module.

Con's mono repo:

• Metrics will be an optional feature, with a single repository change in metrics create a runner release as well. Breaking cahnges in one of both modules will impact release strategy on both.
• Complexity of repo
• From a metrics module point of view, it is always connected to the runners module. Does not make sense to have it seprate.

[Brend-Smits]

My preference would be to keep it in this repository seeing as it has direct (perhaps on internal) dependencies on the runners module and our current core-maintainer team is already small enough. Spreading it across multiple repositories might just increase workflow unnecessarily due to maintaining releases and different repositories and communities.

[ScottGuymer]

I think we need to try and keep the module logically separate from each other so we dont have to deploy both at once. But I agree that it can live in this repo (at least until we find a reason for it not to)

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs. Thank you for your contributions.