LinkedIn
X 4 posts tagged with "CI/CD and automation"
Data Flow governance for Data Integration: automated audit trails with CI/CD
- This blog is specifically about Data Integration, not Boomi Integration (iPaaS). The assets, concepts, and APIs here apply only to Data Integration Data Flows.
- The Boomi Data Integration API uses
riverin its field names and endpoints. For example,river_cross_idandriver_status. Throughout this blog, Data Flow is the product term. API field names are shown exactly as they appear in the API request and responses. bdi-auditis the name given to the reference implementation repository in this blog. It isn't a repository you can clone. Every script and pipeline file it uses is linked from this blog, so you can download them and create your own repository.- This reference implementation is Bitbucket Pipelines-specific: the audit step calls the Bitbucket REST API directly to open and merge pull requests. It won't run as-is on GitHub Actions or another CI platform without rewriting that step.
Building a Data Flow in Boomi Data Integration is easy: drag, drop, connect, done. But here's the question nobody thinks about until it's urgent — who changed that PostgreSQL-to-Snowflake schedule at 2 AM, and why? Or when did a source mapping shift?
When your governance framework or compliance audit asks, "What changed and when?" you need a real answer. Without a change history, you're stuck piecing things together from UI session logs or asking around until someone remembers.
That's exactly what this version control system solves. It treats your Data Flow configurations as version-controlled artifacts: a CI/CD pipeline automatically snapshots your Data Flows, detects changes, and opens a pull request for every Data Flow that drifts. Your team gets a living audit trail with zero manual effort.
Build, test, and deploy EDI integrations faster with Boomi Companion
Building EDI (Electronic Data Interchange) integrations can be slow, complex, and frustrating. Weeks of mapping, testing, and coordinating across multiple systems can quickly stretch into months.
That is exactly what Boomi Companion solves. It lets you describe your integration requirements in plain English and have them built, tested, and deployed in hours. This is not just a concept. It is already a production reality for thousands of businesses, transforming how they connect systems and automate workflows.
Pipelines-as-code for Data Integration: CI/CD with REST & GitHub Actions
Data Integration makes it easy to build Data Flows in the UI. You can drag, drop, and connect things faster. But relying solely on the UI can run into problems, especially when you need to move a pipeline between environments without breaking anything and ensuring repeatable deployments, reviews, and traceability. Suddenly, that “clicky” workflow starts showing cracks.
This is where treating your integrations like code comes in! By leveraging REST APIs and treating your configuration as an artifact, you can automatically version, test, and deploy, giving your Boomi projects the same DevOps treatment your apps already enjoy.
Automating Branch and Merge Functionality with the Boomi Enterprise Platform API
Boomi’s November 2024 release introduced Branch and Merge functionality into the Boomi Platform. While the platform does have a user interface to create branches, package and deploy components on branches, and eventually merge branches, a less talked about but necessary functionality is the ability to automate these processes via API calls to the Boomi Enterprise Platform API.
