<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kuldeep Bhati on Medium]]></title>
        <description><![CDATA[Stories by Kuldeep Bhati on Medium]]></description>
        <link>https://medium.com/@kuldeepbhati?source=rss-1f150b0dc47e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ijDMjIyxz-0Cg9QpE4P9Og.jpeg</url>
            <title>Stories by Kuldeep Bhati on Medium</title>
            <link>https://medium.com/@kuldeepbhati?source=rss-1f150b0dc47e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:26:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kuldeepbhati/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Automate Apigee Hybrid — Control Plane Provisioning]]></title>
            <link>https://medium.com/apigeek/automate-apigee-hybrid-control-plane-provisioning-a9f487197a9f?source=rss-1f150b0dc47e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9f487197a9f</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[apigee-installation]]></category>
            <category><![CDATA[apigee-hybrid]]></category>
            <category><![CDATA[apigee]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Kuldeep Bhati]]></dc:creator>
            <pubDate>Tue, 22 Feb 2022 23:04:19 GMT</pubDate>
            <atom:updated>2022-02-22T23:15:57.561Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automate Apigee Hybrid — Control Plane Provisioning</h3><h4>Ready to use Terraform scripts to automate the Control Plane Provisioning</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/0*k1dTf_rpX_yedvwh.png" /><figcaption>Credit: Google Apigee — <a href="https://cloud.google.com/apigee/docs/hybrid/v1.6/what-is-hybrid">https://cloud.google.com/apigee/docs/hybrid/v1.6/what-is-hybrid</a></figcaption></figure><p>Hello and welcome.</p><p>Apigee Hybrid is a platform for developing and managing API proxies that features a hybrid deployment model.</p><p>Apigee Hybrid deployment consists of 2 steps</p><ol><li>Provisioning Control Plane</li><li>Install the Runtime Plane</li></ol><p>This post focuses on the Step 1 — Provisioning Control Plane. I have created this repository — <a href="https://github.com/bhatikuldeep/apigee-hybrid-x-provision"><strong>https://github.com/bhatikuldeep/apigee-hybrid-x-provision</strong></a> that contains the terraform scripts — that will help you to provision the Apigee Hybrid — Control Plane.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9f487197a9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apigeek/automate-apigee-hybrid-control-plane-provisioning-a9f487197a9f">Automate Apigee Hybrid — Control Plane Provisioning</a> was originally published in <a href="https://medium.com/apigeek">apigeek</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mulesoft Automate Deployment]]></title>
            <link>https://medium.com/apigeek/mulesoft-automate-deployment-45cfc66c6d9f?source=rss-1f150b0dc47e------2</link>
            <guid isPermaLink="false">https://medium.com/p/45cfc66c6d9f</guid>
            <category><![CDATA[bitbucket-pipelines]]></category>
            <category><![CDATA[mulesoft-esb]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Kuldeep Bhati]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 00:37:05 GMT</pubDate>
            <atom:updated>2021-03-11T08:58:31.575Z</atom:updated>
            <content:encoded><![CDATA[<h3>MuleSoft Automate Deployment</h3><h4>Deploy Mule Applications to CloudHub using the Mule Maven Plugin and Bitbucket Pipelines</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YwhdzioPGhNrdJxk" /><figcaption>Credit: Atlasssian (BitBucket)</figcaption></figure><p>Hello and welcome. In this post I will explain how to automate MuleSoft Application deployment to CloudHub using Mule Maven Plugin and Bitbucket Pipeline.</p><h3>Prerequisite</h3><ul><li>MuleSoft CloudHub Account</li><li>Bitbucket Atlasssian Account — for code repository.</li><li>If you are using the HTTP Listener as source for your flow, you need to set its host to 0.0.0.0 and its port to ${http.port}</li><li>Declare all external classes and resources in the exportedPackages and exportedResources fields on the mule-artifact.jsonfile.</li></ul><h4>Project Structure</h4><p>Pipeline file should have the name — bitbucket-pipelines.yml. It should be at repository root-level as described below in a sample project structure. Once it is defined at the root-level, Bitbucket will automatically pick-up any changes to the code commit and will start to run the pipeline.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d68ef870bc829107bc19d113f7c2658/href">https://medium.com/media/1d68ef870bc829107bc19d113f7c2658/href</a></iframe><h3>Pipeline Stages</h3><ol><li>Git Security Scan</li><li>Validate &amp; Compile</li><li>Test</li><li>Deploy to Sandbox CloudHub</li></ol><blockquote>Alright, a big question — how to integrate this pipeline to a MuleSoft Project? Let’s check this out in the next section.</blockquote><h3>How to integrate pipeline to your own MuleSoft Project</h3><ol><li><strong>Update pom.xml: </strong>open pom.xml — plugin element: Inside the plugin element in your project’s pom.xml file, search for plugin section with <em>mule-maven-plugin</em> artifactIdand<strong><em> replace</em></strong> the below pluginplaceholder.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d490335d2bbd40c5091b616b7c86803d/href">https://medium.com/media/d490335d2bbd40c5091b616b7c86803d/href</a></iframe><p>2. <strong>Create Variable References in Bitbucket:</strong> In step 1, as you can see, we are using pipeline variables e.g. — {MULESOFT_ENVIRONMENT} . These pipeline variables are convenient as you can set these once and reuse in your pipeline at build time.</p><ul><li>So let’s create Workspace Variablesas described below;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lUuN3tuP2Uzvp2gWZgnN9A.png" /><figcaption>Bitbucket Workspace Variables</figcaption></figure><blockquote>The reason we’re using <em>Workspace Variables</em> is for the reusability. Once defined, can be reused within the workspace, i.e. for all repository; so you don’t have to create these variables for each and every repository within the workspace.</blockquote><blockquote>We’re usingMULESOFT_USERNAME and MULESOFT_PASSWORD variables as secured . Bitbucket supports variables stored as secured so it’s value is hidden and not visible in the variables list and in the build logs. Secure variables are stored as encrypted values.</blockquote><ul><li>Next, Let’s create Deployment Variables ; these variables can only be used in a specific deployment environment. We will set MULESOFT_ENVIRONMENT variables with the value of a deployment environment in your MuleSoft CloudHub, e.g. Sandbox</li></ul><blockquote>Ensure that the pipeline is enabled before creating Deployment Variables</blockquote><ul><li>Change the Test environment name to Sandbox ; [we’re going to use CloudHub’s Sandbox environment, you can use the one that’s available]</li><li>Under Variables section for the Sandbox environment, create MULESOFT_ENVIRONMENT variable with value Sandbox</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*GAO6d7FeswqqTwz07QBL-Q.png" /><figcaption>Bitbucket — Repository Deployment variables</figcaption></figure><p>For more details about Bitbucket variables, you can visit — <a href="https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/">https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/</a></p><p>3. Create bitbucket-pipelines.yml as described below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4e66935380c8a839709d3137e5471c8/href">https://medium.com/media/f4e66935380c8a839709d3137e5471c8/href</a></iframe><p>4. that’s it basically, all done.</p><p>5. Push the code to your remote master branch — and Bitbucket will trigger the deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yJP0uSsOyBpNm5d4sfTqw.png" /><figcaption>Successful Deployment — BitBucket pipeline (y)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RcCxmq0iBpK6BPEekLJrbQ.png" /><figcaption>Successful Deployment — CloudHub logs (y)</figcaption></figure><h3>Demo Project</h3><p>Remember — the objective is to deploy the application to CloudHub. I have used a sample MuleSoft Application — with a Listener that returns a “Hello World!” JSON response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/238/1*ReeeeWLGCld0MXkuQ8bZEQ.png" /><figcaption>Mule Application — Listener returns a simple “Hello World!” message.</figcaption></figure><blockquote>You can use this repository included with pipeline configurations here — <a href="https://bitbucket.org/kuldeepbhati/cloud-hub-deploy/src/master/">https://bitbucket.org/kuldeepbhati/cloud-hub-deploy/src/master/</a></blockquote><h3>Common Issues</h3><ul><li>4.3.0–20210119 is not a valid value for muleVersion.version.</li></ul><pre>Caused by: org.mule.tools.client.core.exception.ClientException: 400 Bad Request: {“status”:400,”message”:”4.3.0–20210119 is not a valid value for muleVersion.version.”}</pre><blockquote>If you get this error; this is due to the incorrect &lt;app.runtime&gt;4.3.0–20210119&lt;/app.runtime&gt; in your pom.xml file. Correct it as <em>&lt;app.runtime&gt;4.3.0&lt;/app.runtime&gt;</em></blockquote><h3>Important Notes</h3><ul><li>We’re using a single environment in this pipeline — that’s Sandbox . You can always extend this pipeline and use as many upstream environments as it pleases you.</li><li>Ensure that you have correct environment naming across — bitbucket-pipelines.yml , Deployment Variables and your CloudHub environment name.</li><li>You may have noticed, that we’re using MULESOFT_USERNAME and MULESOFT_PASSWORD variables for deployment; although these are stored as secured and not visible in the variables list and also not in build logs, it is advised to use Connected App functionality, please visit this link for more information — <a href="https://help.mulesoft.com/s/article/How-to-deploy-an-application-to-Cloudhub-using-Connected-App-functionality">https://help.mulesoft.com/s/article/How-to-deploy-an-application-to-Cloudhub-using-Connected-App-functionality</a></li><li>We have not introduced any branching model in this post; so If you push code from any branch; the deployment will be triggered. You can use this link to configure branch specific deployment — <a href="https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/">https://support.atlassian.com/bitbucket-cloud/docs/pipeline-triggers/</a></li><li>As of now; we kept this pipeline very simple; if there’s need for using Mule EE repositories you would need to create a Maven settings.xml file that will have Mule EE username and password . You can use this post — <a href="https://medium.com/@chris.shellenbarger/continuous-integration-a-complete-guide-to-using-bitbucket-pipelines-with-maven-repositories-e835bd0f5f11">https://medium.com/@chris.shellenbarger/continuous-integration-a-complete-guide-to-using-bitbucket-pipelines-with-maven-repositories-e835bd0f5f11</a> that describes how to achieve that. Please leave a comment below if you need any help.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45cfc66c6d9f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apigeek/mulesoft-automate-deployment-45cfc66c6d9f">Mulesoft Automate Deployment</a> was originally published in <a href="https://medium.com/apigeek">apigeek</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apigee Edge— Proxy Template Generator (with maven archtype)]]></title>
            <link>https://medium.com/apigeek/apigee-edge-proxy-template-generator-with-maven-archtype-6daf14dbe3ee?source=rss-1f150b0dc47e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6daf14dbe3ee</guid>
            <category><![CDATA[apigee-proxy]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[api-development]]></category>
            <category><![CDATA[maven]]></category>
            <category><![CDATA[apigee]]></category>
            <dc:creator><![CDATA[Kuldeep Bhati]]></dc:creator>
            <pubDate>Thu, 02 May 2019 12:43:07 GMT</pubDate>
            <atom:updated>2019-05-02T12:43:07.393Z</atom:updated>
            <content:encoded><![CDATA[<p>A custom maven archetype to generate a sample Apigee Edge compatible API Proxy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqi9uQTKSaNawJIMAT48Ag.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@rawpixel?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">rawpixel.com</a> from <a href="https://www.pexels.com/photo/achievement-adult-agreement-arms-1153213/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h4>What?</h4><p>It is a custom maven archetype to generate a sample Apigee Edge compatible API Proxy.</p><p>This is an effort to automate Apigee Edge proxy generation — with custom maven archtype. Use this project to create an Apigee Edge proxy skeleton.</p><p>Github repo link — <a href="https://github.com/bhatikuldeep/maven-archetype-apigee-proxy">https://github.com/bhatikuldeep/maven-archetype-apigee-proxy</a></p><h4>Why?</h4><p>There are quite some flavours of apigee edge proxy generator; just to make clear I am not reinventing the wheel :) however, somehow was missing that easiest way to scaffold an api proxy which is compatible with <a href="https://github.com/apigee/apigee-deploy-maven-plugin">apigee-deploy-maven-plugin</a>. In addition to make it compatible I have also added sample postman/newman tests case templates ready to use.</p><p>Use this project to create a Apigee edge proxy skeleton, you can create and upload a sample proxy in few steps.</p><p>Feel free to post any issue/questions/feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6daf14dbe3ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apigeek/apigee-edge-proxy-template-generator-with-maven-archtype-6daf14dbe3ee">Apigee Edge— Proxy Template Generator (with maven archtype)</a> was originally published in <a href="https://medium.com/apigeek">apigeek</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Message Logging made easy with Apigee Edge]]></title>
            <link>https://medium.com/apigeek/message-logging-made-easy-with-apigee-edge-1e3b10860304?source=rss-1f150b0dc47e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e3b10860304</guid>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[loggly]]></category>
            <category><![CDATA[apigee]]></category>
            <category><![CDATA[messagelogging]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <dc:creator><![CDATA[Kuldeep Bhati]]></dc:creator>
            <pubDate>Sun, 07 Apr 2019 23:41:25 GMT</pubDate>
            <atom:updated>2019-04-07T23:41:25.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-ft98hQL4aWhAYSA9dfEg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@olly?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">bruce mars</a> from <a href="https://www.pexels.com/photo/man-in-white-dress-shirt-sitting-on-black-rolling-chair-while-facing-black-computer-set-and-smiling-840996/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>In this post, I have tried to cover most common external <strong>message logging system </strong>with Google’s API Management — <a href="https://medium.com/u/c04d3991e342">Apigee</a> Edge. At the end of the post you can find link to the code repository that you can use.</p><p>Okay, so let’s get started.</p><p>Apigee Edge offers a seamless syslog integration to external logging systems like Loggly, Splunk, SumoLogic etc. to log your API requests. However, you can also send logs to ELK (Elasticsearch, Logstash and Kibana) stack.</p><blockquote>Although sending logs to Loggly is straight-forward by implementing out-of-the-box <a href="https://docs.apigee.com/api-platform/reference/policies/message-logging-policy">Message Logging Policy</a>, however it is little bit challenging when integrating with ELK stack (Elasticsearch, Logstash and Kibana), especially sending JSON log messages to the ELK stack.</blockquote><p>I have put some efforts in this and tried my best to cover both the <strong><em>ELK stack (Part 1)</em></strong> and <strong><em>Loggly (Part 2) logging</em></strong> in this post.</p><blockquote>The sole objective of creating these repositories is to help Apigee developers QuickStart external logging with as less configurations as possible.</blockquote><h3>Why?</h3><p>Logs are quite important to track down issues in API runtime environments. Logs can be useful for developers during and after the development phase, especially because they are the ones writing the code and configuring the APIs. Also, it is important for security teams to see if there has been any unauthenticated/unauthorised API access; logging gives the security team all the information they need.</p><p>Apigee Edge offers a 10 min or 20 messages trace window (whichever reaches first), so you can trace the live calls to find the issues or capture messages during development to see whether runtime properties are being set properly or not, for e.g. quota counter for a developer app . However that is not sufficient when the API call was made outside of this trace session. You are helpless if you don’t have the logs. Having an Apigee Private Cloud/On-premise subscription, you have full access to the logs, however having Apigee Edge Public Cloud subscription you do not have access to the logs. So if you happen to be a Public Cloud Customer, <strong>it is highly recommended</strong> to use either your own premise ELK stack or a third-party log management services like Loggly to have full and complete insights in your APIs.</p><h3>How?</h3><p>I have created two git repositories (see Part 1 and Part 2), both contain a working demo/api proxy which demonstrates logging to Loggly (Formatted JSON) and ELK Logging.</p><h4>Part 1</h4><p><strong><em>Apigee Edge — External Message Logging to ELK stack</em></strong><em><br></em>Repo Link — <a href="https://github.com/bhatikuldeep/hello-world-elk-logging">https://github.com/bhatikuldeep/hello-world-elk-logging</a></p><h4>Part 2</h4><p><strong><em>Apigee Edge — External Message Logging to Loggly<br></em></strong>Repo Link — <a href="https://github.com/bhatikuldeep/hello-world-loggly-logging">https://github.com/bhatikuldeep/hello-world-loggly-logging</a></p><p>I have tried my best to cover what is essential, however if there’s any support required, feel free to contact me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e3b10860304" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apigeek/message-logging-made-easy-with-apigee-edge-1e3b10860304">Message Logging made easy with Apigee Edge</a> was originally published in <a href="https://medium.com/apigeek">apigeek</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>