Skip to content

vault_secrets_sync.md

Latest commit

 

History

History
59 lines (40 loc) · 1.66 KB

vault_secrets_sync.md

File metadata and controls

59 lines (40 loc) · 1.66 KB
page_title Resource hcp_vault_secrets_sync
subcategory HCP Vault Secrets
description The Vault Secrets sync resource manages an integration.

hcp_vault_secrets_sync (Resource)

The Vault Secrets sync resource manages an integration.

Example Usage

# the provider is derived from the integration name
resource "hcp_vault_secrets_sync" "example_aws_sync" {
  name             = "my-aws-1"
  integration_name = "my-integration-1"
}

Schema

Required

  • integration_name (String) The Vault Secrets integration name.
  • name (String) The Vault Secrets Sync name.

Optional

  • gitlab_config (Attributes) Configuration parameters used to determine the sync destination. (see below for nested schema)
  • project_id (String) HCP project ID that owns the HCP Vault Secrets integration. Inferred from the provider configuration if omitted.

Read-Only

  • id (String) Required ID field that is set to the sync name.
  • organization_id (String) HCP organization ID that owns the HCP Vault Secrets integration.

Nested Schema for gitlab_config

Required:

  • scope (String) The scope to which values apply. The valid options are GROUP and PROJECT

Optional:

  • group_id (String, Sensitive) ID of the group, if the scope is GROUP
  • project_id (String, Sensitive) ID of the project, if the scope is PROJECT

Import

Import is supported using the following syntax:

# Vault Secrets Integration can be imported by specifying the name of the integration
terraform import hcp_vault_secrets_sync.example my-sync-name