|
1 | 1 | <h1>Cloud Scripting Overview</h1> |
2 | 2 |
|
3 | | -Jelastic <b>Cloud Scripting (CS)</b> is a tool, designed to program the cloud platform behaviour related to your application lifecycle for automating frequent tasks, complex CI/CD flows and clustering configurations. |
| 3 | +<b>Cloud Scripting (CS)</b> is a tool, designed to program the cloud platform behaviour related to your application lifecycle for automating frequent tasks, complex CI/CD flows and clustering configurations. |
4 | 4 |
|
5 | 5 | <center></center> |
6 | 6 |
|
7 | 7 | There are three main pillars of cloud scripting: |
8 | 8 |
|
9 | | -* **Actions** - scripted logic for executing a set of commands to automate the tasks. The system provides a default list of actions and possibility to <a href="creating-manifest/custom-scripts/" target="_blank">script custom actions</a> using <a href="https://docs.jelastic.com/api/" target="_blank">API calls</a>, Linux bash <a href="creating-manifest/actions/#cmd" target="_blank">shell command</a>, JS and Java scripts |
| 9 | +* **Actions** - scripted logic for executing a set of commands to automate the tasks. The system provides a default list of actions and possibility to <a href="creating-manifest/custom-scripts/" target="_blank">script custom actions</a> using <a href="https://www.virtuozzo.com/application-platform-api-docs/" target="_blank">API calls</a>, Linux bash <a href="creating-manifest/actions/#cmd" target="_blank">shell command</a>, JS and Java scripts |
10 | 10 |
|
11 | 11 | * **Events** - specific <a href="creating-manifest/events/" target="_blank">triggers</a> for executing actions on a required application lifecycle stage |
12 | 12 |
|
13 | 13 | * **Injection** - supplying default actions, <a href="creating-manifest/placeholders/" target="_blank">placeholders</a>, platform API methods, environment variables, request parameters and input settings in custom scripts by default |
14 | 14 |
|
15 | | -<p dir="ltr" style="text-align: justify;">The developed Cloud Scripting solutions are wrapped into packages and distributed with Jelastic Packaging Standard (<a href="https://docs.jelastic.com/jps" target="_blank">JPS</a>). This is accomplished through preparing a manifest file in JSON format. Such packaged solutions can be effortlessly deployed to the platform via <a href="https://docs.jelastic.com/environment-import" target="_blank">import</a> functionality.</p> |
| 15 | +<p dir="ltr" style="text-align: justify;">The developed Cloud Scripting solutions are wrapped into packages and distributed with Jelastic Packaging Standard (<a href="https://www.virtuozzo.com/application-platform-docs/jps/" target="_blank">JPS</a>). This is accomplished through preparing a manifest file in JSON format. Such packaged solutions can be effortlessly deployed to the platform via <a href="https://www.virtuozzo.com/application-platform-docs/environment-import/" target="_blank">import</a> functionality.</p> |
16 | 16 |
|
17 | | -<p dir="ltr" style="text-align: justify;">The example below represents the Cloud Scripting basic use case. This manifest declares the creation of a new environment with the Jelastic-certified Payara Micro cluster image and provides possibility to configure new cluster members while scaling nodes. Within the manifest, the following key parameters are declared:</p> |
| 17 | +<p dir="ltr" style="text-align: justify;">The example below represents the Cloud Scripting basic use case. This manifest declares the creation of a new environment with the Payara Micro cluster image and provides possibility to configure new cluster members while scaling nodes. Within the manifest, the following key parameters are declared:</p> |
18 | 18 |
|
19 | 19 | * `nodes` - a environment topology which will be created |
20 | 20 |
|
|
0 commit comments