Время создания
Filters

Clio release version 6.1.0.15 allows you to save package states from your Creatio environment to the manifest file. You can use the following command to save settings to a file. 

clio save-manifest "C:\GitOps\production-manifest.yaml" -e production

 

Clio stores packages' Names and hash, which are based on ModifiedOn, Checksum, and Names of relative Schemas. For example

Also in the manifest file, Clio store feature states and addresses 

And web services addresses

If the manifest file does not exist, this command will create it. if the file already exists, Clio rewrites it. This behavior was created to organize the flow to store and monitor changes using Git.

 

 

0 comments
Show all comments
Idea
Discussion

 

Clio version 6.1.0.14 has been released. What`s new:

Added support for custom naming your composable application in Hubs. Now, you can specify aliases that Clio will use to find application releases in the file system. Example:

 

Environment:
  url: https://preprod.creatio.com
  authappurl: https://preprod.creatio.com/0/ServiceModel/AuthService.svc/Login
 
apps:
  - name: CrtCustomer360
    version: "1.5.2"
    apphub: MyAppHub
    aliases: ["Customer360"]
 
 
app_hubs:
  - name: MyAppHub
    path: "//MyAppHub/Apps"

 

Fix behavior for environment settings when -e is provided.

clio apply-manifest my-prod-manifest.yaml -e prod 

 

P.S: Next releases will add a feature for storing information about the list of packages from environment to manifest and ability transfer configuration between two Creatio instances

0 comments
Show all comments

Clio version 6.1.0.13 was released. Now, you can add packages to the workspace with auto generate composable application descriptors.

 

// Init clio workspace
clio createw
 
// Add package to workspace
clio add-package MyApp -a True

 

If you have one application in the workspace, new packages will automatically be included in it.

 

// Init clio workspace
clio createw
 
// Add package and app metadata to the workspace
clio add-package MyApp -a True
 
// Add a package to the workspace and include it in MyApp
clio add-package MyPackage

 

This command can be used to add several applications to one workspace.

 

// Init clio workspace
clio createw
 
// Add first app to workspace
clio add-package MyApp1 -a True
 
// Add the second app to the workspace
clio add-package MyApp2 -a True

 

P.S: Error of work with temp directories in multiple Clio instances at one time was fixed

0 comments
Show all comments

Clio release 6.1.0.12 provides a command to create a state manifest for the Creatio instance and store the configuration of web services and feature states.

 

clio save-state "D:\manifest\myinstance-creatio-manifest.yaml" -e MyInstance

 

Storing this file in Git can be used to control instance changes. In future releases, the manifest file will store sys-settings values, applications, and packages, and it will also clone environment settings to clean Creatio instances.

 

P.S: Also the ability to work with HotFix mode was added to Clio commands. To enable/disable it use the following command

 

# To enable hot-fix mode for a package  
clio pkg-hotfix <PACKAGE_NAME> true -e <ENVIRONMENT_NAME> 
 
# To disable hot-fix mode for a package 
clio pkg-hotfix <PACKAGE_NAME> false -e <ENVIRONMENT_NAME> 

 

0 comments
Show all comments
Idea
Discussion

Clio release 6.1.0.8 extends the ability to configuare your Creatio environments in a GitOps manner. Now, you can configure the URL address of WebServices in the manifest file.

environment:
  url: https://production.creatio.com
 
webservices:
  - name: GoogleAnalytics
    url: "https://google.ca"
  - name: FaceBookAPI
    url: "https://facebook.com/api"
 
app:
# list of applications
 
app-hubs:
# list of application stores
 
settings:
# list of sys-settings and value
 
features:
# list of features

Also, we extend the Clio commands and add abilities to see all web services, and their addresses

clio get-webservice-url -e <environment-name>

Improvements: From release 6.1.0.8, you can set the working directory for Clio via the Environment variable CLIO_WORKING_DIRECTORY. 

<your workplace>/tasks/set-clio-working-directory "c:\Temp\ClioWorkDir"

It helps avoid problems with CI\CD pipelines when you can't access default temp directories.

 

COMING SOON: In the next release, a "save-configuration-to-manifest" command will be released

0 comments
Show all comments