Deploy Oracle Visual Builder Applications.
| Info |
|---|
Either |
| Info |
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. |
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
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.
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. |
...
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.
| ||
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' |
Artifacts
This operation consumes artifacts from the artifacts repository.
...