Add account metrics resource

[ennyjfrick]

What was changed

Hi again! This PR adds a new resource to configure account-level metrics. It allows enabling and disabling of an account's metrics endpoint, configuring the CA cert accepted by the metrics endpoint, and exporting the metrics endpoint URI once created.

Why?

The new resource is intended to enable a better experience for operators with certificate and observability infrastructure already in Terraform. Instead of needing to configure certificates and Prometheus scrapes for Temporal Cloud out-of-band, Temporal Cloud observability features can now slot nicely in with existing Terraform configuration.

Checklist

2. How was this tested:
   Run acceptance tests

3. Any docs updates needed?
   Docs generated!

[swgillespie]

thank you for all of the hard work on these 🙏 I will check this out!

[anekkanti]

@ennyjfrick thank you for your PR.

The protos/apis you are referring from the tcld repo are meant to be deprecated, and will be replaced by the once in api-cloud repo.
We have a proposed account metrics mgmt apis that we are working on. PR:temporalio/api-cloud#14. We hope to get this out soon.
Can we hold off on this PR and wait for the apis to be available?

[ennyjfrick]

@anekkanti totally fine with me!

[ennyjfrick]

@anekkanti hey! wondering if there was any update on the updated account management APIs

[swgillespie]

@anekkanti can you share any updates you have here?

[anekkanti]

@ennyjfrick @swgillespie
We finally have a path to unblock the above APIs, and i am working on it.
It will likely take us at least a few weeks to get the required APIs out for metrics mgmt.

[ennyjfrick]

@swgillespie @anekkanti I just opened temporalio/api-go#181 to update the generated client with the account get & update operations, will work on redoing this PR so the metrics endpoint resources uses those changes.

[ennyjfrick]

@swgillespie ok, should be good to go and ready for review here.

Two things to note:

1. This uses a commit off of main of go.temporal.io/api rather than a release
2. The protos switched to using enum fields for a bunch of fields that were previously just strings; my PR uses the deprecated string fields whenever a proto field is set since converting everything to the enums is a bigger project.

[swgillespie]

@rohitgup14 @anekkanti can you check this out? ^

[anekkanti]

@ennyjfrick Just merged the changes that moves to using the enums in the new apis.
Can you rebase to those changes in main. Thanks!

[ennyjfrick]

@anekkanti all done!

[anekkanti]

What happens when you create 2 of the temporalcloud_metrics_endpoint resources? Which one will be applied to the account.

Is there a way to make this resource singleton? Not even sure if terraform supports such concept.

[ennyjfrick]

@anekkanti there's no terraform support for singletons explicitly unfortunately, although we could put in some logic that does not allow you to create the resource if the endpoint is already configured and add some annotations stating this is an account singleton; this is what I've seen recommended for similar situations.

[anekkanti]

put in some logic that does not allow you to create the resource if the endpoint is already configured and add some annotations stating this is an account singleton

I definitely like this, it will elevate some of the confusion when someone accidentally creates multiple resources.

[anekkanti]

LGTM, a few things to address:

1. Add a check to the Create where the provider errors out when the cert is already set on the account.
2. Fix lint errors.

[ennyjfrick]

@anekkanti howdy! sorry for the delay, should be good to go now

[ennyjfrick]

@swgillespie / @anekkanti following up

[swgillespie]

@anekkanti @captainbeardo @briankassouf FYI

[ennyjfrick]

@swgillespie @anekkanti think I need one of you to hit the merge button, it's greyed out for me