Codepipeline is the Schema for the Codepipelines API. Provides a CodePipeline
Type
CRD
Group
codepipeline.aws.upbound.io
Version
apiVersion: codepipeline.aws.upbound.io/v1beta1
kind: Codepipeline
CodepipelineSpec defines the desired state of Codepipeline
No description provided.
One or more artifact_store blocks. Artifact stores are documented below.
The encryption key block AWS CodePipeline uses to encrypt the data in the artifact store, such as an AWS Key Management Service (AWS KMS) key. If you don't specify a key, AWS CodePipeline uses the default key for Amazon Simple Storage Service (Amazon S3). An encryption_key block is documented below.
Reference to a Bucket in s3 to populate location.
Policies for referencing.
Selector for a Bucket in s3 to populate location.
Policies for selection.
Reference to a Role in iam to populate roleArn.
Policies for referencing.
Selector for a Role in iam to populate roleArn.
Policies for selection.
(Minimum of at least two stage blocks is required) A stage block. Stages are documented below.
The action(s) to include in the stage. Defined as an action block below
A list of artifact names to be worked on.
A list of artifact names to output. Output artifact names must be unique within a pipeline.
A trigger block. Valid only when pipeline_type is V2. Triggers are documented below.
Provides the filter criteria and the source stage for the repository event that starts the pipeline. For more information, refer to the AWS documentation. A git_configuration block is documented below.
The field where the repository event that will start the pipeline is specified as pull requests. A pull_request block is documented below.
The field that specifies to filter on branches for the pull request trigger configuration. A branches block is documented below.
A list that specifies which pull request events to filter on (opened, updated, closed) for the trigger configuration. Possible values are OPEN, UPDATED and CLOSED.
The field that specifies to filter on file paths for the pull request trigger configuration. A file_paths block is documented below.
The field where the repository event that will start the pipeline, such as pushing Git tags, is specified with details. A push block is documented below.
A pipeline-level variable block. Valid only when pipeline_type is V2. Variable are documented below.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
One or more artifact_store blocks. Artifact stores are documented below.
The encryption key block AWS CodePipeline uses to encrypt the data in the artifact store, such as an AWS Key Management Service (AWS KMS) key. If you don't specify a key, AWS CodePipeline uses the default key for Amazon Simple Storage Service (Amazon S3). An encryption_key block is documented below.
Reference to a Bucket in s3 to populate location.
Policies for referencing.
Selector for a Bucket in s3 to populate location.
Policies for selection.
Reference to a Role in iam to populate roleArn.
Policies for referencing.
Selector for a Role in iam to populate roleArn.
Policies for selection.
(Minimum of at least two stage blocks is required) A stage block. Stages are documented below.
The action(s) to include in the stage. Defined as an action block below
A list of artifact names to be worked on.
A list of artifact names to output. Output artifact names must be unique within a pipeline.
A trigger block. Valid only when pipeline_type is V2. Triggers are documented below.
Provides the filter criteria and the source stage for the repository event that starts the pipeline. For more information, refer to the AWS documentation. A git_configuration block is documented below.
The field where the repository event that will start the pipeline is specified as pull requests. A pull_request block is documented below.
The field that specifies to filter on branches for the pull request trigger configuration. A branches block is documented below.
A list that specifies which pull request events to filter on (opened, updated, closed) for the trigger configuration. Possible values are OPEN, UPDATED and CLOSED.
The field that specifies to filter on file paths for the pull request trigger configuration. A file_paths block is documented below.
The field where the repository event that will start the pipeline, such as pushing Git tags, is specified with details. A push block is documented below.
A pipeline-level variable block. Valid only when pipeline_type is V2. Variable are documented below.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
CodepipelineStatus defines the observed state of Codepipeline.
No description provided.
One or more artifact_store blocks. Artifact stores are documented below.
The encryption key block AWS CodePipeline uses to encrypt the data in the artifact store, such as an AWS Key Management Service (AWS KMS) key. If you don't specify a key, AWS CodePipeline uses the default key for Amazon Simple Storage Service (Amazon S3). An encryption_key block is documented below.
(Minimum of at least two stage blocks is required) A stage block. Stages are documented below.
The action(s) to include in the stage. Defined as an action block below
A list of artifact names to be worked on.
A list of artifact names to output. Output artifact names must be unique within a pipeline.
A trigger block. Valid only when pipeline_type is V2. Triggers are documented below.
Provides the filter criteria and the source stage for the repository event that starts the pipeline. For more information, refer to the AWS documentation. A git_configuration block is documented below.
The field where the repository event that will start the pipeline is specified as pull requests. A pull_request block is documented below.
The field that specifies to filter on branches for the pull request trigger configuration. A branches block is documented below.
A list that specifies which pull request events to filter on (opened, updated, closed) for the trigger configuration. Possible values are OPEN, UPDATED and CLOSED.
The field that specifies to filter on file paths for the pull request trigger configuration. A file_paths block is documented below.
The field where the repository event that will start the pipeline, such as pushing Git tags, is specified with details. A push block is documented below.
A pipeline-level variable block. Valid only when pipeline_type is V2. Variable are documented below.
Conditions of the resource.
codepipeline
apiVersion: codepipeline.aws.upbound.io/v1beta1
kind: Codepipeline
metadata:
annotations:
meta.upbound.io/example-id: codepipeline/v1beta1/codepipeline
labels:
testing.upbound.io/example-name: codepipeline
name: codepipeline
spec:
forProvider:
artifactStore:
- locationSelector:
matchLabels:
testing.upbound.io/example-name: codepipeline_bucket
type: S3
region: us-west-1
roleArnSelector:
matchLabels:
testing.upbound.io/example-name: codepipeline_role
stage:
- action:
- category: Source
configuration:
Branch: master
OAuthToken: your-token-here
Owner: my-organization
Repo: test
name: Source
outputArtifacts:
- test
owner: ThirdParty
provider: GitHub
version: "1"
name: Source
- action:
- category: Build
configuration:
ProjectName: test
inputArtifacts:
- test
name: Build
outputArtifacts:
- build_output
owner: AWS
provider: CodeBuild
version: "1"
name: Build
- action:
- category: Deploy
configuration:
ActionMode: REPLACE_ON_FAILURE
Capabilities: CAPABILITY_AUTO_EXPAND,CAPABILITY_IAM
OutputFileName: CreateStackOutput.json
StackName: MyStack
TemplatePath: build_output::sam-templated.yaml
inputArtifacts:
- build_output
name: Deploy
owner: AWS
provider: CloudFormation
version: "1"
name: Deploy
© 2024 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.