fix: Fix dependencies and implementation of the logging configuration support feature

[schniber]

Description

This PR addresses the following:
#7 : using the locals to reference the workspace id has as a consequence that terraform does not know the interdependencies between the workspace, the alert manager config and the rule namespace group.
#8 : this feature will allow to add the support of cloudwatch logging to the prometheus workspace.

Motivation and Context

This PR fixes the example and adds the support for the prometheus worksapce logging configuration.

see issues fixed above.

Breaking Changes

No

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[schniber]

Hello @bryantbiggs,

This PR is ready. Thanks in advance for your feedback.

Bests.

[bryantbiggs]

this should be:

dynamic "logging_configuration" {
    for_each = length(var.logging_configuration) > 0 ? [var.logging_configuration] : []

    content {
      log_group_arn = logging_configuration.value.log_group_arn
    }
  }

and the variables will need to be updated to match

[schniber]

Fixed in new commit.

Thanks a ton !

[bryantbiggs]

this can be fixed with:

locals {
  workspace_id = var.create && var.create_workspace ? aws_prometheus_workspace.this[0].id : var.workspace_id
}

[schniber]

Fixed in new commit.

Thanks a ton !

[bryantbiggs]

awesome, thanks for the PR!

[antonbabenko]

This PR is included in version 2.2.1 🎉

[schniber]

@bryantbiggs I think we need to adapt the example also.
since we now get an issue at the creation. we need to add ":*" for the logging configuration.

[bryantbiggs]

oy, thats rather odd - looks like we do https://github.com/hashicorp/terraform-provider-aws/blob/2d2308a4872843b878a292dd2c95730e16a7a2e6/internal/service/amp/workspace_test.go#L324

[schniber]

so when I added the ":*" the example is working back.
I think there's a bug with the v4.35.0 then.
what do you advise to do next ?
shall we fix the example ?

[bryantbiggs]

ya, we can just update the example to match what the provider tests show with the addition of the trailing :*

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.