PushDashboards
Commit and push your saved dashboards to a Git repository.
type: "io.kestra.plugin.git.PushDashboards"
Manually push a single dashboard to Git if the input push is set to true.
id: push_dashboards
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.git.PushDashboards
dashboards: mydashboard # if you prefer templating, you can use "{{ flow.id }}"
url: https://github.com/kestra-io/scripts
username: git_username
password: "{{ secret('GITHUB_ACCESS_TOKEN') }}"
branch: main
commitMessage: "add mydashboard from {{ flow.namespace ~ '.' ~ flow.id }}"
YES
main
The branch to which dashboards should be committed and pushed.
NO
Whether to clone submodules.
YES
Add dashboards from flow: {{ flow.id }}
Git commit message.
YES
**
List of glob patterns or a single one that declares which dashboards should be included in the Git commit.
NO
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.
YES
_dashboards
Directory to which dashboards should be pushed.
YES
The passphrase for the privateKey
.
YES
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).
YES
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.
YES
The URI to clone from.
YES
The username or organization.