shc integration provision
shc integration provision
Section titled “shc integration provision”prepare a provider for a plug, leaving the plug where it is
Synopsis
Section titled “Synopsis”Run the provision jobs of the socket that serves the plug on the provider, with the plug data the deployment’s own vars render. For postgres that creates the database and its login role, sets the role’s password from the deployment’s vault var, and matches the encoding and collation of the database the plug is on now.
The deployment stays bound where it is. Restore its data into the prepared
provider, then move the plug with shc update <deployment> -i <plug>=<provider>,
which finds the provider prepared.
shc integration provision <deployment> -i <plug>=<provider> [flags]Examples
Section titled “Examples” shc integration provision activepieces -i postgres=postgres shc integration provision activepieces -i postgres=pg2 -t corp -e prodOptions
Section titled “Options” -h, --help help for provision -i, --integrate string the <plug>=<provider> to prepareOptions inherited from parent commands
Section titled “Options inherited from parent commands” --config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win -d, --debug enable debug mode (default: $SHC_DEBUG) -e, --environment string environment name (scoped parent) --exclude string comma-separated dotted paths to drop --fields string comma-separated columns/keys to show (and their order) --filter string comma-separated dotted paths to keep (drops everything else) -o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT) -s, --stack string stack name (scoped parent) -t, --tenant string tenant name (scoped parent) -v, --verbose verbose output (default: $SHC_VERBOSE)SEE ALSO
Section titled “SEE ALSO”- shc integration - manage integrations
shc@docs:~$