CICD has become a widely adopted practice now a days. Automating both infrastructure deployments and artefact deployments has been a main focus point in almost all the projects in the industry these days. There are so many automation tools out there. But in this article I will use a Gitlab CICD Pipeline.
In this article Im going to explain how we can automate API deployment for a WSO2 API Manager. WSO2 API Manager provides a very sophisticated tool called APICTL to perform all API deployment related activities. …
AWS has two major offerings for deploying containers. EKS and ECS. EKS is the k8s based one and ECS has two options, EC2 based or Fargate. Due to the advantages and features, some people prefer to use ECS Fargate.
In this article Im going to explain how we can deploy a WSO2 API Manager 4.0.0 all in one HA(active-active) Cluster in ECS Fargate.
For more information on the deployment, please refer to following WSO2 official documentation
Following are the high level steps
This is the 4th post of a series of posts about Automating a WSO2 deployment using Azure Devops pipelines. Links to all the posts can be found in the bottom of this article.
In this post Im going to explain how did we develop a CI/CD pipeline to deploy Carbon Applications(.car files) to a WSO2 EI deployment in an Openshift cluster. We used maven car deploy plugin to deploy the .car files.
These are Maven Multi Module projects. Which contained a config project, a registry resources project, a composite application project as sub projects.
I will post the whole pipeline…
This is the 3rd post of a series of posts about Automating a WSO2 deployment using Azure Devops pipelines. Links to all the posts can be found in the bottom of this article.
In this post Im going to explain how we automated a WSO2 deployment in an Openshift cluster. The same pipeline can be used even for a WSO2 deployment in a Kubernetes cluster, by only changing the ‘oc’ commands to ‘kubectl’ commands.
We used WSO2 Official Kubernetes artefacts and parameterised them according to our need.
Enterprise Integrator — https://github.com/wso2/kubernetes-ei/tree/6.4.x/
Below is the directory/file structure…
This is the 2nd post of a series of posts about Automating a WSO2 deployment using Azure Devops pipelines. Links to all the posts can be found in the bottom of this article.
In this post Im going to talk about how to write pipelines in Azure Devops for a WSO2 deployment.
As I mentioned in my previous post, we had repositories for each wso2 product to build docker images. We could have used docker images from wso2 official docker registry and use those images as base images and create our own images. Customer preferred the other way which is…
Bit of a background here. There was a WSO2 deployment where all deployment related stuff including product upgrades and artefact upgrades were done manually. I was assigned to automate the whole Deployment process.
The deployment was on an OpenShift cluster which was in house(on premise) and as the CI/CD tool/solution, customer had chosen Azure Devops. After completing this task, Azure Devops became one of my favourites(I would say the most favourite) in CI/CD domain. Thing that I loved most about Azure devops is, its documentation. Very informative and comprehensive. And at the same time simple and easy to learn.
The new configuration model based on the toml format is introduced from API Manager 3.0.0 onwards. In older versions of the product, users had to modify different configuration files depending on the components related to the specific feature they were configuring.
With new configuration model all configuration files have been merged to make configurations easier. Therefore, the
<API-M_HOME>/repository/conf/deployment.toml file is the single source used to configure and tune the various features in API Manager.
You can follow below documentation to understand the configuration parameters that can be used in deployment.toml file.
But IMHO, this documentation doesn’t cover everything. Even though…
Have you ever wanted a simple Kubernetes cluster to try things out ? Or just to get familiar with kubernetes components, commands and other stuff ? Basically, have you ever wanted a Kubernetes Playground ?
But as far as I found, there are limitations with those options. …
Usually APIs are secured using some kind of protocol. More commonly using OAuth these days.
What if you or your company as a API provider, want to expose an API(or particular API resource in a given API) which doesnt need authentication.
Which means its an Open API / Public API
This is how we can accomplish it using WSO2 API Manager.
To make an API open , In WSO2 API Manager we need to disable oauth protection for all the resources in API, in the Manage section while publishing the API.
Start creating an api, go up to Manage…
Here in this article Im going to describe how we can add basic auth authentication for a WSO2 Data Service.
We will be using wso2 developer studio(EI Tooling) for this task.
I have following project in my EI Tooling (Developer Studio). And I have my dataservice called test.dbs
When I deploy it, It will be like below. Unsecured.