eIAM Automation (CI/CD)
Continuous Integration | Continuous Delivery | Continuous DeploymenteIAM Automation of Service Release & Application Integrations
The new eIAM automation platform will meet the following objectives:- An eIAM application integration via the REF/ABN/PROD instances can be individually planned and executed (detailed informations under: CC-PLan).
- The eIAM service changes and new features can be introduced continuously and without service interruptions.
- With the Testing in Canary mode, a service change, a new feature can first be made available to only a small subset of users for testing before it is activated for all.
-
- eIAM automation of service release & application integrations
- Application integration data sources
- The eIAM doser provides all data needed for the eIAM integration REF/ABN/PROD.
- In the context of the eIAM integration project, the necessary system configurations for REF/ABN/PROD are also created
- Filing / Repository
- The integration team places all information from the eIAM dossier and the necessary system configuration in the central repository, the Central Configuration Repository (CCRepo).
- Code generation
- The Generation Engine, together with the eIAM configuration data and the Central Configuration Repository, forms the core of the CI/CD architecture to generate the corresponding codes required per eIAM instance and component.
- Using the Jenkins pipeline, the project/service code updates can be individually created and continuously updated.
- Konfigurationsdaten
- This configuration data is then pushed through the different levels of DEV respectively for applications from REF to PROD (export/import functionality)
- Lieferung
- The respective components are prepared here for "delivery" to the Bundestrustbroker (BTB) and container infrastructures per eIAM instance and can then be specifically activated.
- Operation
- The operation is based on the Bundestrustbroker (BTB) for the identity and attribute switches and a container infrastructure (Kubernetes) which include the following CI/CD advantages:
- High availability thanks to failover facilities
- high scalability
- uninterrupted maintenance
- Canary deployments
- High availability thanks to failover facilities
Implementation Plan (CI/CD)
The eIAM integrated applications will be gradually migrated to the BTB and CI/CD container infrastructure. This migration should be completed transparently and without disruption for all applications by the end of 1st quarter 2024.