Commit 1216df58 authored by jeremy's avatar jeremy

clarify that bconf are generated for Bonita from 7.8.0

parent 229d54d4
...@@ -49,7 +49,7 @@ $ cd bonita-continuous-delivery ...@@ -49,7 +49,7 @@ $ cd bonita-continuous-delivery
$ bcd -s scenarios/build_and_deploy.yml --yes livingapp build -p bonita-vacation-management-example -e Test $ bcd -s scenarios/build_and_deploy.yml --yes livingapp build -p bonita-vacation-management-example -e Test
``` ```
The build process finally generates a **.zip** package and a **.bconf** artifact located in the repository's `target` repository. The generated artifacts are named after the repository's root directory name and the selected environment name. The build process finally generates a **.zip** package and, for Bonita from 7.8.0, a **.bconf** artifact located in the repository's `target` repository. The generated artifacts are named after the repository's root directory name and the selected environment name.
For instance with the `bonita-vacation-management-example` example, the following files will be generated: For instance with the `bonita-vacation-management-example` example, the following files will be generated:
- `bonita-vacation-management-example/target/bonita-vacation-management-example-<environment>-<timestamp>.zip` - `bonita-vacation-management-example/target/bonita-vacation-management-example-<environment>-<timestamp>.zip`
......
...@@ -24,7 +24,7 @@ First, here are the **types of artifacts** that can be deployed: ...@@ -24,7 +24,7 @@ First, here are the **types of artifacts** that can be deployed:
The deployment entry point is called an **Application Archive**. It consists of all artifacts to be deployed and an optional configuration file called **Deployment Descriptor**. This file describes which **Policy** should be applied while deploying each artifact. The deployment entry point is called an **Application Archive**. It consists of all artifacts to be deployed and an optional configuration file called **Deployment Descriptor**. This file describes which **Policy** should be applied while deploying each artifact.
Since BCD 3.0.0, **Application Configuration** artifacts can also be deployed. An Application Configuration artifact has a **.bconf** extension and is generated by the [Living App Build command](livingapp_build.md). Since BCD 3.0.0, **Application Configuration** artifacts can also be deployed. An Application Configuration artifact has a **.bconf** extension and is generated by the [Living App Build command](livingapp_build.md) for Bonita from 7.8.0.
Application Configuration artifacts can be customized using the `bcd livingapp extract-conf|merge-conf` commands as described in [this documentation](livingapp_manage_configuration.md). Application Configuration artifacts can be customized using the `bcd livingapp extract-conf|merge-conf` commands as described in [this documentation](livingapp_manage_configuration.md).
::: danger ::: danger
...@@ -184,7 +184,7 @@ bcd -s <scenario> livingapp deploy -p <application_path> -c <configuration_path> ...@@ -184,7 +184,7 @@ bcd -s <scenario> livingapp deploy -p <application_path> -c <configuration_path>
where: where:
* **\<scenario>** is the path to the BCD scenario which defines the target Bonita stack. Artifacts will be deployed using tenant credentials defined by this scenario (`bonita_tenant_login` and `bonita_tenant_password` variables). * **\<scenario>** is the path to the BCD scenario which defines the target Bonita stack. Artifacts will be deployed using tenant credentials defined by this scenario (`bonita_tenant_login` and `bonita_tenant_password` variables).
* **\<application_path>** is the path to the Application Archive to deploy (zip file or directory). * **\<application_path>** is the path to the Application Archive to deploy (zip file or directory).
* **\<configuration_path>** is the path to the Application Configuration bconf artifact to deploy. * **\<configuration_path>** is the path to the Application Configuration bconf artifact to deploy. This file can be generated for Bonita from 7.8.0
You may deploy an application archive and an application configuration artifact separately. The `bcd livingapp deploy` command requires at least one the deployable artifacts to be provided. You may deploy an application archive and an application configuration artifact separately. The `bcd livingapp deploy` command requires at least one the deployable artifacts to be provided.
......
...@@ -6,7 +6,7 @@ This tutorial describes how to configure your Bonita Living Application from the ...@@ -6,7 +6,7 @@ This tutorial describes how to configure your Bonita Living Application from the
Since BCD 3.0.0, if you build a living Application you will get separatly: Since BCD 3.0.0, if you build a living Application you will get separatly:
- a zip file which contains binaries - a zip file which contains binaries
- a bconf file which contains the configuration for the target [environment](https://documentation.bonitasoft.com/bonita/${bonitaDocVersion}/environments) (Local by default) - and for Bonita from 7.8.0 a bconf file which contains the configuration for the target [environment](https://documentation.bonitasoft.com/bonita/${bonitaDocVersion}/environments) (Local by default)
Here is an example of a build result: Here is an example of a build result:
``` ```
......
...@@ -25,7 +25,7 @@ The following changes introduce incompatibility with BCD 2.x: ...@@ -25,7 +25,7 @@ The following changes introduce incompatibility with BCD 2.x:
* Manage Docker dependencies through a secured public registry * Manage Docker dependencies through a secured public registry
* [Manage Bonita licenses](manage_bonita_licenses.md) with BCD sub-commands (`bcd license [generate,revoke]`) * [Manage Bonita licenses](manage_bonita_licenses.md) with BCD sub-commands (`bcd license [generate,revoke]`)
* [Manage Living Apps Configuration](livingapp_manage_configuration.md) with BCD sub-commands (`bcd livingapp [extract-conf,merge-conf]`) * [Manage Living Apps Configuration](livingapp_manage_configuration.md) with BCD sub-commands (`bcd livingapp [extract-conf,merge-conf]`) for Bonita from 7.8.0
* Create and delete Microsoft Azure resources for the Bonita stack automatically (`bcd_provider: azure`) * Create and delete Microsoft Azure resources for the Bonita stack automatically (`bcd_provider: azure`)
### Enhancements ### Enhancements
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment