aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

AWS::QBusiness::ChatControlsConfiguration - Coverage - New resource type for existing service, API already exists

Open
#2,281 0 comments 1 reaction 0 assignees View on GitHub
Coverage
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

Other

### Resource name

AWS::QBusiness::ChatControlsConfiguration

### Description

Please add the `AWS::QBusiness::ChatControlsConfiguration` resource for the existing `QBusiness` service and the existing [APIs](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/guardrails-api.html).

Note: It looks like there's no API for creating `ChatControlsConfiguration`. Rather in order to create `ChatControlsConfiguration`, you need to call the [UpdateChatControlsConfiguration](https://docs.aws.amazon.com/amazonq/latest/api-reference/API_UpdateChatControlsConfiguration.html) API with the corresponding `applicationId`.

### Other Details

Docs:

- https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/guardrails-api.html
- [GetChatControlsConfiguration](https://docs.aws.amazon.com/amazonq/latest/api-reference/API_GetChatControlsConfiguration.html)
- [UpdateChatControlsConfiguration](https://docs.aws.amazon.com/amazonq/latest/api-reference/API_UpdateChatControlsConfiguration.html)
- [DeleteChatControlsConfiguration](https://docs.aws.amazon.com/amazonq/latest/api-reference/API_DeleteChatControlsConfiguration.html)

Contributor guide

Open the contributing guide

Research direction

Start with the existing QBusiness service implementation and the linked GetChatControlsConfiguration, UpdateChatControlsConfiguration, and DeleteChatControlsConfiguration API documentation. Determine how resource types are represented when creation uses UpdateChatControlsConfiguration, then verify that AWS::QBusiness::ChatControlsConfiguration is covered for the documented APIs.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.