Standard Platform Services¶
Purpose & Scope¶
This page will give an outline of the Configuration services that need to be performed by the KaaS Team. This includes a description of how configuration management is handled. Input configurations are handled through the "Qualify once and Deploy many" approach, described in Manage IT Infrastructure SOP [Q216301]. No formal verification using test plans is performed.
Configuration with Teams Provisioning Pipeline¶
- The Teams provisioning Pipeline automates the manual configuration of adding Teams/namespaces, Service Accounts and identity pools (programmatic access to other systems/entities).
It will run multiple times a week, being updated with new configuration each time. To ensure an efficient and controlled process, the following principles will guide "Standard Configuration Input";
- Configuration changes (commits) in the Teams Pipeline /configuration folder - adding Service Accounts, Ad-grp mappings, Namespaces etc. - only needs to be peer-reviewed
- Pipeline deployment approvals ('gates') that only contains updates to the /configuration folder, can be approved by a Platform Operator role and does not have to involve the KaaS Platform Lead
- When deploying these updates, it is acceptable to refer to a specific customer ServiceNow request - ServiceNow CHG IDs are only required when onboarding new Teams or changing source code base
Team Onboarding¶
Team Resources¶
Pipeline Template Onboarding¶
Configuration with Stream Governance Pipeline¶
- Stream Governance Pipeline is used by the KaaS Platform Team to create Business Metadata and Tags. This pipeline will allow the configuration and deployment of business metadata and tags objects that can be applied by onboarding teams with the help of application pipeline template.
Any updates to the Stream governance pipeline are handled via normal change ticket in ServiceNow. Whenever the Stream governance pipeline runs for updating the business metadata and tags by platform teams, it is verified for, - latest code/configuration review followed with Pull Request for successful deployments to QA/PRD environments - CIL baseline verification against the latest available pipeline build and tags in the qualified environments (informal verification done in the ServiceNow CHG ticket itself)
Stream governance pipeline recurrent deployments are verified via items described above and same are captured as part of closure comments in the CHG ticket before its closure by ServiceNow Change manager and ITQC.
Business metadata and tags creation¶
