First set-up Content Repository Resource and client library

[qdegraaf]

First resource as a proof of concept for the Amplience Terraform provider

[qdegraaf]

Content Repositories

Content repositories are separate spaces within a Hub in which content and slots are stored. Through the provider a repository can only be

• Created (name & label fields)
• Updated (name & label fields)
• Read

At present the Amplience Dynamic Content API does not allow deletion of repositories. For adding content to the repository with Terraform see Content Item

Depending on your needs and requirements you may opt to have multiple repositories in a single Hub or use multiple Hubs (see also Hub info).

For more information see the Amplience user documentation and/or the API documentation

Example Usage

resource "amplience_content_repository" "a-generic-content-repository" {
  name = "a highly generic name"
  label = "a good identifying label"
}