feat(apprunner): add ObservabilityConfiguration for AppRunner Service

[mazyu36]

Issue # (if applicable)

Closes #22985 .

Reason for this change

At the moment, L2 Construct does not support a tracing setting for the AppRunner Service.

Description of changes

• Add ObservabilityConfiguration Class
• Add observabilityConfiguration property to the Service Class

Description of how you validated changes

Add unit tests and integ tests.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[lpizzinidev]

Thanks 👍
Left some comments for some minor adjustments and an open question on the vendor property.

[lpizzinidev]

Can you please order this alphabetically?

[mazyu36]

Thanks. I fixed it.

[lpizzinidev]

Suggested change

	* @default Vendor.AWSXRAY
	* @default - tracing is not enabled for the service

From the CloudFormation documentation, it seems we're allowed to omit this value.
Can you please verify if the construct deploys when that is the case?
Ie, changing the implementation to:

    const resource = new CfnObservabilityConfiguration(this, 'Resource', {
      observabilityConfigurationName: props.observabilityConfigurationName,
      traceConfiguration: props.vendor ? {
        vendor: props.vendor,
      } : undefined,
    });

[mazyu36]

Thanks.
I fixed it, and I tried to deploy it.
An Observability Configuration without TraceConfiguration could be deployed.

% aws apprunner describe-observability-configuration --observability-configuration-arn arn:aws:apprunner:us-east-1: 01234567890:observabilityconfiguration/my-observability-no-vendor/1/2bc8fefaddcc4b878c0dfe2598412555 --region us-east-1
{
    "ObservabilityConfiguration": {
        "ObservabilityConfigurationArn": "arn:aws:apprunner:us-east-1:01234567890:observabilityconfiguration/my-observability-no-vendor/1/2bc8fefaddcc4b878c0dfe2598412555",
        "ObservabilityConfigurationName": "my-observability-no-vendor",
        "ObservabilityConfigurationRevision": 1,
        "Latest": false,
        "Status": "ACTIVE",
        "CreatedAt": "2024-06-02T09:46:36.997000+09:00"
    }
}

But the App Runner Service with it could not be deployed. It threw an error.

So, I added the above information to the documentation for the vendor property.

[mazyu36]

Add a validation for observabilityConfigurationName and unit tests.

[mazyu36]

@lpizzinidev
Thank you for the review!
I've addressed all your comments.

[lpizzinidev]

Thanks 👍 Left comments for some final adjustments

[lpizzinidev]

Thanks 👍

[lpizzinidev]

Thanks 👍

[GavinZZ]

LGTM, thanks for contributing!

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[GavinZZ]

@mazyu36 Can you fix the failed unit test please when available?

Pull request has been modified.

[mazyu36]

@GavinZZ
Thanks.
I've updated to resolve conflicts by #30358.

Could you please review and approve again?

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: c850eb3
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one.