Skip to main content

SecretSyncBitbucket

Resource SecretSyncBitbucket in pulumi-infisical.
4 min read

Resource SecretSyncBitbucket in pulumi-infisical.

Pulumi type: infisical:index/secretSyncBitbucket:SecretSyncBitbucket.

name is the Pulumi resource name. Nested object fields are documented under that object. They are not arguments of this resource.

Example#

Only required arguments are set. A string in angle brackets stands in for that argument. Any other value is an option or example written in the SDK description.

Arguments#

PropertyTypeRequiredDescription
autoSyncEnabledbooleannoWhether secrets should be automatically synced when changes occur at the source location or not.
connectionIdstringyesThe ID of the bitbucket Connection to use for syncing.
descriptionstringnoAn optional description for the Bitbucket sync.
destinationConfigSecretSyncBitbucketDestinationConfig (input)yesThe destination configuration for the secret sync.
environmentstringyesThe slug of the project environment to sync secrets from.
namestringnoThe name of the Bitbucket sync to create. Must be slug-friendly.
projectIdstringyesThe ID of the Infisical project to create the sync in.
secretPathstringyesThe folder path to sync secrets from.
syncOptionsSecretSyncBitbucketSyncOptions (input)yesParameters to modify how secrets are synced.

Outputs#

Computed outputs are produced by the provider. They are not constructor arguments.

PropertyTypeComputedDescription
autoSyncEnabledbooleannoWhether secrets should be automatically synced when changes occur at the source location or not.
connectionIdstringnoThe ID of the bitbucket Connection to use for syncing.
descriptionstringnoAn optional description for the Bitbucket sync.
destinationConfigSecretSyncBitbucketDestinationConfig (output)noThe destination configuration for the secret sync.
environmentstringnoThe slug of the project environment to sync secrets from.
namestringnoThe name of the Bitbucket sync to create. Must be slug-friendly.
projectIdstringnoThe ID of the Infisical project to create the sync in.
secretPathstringnoThe folder path to sync secrets from.
syncOptionsSecretSyncBitbucketSyncOptions (output)noParameters to modify how secrets are synced.

SecretSyncBitbucketDestinationConfig (input)#

Input object SecretSyncBitbucketDestinationConfig. Fields below belong to this object, not to the parent.

PropertyTypeRequiredDescription
environmentIdstringnoThe Bitbucket deployment environment ID (optional).
repositorySlugstringyesThe Bitbucket repository slug to sync secrets to.
workspaceSlugstringyesThe Bitbucket workspace slug.

SecretSyncBitbucketSyncOptions (input)#

Input object SecretSyncBitbucketSyncOptions. Fields below belong to this object, not to the parent.

PropertyTypeRequiredDescription
disableSecretDeletionbooleannoWhen set to true, Infisical will not remove secrets from Bitbucket. Enable this option if you intend to manage some secrets manually outside of Infisical.
initialSyncBehaviorstringyesSpecify how Infisical should resolve the initial sync to the destination. Supported options: overwrite-destination
keySchemastringnoThe format to use for structuring secret keys in the Bitbucket destination.

SecretSyncBitbucketDestinationConfig (output)#

Output object SecretSyncBitbucketDestinationConfig. Fields below belong to this object.

PropertyTypeAlways presentDescription
environmentIdstringnoThe Bitbucket deployment environment ID (optional).
repositorySlugstringyesThe Bitbucket repository slug to sync secrets to.
workspaceSlugstringyesThe Bitbucket workspace slug.

SecretSyncBitbucketSyncOptions (output)#

Output object SecretSyncBitbucketSyncOptions. Fields below belong to this object.

PropertyTypeAlways presentDescription
disableSecretDeletionbooleanyesWhen set to true, Infisical will not remove secrets from Bitbucket. Enable this option if you intend to manage some secrets manually outside of Infisical.
initialSyncBehaviorstringyesSpecify how Infisical should resolve the initial sync to the destination. Supported options: overwrite-destination
keySchemastringnoThe format to use for structuring secret keys in the Bitbucket destination.