Skip to content

Integration: Overview📜

The following documents should be followed, in order, to move a package to maintained or (*) fully integrate a new package into Big Bang:

  • [ ] 1. Get BBTOC Approval: Follow the BBTOC Package Maintenance Tracks process to get approval for package integration
  • [ ] 2. Notify Cyber: Notify the Cyber team of the new package integration to begin security review
  • [ ] 3. Upstream Helm Chart: Initialize package workspace using an upstream Helm chart
  • [ ] 4. CICD Pipeline: Establish a baseline package pipeline for testing changes
  • [ ] 5. *Flux Helm Chart: Create Flux compatible GitOps Helm chart required by Big Bang
  • [ ] 6. Big Bang Common Library: Integrate with bb-common for service mesh, network policies, and Istio hardening
  • [ ] 7. Monitoring: Enable metrics scraping on product
  • [ ] 8. Database: If required, add internal and external database support using Big Bang values
  • [ ] 9. Object Storage: If required, add internal or external object storage support using Big Bang values
  • [ ] 10. Single-Sign On: If available, add Single-Sign On (SSO) through internal or external identify provider
  • [ ] 11. Additional Tests: Add testing to validate basic functionality
  • [ ] 12. Policy Enforcement: Update package to comply with default security and governance policies in Big Bang
  • [ ] 13. Cyber Review: Complete Cyber security review and address any findings
  • [ ] 14. Supported Package: Migrate package into the Big Bang repo as an integrated or maintained package
  • [ ] 15. Final Documentation: Add additional Big Bang documentation for final release
  • [ ] 16. *Big Bang Merge Request: Create Big Bang Merge Request and run all packages pipeline