Skip to end of banner
Go to start of banner

(DRAFT) Manage Scratch Environment ver 1.2

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Link: Manage Scratch Environment ver 1.2

Description

This pipeline was designed to build a scratch Rancher environment. Development of pipeline in progress.  

!!! Note !!! Not all options are checked

General properties

Listed properties cannot be modified without full recreation of related resource.

Postgre DB version
DB Size

Build with parameter

Available parameters:

teamName, Action, TenantName, Repo, Plan, Change, Register, branch, platform_image


Parameter teamName:

Specifies the name of environment and access parameters in Rancher. For most values admin and members of github teamName team have access to Rancher to configure module deployment.


Development TeamStatusRancher permissionsPurposePlatform-core branchEnv. re-creation ticketDevelopment team status (optional)Feedback
metadata

CHECKEDAvailable to use.

Spitfire
platform-complete/master

RANCHER-31 - Getting issue details... STATUS



concorde

CHECKED Available to use.

Firebird

platform-core/concorde-rancher

RANCHER-70 - Getting issue details... STATUS



core-functional

IN REVIEW

prokopovych/core-functional
platform-complete/prokopovych-rancher

RANCHER-54 - Getting issue details... STATUS



volaris

CHECKEDAvailable to use.

Volaris

platform-core/volaris-rancher

RANCHER-75 - Getting issue details... STATUS



volaris-2nd

IN REVIEWAvailable to use.

Volaris
platform-core/volaris-rancher

RANCHER-78 - Getting issue details... STATUS



core-platform

CHECKEDAvailable to use.

Core Platform
platform-complete/core-platform-rancher

RANCHER-53 - Getting issue details... STATUS



ebsco-core

INITIAL







falcon

CHECKEDAvailable to use.

Falcon
platform-core/falcon-rancher

RANCHER-56 - Getting issue details... STATUS



firebird

CHECKED Available to use.

Firebird

platform-core/firebird-rancher

RANCHER-49 - Getting issue details... STATUS



folijet

CHECKED Available to use.

Folijet

platform-core/folijet-rancher

RANCHER-47 - Getting issue details... STATUS



vega

CHECKED Available to use.

Vega

platform-core/vega-rancher

RANCHER-55 - Getting issue details... STATUS



spanish

CHECKED Available to use.

Spanish
platform-complete/master

FOLIO-3320 - Getting issue details... STATUS



spitfire

IN REVIEWAvailable to use.

Spitfire
platform-core/spitfire-rancher

RANCHER-48 - Getting issue details... STATUS



stripes-force

INITIAL







thor

INITIAL







thunderjet

CHECKEDAvailable to use.

thunderjet
platform-core/thunderjet-rancher

RANCHER-52 - Getting issue details... STATUS



unamUsed for testing config.






Parameter Action:

Specifies what action will be performed.

ValueDescription
createCreate environment with specified parameters.
update

Update enviroment with new list of modules. 
Can be used for creation – NOT  RECOMMENDED

deleteDelete enviroment. DB data will be erased.

Parameter TenantName:

Default value: diku

This parameter specifies tenantID for enviroment. Okapi will contain 2 tenants supertenant and TenantName. All modules will be registered and deployed within tenant TenantName

!!! NOTE !!! Module platform-complete is configured to address a specific tenant, which is determined during BUILD-UI.

Parameter Repo and branch:

Files okapi-install.json & stripes-install.json are used to create/update environment. They can be specified with repo and branch. 

Repo value stands for platform-core or platform-complete.

There is separated list of branches for each value of repo.

!!! NOTE !!! If selected branch does not contain okapi-install.json & stripes-install.json, pipeline will fail.

There are created branches in platform-core (e.g. folijet-rancher). These branches contain a list of modules required for a particular team.

Parameter platform_image:

Specified image will be used for module platform-complete. Available values are formed by BUILD-UI.

  • No labels