[RANCHER-2] Automatic FOLIO set up in the Scratch dev environments. Created: 07/Sep/20 Updated: 25/Feb/22 Resolved: 25/Feb/22 |
|
| Status: | Closed |
| Project: | rancher |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Taras Spashchenko | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | KT-ID | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original estimate: | Not Specified |
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||
| Sub-tasks: |
|
||||||||||||||||||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||||||||||||||||||
| Story Points: | 21 | ||||||||||||||||||||||||||||||||||||||||
| Development Team: | Kitfox | ||||||||||||||||||||||||||||||||||||||||
| Description |
|
It is required to automate FOLIO set up in the Scratch dev environments.
As a result, a completely separate FOLIO platform must be deployed in the team’s project in Rancher.
Once testing has been completed and the deployed platform is not needed any more there should be a dedicated Jenkins job intended for clean up. The developer has to provide just tenantId for that and all the applications launched by the previous Jenkins job will be removed as well as the DB schemas created during modules’ enablement for the tenant. |
| Comments |
| Comment by Stanislav Miroshnichenko [ 10/Dec/20 ] |
|
Pipeline to deploy backend modules and Stripes bundle Basically, we have to create Jenkins pipeline with parameters:
Here is the 'modules' structure example: }, , ] If 'repository' filed is not empty, Jenkins job must build docker container and push it to 'docker.dev.folio.org' repository. Typical steps for Jenkins job: |
| Comment by Vitaly Demchenko [ 25/Feb/22 ] |
|
Mostly done. Multi-tenancy will be covered by unified pipeline |