USE CASE
Implement
CI/CD Pipeline Flows
for Broadcom Layer7
Staying ahead of the curve
The Challenge
Successful companies that offer APIs to their customers and partners prioritize staying ahead of the competition. This entails providing secure data transfer and customizable services that can keep up with changing technology. The key to achieving this is through APIOps, which involves continuous integration and development.
By adopting agile practices, API developers, testers, and app testers can work efficiently without any major disruptions. This enables the company to quickly and easily comply with any internal or external requirements and regulations.
In order to maintain smooth and agile operations that can respond to ongoing needs and requirements, automation is crucial for business as usual scenarios. By prioritizing APIOps, companies can continue to deliver high-quality services and stay ahead of the curve.
By adopting agile practices, API developers, testers, and app testers can work efficiently without any major disruptions. This enables the company to quickly and easily comply with any internal or external requirements and regulations.
In order to maintain smooth and agile operations that can respond to ongoing needs and requirements, automation is crucial for business as usual scenarios. By prioritizing APIOps, companies can continue to deliver high-quality services and stay ahead of the curve.
The Solution
As a Solution, APIIDA presents the APIIDA API Gateway Manager to be installed in the management layer.
We bring the following key features for the outlined scenario:
Centralized Management
capabilities
The APIIDA API Gateway Manager is designed to connect to many Layer7 API gateway runtimes in a central administration platform. This platform allows to manage connections to the different runtimes, discover APIs on each runtime and register them against environment constrains. Configure alarm thresholds and version control integration as well as dependencies and parametrizations.
API Life-cycle management
and CI/CD Pipeline integration
The APIIDA API Gateway Manager together with the central IT management allows to integrate with pipeline managers such as git runners, puppet or jenkins, version control systems such as github or Bitbucket. It covers regression control. There is also the possibility of automating the pipeline.
Separation of Duties
and Concerns
Depending on the group structure of the organization and the needs and requirements of the business units, it is possible to give separate duties to different bodies of the organization to help work together with the change management process and have different authorization levels.
Continuous Health Check
and Advocacy
The APIIDA API Gateway Manager is able to show the Operations team discrepancies between environments, making sure that all the gateways in an environment has consistent services and policies and dependencies. It also allows to check if there are any expired certificates or keys, and if there are any open insecure connections.
Operations
Automation
The APIIDA API Gateway Manager has a list of APIs that enables automatic interaction with event driven tools, that can trigger actions such as migrations or regression actions. Moreover, any alarms can be configured to hook up to messaging platforms such as slack and teams or even emails; also, it can interface with agile tools such as Jira to create tasks or tickets automatically and assign them, automating a big part of the Operations part.
APIIDA
Expert Services
With this APIIDA Expert Services package, implementing CI/CD pipeline flows with Broadcom Layer7 and the APIIDA API Gateway Manager becomes a breeze.
Our pre-defined integrations and expertise in the field ensure a seamless integration that is tailored to your specific needs. From strategy to execution, we work with you every step of the way to guarantee a completely integrated and secure API management solution. Trust APIIDA to provide expert services that deliver results.
What’s in for your business?
The Benefits
Drive Speed to Innovation
Get to market faster and seize new business opportunities by managing your API services with fast, easy, and reliable migration across your environments for development, test, and production.
Automate DevOps Processes
Enhance the Developer Experience with CI/CD pipeline automation and integration with testing means, combined with an easy and comprehensive service categorization and version control.
Reduce Costs
Reduced Cost by shorten the time of an idea and the business service with automation and an improved developer experience by reducing operational tasks, so you can focus on initiative tasks.
The Solution at a High Level
We accept that all environments are different so the solution depicted here is meant to give a generic high level view of what a possible setup can be. At the core of it all there is the APIIDA API Gateway Manager, AAGM in short, which is meant to be the central point of contact for the CI/CD pipeline. On one side you have the Layer7 API Gateways, divided in their own environments, and the challenge is to be able to, in a sustainable, repeatable and persistent way, migrate services and components from one environment to the other, all the while maintaining an audit trail of the migration, a means to version control, and regress in case of issues. In this simple example below, the CI/CD pipeline is divided in two sections for agile purposes: one is when a developer is ready to tag and upload to the version control. The other section is about pushing the version controlled resource from the point of truth, which is the Version Control System to the next environment.
Part 1
Developer is ready with their development and wants to record the change.
1. They would use Jenkins jobs to call APIs on AAGM to migrate the resource (API or dependency)
2. AAGM scans the Gateway on Environment 1 to get the latest version of the resource with all its dependencies.
3. AAGM will apply any rules to the resource, such as variable changes, mappings, library checking.
4. AAGM will tag and push the version to the Version Control system (such as Bitbucket or Github).
1. They would use Jenkins jobs to call APIs on AAGM to migrate the resource (API or dependency)
2. AAGM scans the Gateway on Environment 1 to get the latest version of the resource with all its dependencies.
3. AAGM will apply any rules to the resource, such as variable changes, mappings, library checking.
4. AAGM will tag and push the version to the Version Control system (such as Bitbucket or Github).
Part 2
API Owner is ready to push the version in the VCS to the next environment.
1. API owner kicks off the the Jenkins job which calls the appropriate APIs of the AAGM to trigger the migration.
2. AAGM will retrieve the information from the repository (the right tag or branch).
3. AAGM will apply any mappings or changes to the bundle.
4. AAGM pushes the bundle to the Gateway on the next environment (Environment 2 in this image) and can trigger tests to see if the service works as required.
If it does not, it can revert the migration.
1. API owner kicks off the the Jenkins job which calls the appropriate APIs of the AAGM to trigger the migration.
2. AAGM will retrieve the information from the repository (the right tag or branch).
3. AAGM will apply any mappings or changes to the bundle.
4. AAGM pushes the bundle to the Gateway on the next environment (Environment 2 in this image) and can trigger tests to see if the service works as required.
If it does not, it can revert the migration.
Each one of these steps are audited and recorded, and the state of the service can be monitored via Prometheus-stored statistics which are also visible directly on the AAGM dashboard for that service.
