App is the Schema for the Apps API. Provides an Amplify App resource.
Type
CRD
Group
amplify.aws.upbound.io
Version
apiVersion: amplify.aws.upbound.io/v1beta1
kind: App
AppSpec defines the desired state of App
No description provided.
Personal access token for a third-party source control system for an Amplify app. This token must have write access to the relevant repo to create a webhook and a read-only deploy key for the Amplify project. The token is not stored, so after applying this attribute can be removed and the setup token deleted.
Automated branch creation configuration for an Amplify app. An auto_branch_creation_config block is documented below.
Automated branch creation glob patterns for an Amplify app.
Reference to a Role in iam to populate iamServiceRoleArn.
Policies for referencing.
Selector for a Role in iam to populate iamServiceRoleArn.
Policies for selection.
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.
Personal access token for a third-party source control system for an Amplify app. This token must have write access to the relevant repo to create a webhook and a read-only deploy key for the Amplify project. The token is not stored, so after applying this attribute can be removed and the setup token deleted.
Automated branch creation configuration for an Amplify app. An auto_branch_creation_config block is documented below.
Automated branch creation glob patterns for an Amplify app.
Reference to a Role in iam to populate iamServiceRoleArn.
Policies for referencing.
Selector for a Role in iam to populate iamServiceRoleArn.
Policies for selection.
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.
AppStatus defines the observed state of App.
No description provided.
Automated branch creation configuration for an Amplify app. An auto_branch_creation_config block is documented below.
Automated branch creation glob patterns for an Amplify app.
Describes the information about a production branch for an Amplify app. A production_branch block is documented below.
Conditions of the resource.
example
apiVersion: amplify.aws.upbound.io/v1beta1
kind: App
metadata:
annotations:
meta.upbound.io/example-id: amplify/v1beta1/webhook
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
name: app
region: us-west-1
example
apiVersion: amplify.aws.upbound.io/v1beta1
kind: App
metadata:
annotations:
meta.upbound.io/example-id: amplify/v1beta1/branch
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
name: app
region: us-west-1
example
apiVersion: amplify.aws.upbound.io/v1beta1
kind: App
metadata:
annotations:
meta.upbound.io/example-id: amplify/v1beta1/backendenvironment
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
name: example
region: us-west-1
example
apiVersion: amplify.aws.upbound.io/v1beta1
kind: App
metadata:
annotations:
meta.upbound.io/example-id: amplify/v1beta1/app
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
buildSpec: |
version: 0.1
frontend:
phases:
preBuild:
commands:
- yarn install
build:
commands:
- yarn run build
artifacts:
baseDirectory: build
files:
- '**/*'
cache:
paths:
- node_modules/**/*
customRule:
- source: /<*>
status: "404"
target: /index.html
environmentVariables:
ENV: test
name: example
region: us-west-1
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.