canasta gitops push

canasta > gitops > push

canasta gitops push

Push configuration changes to the git repository

Synopsis

Commit staged changes and push to the remote repository. Stage changes first with canasta gitops add; commits already made by other commands (such as canasta gitops fix-submodules) are also pushed even when nothing is staged. When pull_requests is enabled in hosts.yaml, creates a branch and opens a pull request instead of pushing directly to main.

canasta gitops push [flags]

Examples

canasta gitops push
canasta gitops push -m 'Add docs wiki'

Flags

Flag	Shorthand	Description	Default	Required	Orchestrator
--id	-i	Canasta instance ID	*		Both
--key		Compose only. Path on the controller (the machine running canasta) to the git-crypt symmetric key, used to unlock the checkout if it is locked. Without it, a repo with GPG recipients is unlocked through a forwarded GPG agent.			Both
--message	-m	Commit message (defaults to 'Configuration update')			Both
--ssh-key		Path on the instance's host to an SSH private key for git network operations. When set, git runs with GIT_SSH_COMMAND="ssh -i <ssh-key> ...". On a remote host, give an absolute path or one starting with a quoted '~' (for example '~/x'). On Compose, the instance remembers the path, and later gitops commands use it when --ssh-key is omitted; passing it again replaces it. Without a remembered key, git uses ssh-agent forwarding on Compose, or the staged deploy key on Kubernetes.			Both

* Defaults to the Canasta instance matching the current directory, if any.

Global flags

Flag	Shorthand	Description	Default	Required	Orchestrator
--help	-h	Show help message and exit			Both
--verbose	-v	Enable verbose output			Both