Deploy Oracle Visual Builder Applications.
If a team.json file is found in the artifacts directory, it will be imported into the instance after being deployed. To get a team.json file, look at the export team input in the export application operation.
Either FDOVB_CLOUD_ACCOUNT_CODE Target property value or FDOVB_INP_CLOUD_ACCOUNT_CODE plugin input value should be configured. When both are set, the plugin input value will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup Cloud Account for OVB.
In order to deploy an application it must have both the rootURL and version set in the visual-application.json file. The rootURL is used as the application ID and version as the version. If you use the export application operation this will be set automatically.
deployApplication operation must be used along with the buildApplication. Only using exportApplication in the build workflow directly, will not suffice.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Visual Builder Account |
| No | The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Application Profile ID |
| No | Oracle Visual Builder Application Profile ID. Default is generally base_configuration. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Oracle Visual Builder Account |
| No | The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance. |
Publish Application |
| No | Publish the app, or just stage it. |
Delete if Already Live |
| No | Delete the app if it is already live. If this option is checked, basic auth is not supported. This is due to the REST API being used to determine if an app is already live. |
Schema |
| No | Specifies data schema processing during application stage or publish. Value of 'new' creates a new data schema. Value of 'dev' uses the data schema from development. Value of 'stage' uses the data schema from the previous staged version of the application. Value of 'live' uses the data schema from the previous live version of the application. Defaults to 'new' |
Node Executable Path |
| No | An absolute path to a Node executable or its parent directory. If not given, node in path will be considered. @Since 6.5.0.16 |
Nodejs Version |
| No | Nodejs version. Installs node with the provided version. This input will be ignored if the input |
NPM Install Arguments |
| No | Allows to enter one or more arguments to npm install command. (Ex --no-optional). @Since 6.5.0.13 |
.npmrc |
| No | npm configurations entered as list of key = value parameters (e.g. loglevel=notice), one key value pair per line. @Since 6.5.0.15 All default npmrc configurations are listed when the command “npm config list -l” is run. Some examples are- 1.registry=https://registry.npmjs.org/ (Specifies the URL of the npm registry) 2.strict-ssl=false (Controls SSL certificate validation during HTTPS requests.) 3.proxy=http://your-proxy-url:port 4.loglevel=verbose (Sets the logging level for npm output (e.g., 5.production=true (Instructs npm to skip installation of devDependencies.) For more details, refer npm-config | npm Docs Also, when multiple .npmrc files are available, npm follows a specific hierarchy for merging these configurations. Such as Project-Specific > User-Specific >Global. For more details, refer https://docs.npmjs.com/cli/v10/configuring-npm/npmrc |
Artifacts
This operation consumes artifacts from the artifacts repository.
Endpoint Selection
This operation delegates the selection to the workflow developer to determine.
Endpoint Execution
This operations delegates the execution to the workflow developer to decide.