PushApps
Commit and push Kestra Apps created from kestra UI to Git.
type: "io.kestra.plugin.ee.git.PushApps"
Manually push a single app to Git if the input push is set to true.
id: push_apps
namespace: prod
inputs:
- id: push
type: BOOLEAN
defaults: false
tasks:
- id: if
type: io.kestra.plugin.core.flow.If
condition: "{{ inputs.push == true}}"
then:
- id: commit_and_push
type: io.kestra.plugin.ee.git.PushApps
apps: myapp
url: https://github.com/kestra-io/scripts
username: git_username
password: "{{ secret('GITHUB_ACCESS_TOKEN') }}"
branch: main
commitMessage: "add myapp from {{ flow.namespace ~ '.' ~ flow.id }}"
**
Which Apps should be included in the commit.
kestra
The branch to which Apps should be committed and pushed.
If the branch doesn’t exist yet, it will be created. If not set, the task will push the files to the kestra
branch.
Whether to clone submodules.
Add apps from {{ flow.id }} namespace
Git commit message.
false
If true
, the task will only output modifications without pushing any file to Git yet. If false
(default), all listed files will be pushed to Git immediately.
_apps
Directory to which Apps should be pushed.
The passphrase for the privateKey
.
The password or Personal Access Token (PAT). When you authenticate the task with a PAT, any flows or files pushed to Git from Kestra will be pushed from the user associated with that PAT. This way, you don't need to configure the commit author (the authorName
and authorEmail
properties).
PEM-format private key content that is paired with a public key registered on Git.
To generate an ECDSA PEM format key from OpenSSH, use the following command: ssh-keygen -t ecdsa -b 256 -m PEM
. You can then set this property with your private key content and put your public key on Git.
The URI to clone from.
The username or organization.