vb-export

Downloads application sources from the Visual Builder instance and expands the archive on the local file system for further processing.

The following table describes the subtasks, hooks, and inputs and outputs of the vb-export task:

The following tables describe the options for the vb-export task.

Application selection options

Name	Mandatory	Default Value	Description
id	yes	n/a	ID of the visual application you're going to build. The application needs to exist on the referred Visual Builder instance.
ver	yes	n/a	Version of the visual application
url[:dt]	yes	n/a	URL of your Visual Builder service instance. The `dt` suffix is optional.

Authentication options

Name	Mandatory	Default Value	Description
username[:dt]	no	n/a	The username to be used to obtain OAuth access token for further communication with Visual Builder services. The `dt` suffix is optional.
password[:dt]	no	n/a	The password to be used to obtain OAuth access token for further communication with Visual Builder services. The `dt` suffix is optional. A password specified via the `--password` Grunt option may need to be enclosed in single quotation marks (') if it contains special characters. In general, it's advisable to always use quotation marks for the `--password` option, especially in VB Studio jobs where the password is provided via a job variable. For example: `grunt vb-deploy '--password=Jkl@#&!%^23' ...`.
accessToken[:dt]	no	n/a	The value of an OAuth access token. If provided, username and password options are not necessary. The `dt` suffix is optional.
sslCertificate[:dt]	no	n/a	The path to the SSL certificate for the connection to Visual Builder instances provisioned with self-signed certificates. The `dt` suffix is optional.

Build options

Name	Mandatory	Default Value	Description
git-sources	no	./	The location of the sources of the visual application.