awscc_personalize_dataset_group - Allow for custom domains

[DanCRichards]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment
• The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

Description

AWS Personalize (Recommandation Service) usually is run for Ecommerce websites or On Demand video websites. The service also allows for custom domains, for example, recommending news articles on a news website.

awscc_personalize_dataset_group doesn't allow for the instantiation of custom domains which supports this

New or Affected Resource(s)

• awscc_personalize_dataset_group

Potential Terraform Configuration

terraform {
  required_providers {
    awscc = {
      source  = "hashicorp/awscc"
      version = "~> 0.50.0"
    }
  }
}

provider "awscc" {
  region = "ap-southeast-2"
}

resource "awscc_personalize_dataset_group" "personalise-news_site-dataset-group" {
  name = "personalise-news_site-dataset-group"
  domain = "CUSTOM"
}

References

[rupert-evill]

Hi @DanCRichards, you can create a personalize dataset group with a CUSTOM domain by simply omitting the domain argument. For example:

resource "awscc_personalize_dataset_group" "personalize_dataset_group" { name = "personalize_dataset_group" }