pulumi-google-native-kotlin/com.pulumi.googlenative.cloudbuild.v1.kotlin.outputs/GitFileSourceResponse

GitFileSourceResponse

data class GitFileSourceResponse(val bitbucketServerConfig: String, val githubEnterpriseConfig: String, val path: String, val repoType: String, val repository: String, val revision: String, val uri: String)

GitFileSource describes a file within a (possibly remote) code repository.

Constructors

Link copied to clipboard
fun GitFileSourceResponse(bitbucketServerConfig: String, githubEnterpriseConfig: String, path: String, repoType: String, repository: String, revision: String, uri: String)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard
val bitbucketServerConfig: String

The full resource name of the bitbucket server config. Format: projects/{project}/locations/{location}/bitbucketServerConfigs/{id}.

Link copied to clipboard
val githubEnterpriseConfig: String

The full resource name of the github enterprise config. Format: projects/{project}/locations/{location}/githubEnterpriseConfigs/{id}. projects/{project}/githubEnterpriseConfigs/{id}.

Link copied to clipboard
val path: String

The path of the file, with the repo root as the root of the path.

Link copied to clipboard
val repository: String

The fully qualified resource name of the Repo API repository. Either uri or repository can be specified. If unspecified, the repo from which the trigger invocation originated is assumed to be the repo from which to read the specified path.

Link copied to clipboard
val repoType: String

See RepoType above.

Link copied to clipboard
val revision: String

The branch, tag, arbitrary ref, or SHA version of the repo to use when resolving the filename (optional). This field respects the same syntax/resolution as described here: https://git-scm.com/docs/gitrevisions If unspecified, the revision from which the trigger invocation originated is assumed to be the revision from which to read the specified path.

Link copied to clipboard
val uri: String

The URI of the repo. Either uri or repository can be specified. If unspecified, the repo from which the trigger invocation originated is assumed to be the repo from which to read the specified path.