Apply remaining
The apply-remaining workflow step deploys the remainder components that have not been deployed. This is useful for applications that are being deployed component-by-component using the apply-component workflow step, or other custom workflow step definition that partially renders the application.
The following snippet shows an application where component1
is first deployed using the apply-component workflow step, and then all the remainder components are deployed using the apply-remaining workflow step. Notice that for the purpose of the example, component3
has been excluded and will never be deployed.
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: my-app
annotations:
version: "v0.0.1"
description: "My apply-remaining application"
spec:
components:
- name: component1
type: worker
properties:
image: my-app-image:v1.0.0
cmd: ["cmd"]
cpu: "0.25"
memory: "200Mi"
- name: component2
type: worker
properties:
image: my-app-image:v1.0.0
cmd: ["cmd"]
cpu: "0.25"
memory: "200Mi"
- name: component3
type: worker
properties:
image: my-app-image:v1.0.0
cmd: ["cmd"]
cpu: "0.25"
memory: "200Mi"
workflow:
steps:
- name: deploy-server1
type: apply-component
properties:
component: "component2"
- name: deploy-remaining #
type: apply-remaining # Set to apply-remainig
properties:
exceptions: ["component3"] # (Optional) name of components that will not be deployed