<?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 Ashish Kamat on Medium]]></title>
        <description><![CDATA[Stories by Ashish Kamat on Medium]]></description>
        <link>https://medium.com/@ashishkamat27?source=rss-36936ba363c2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Ashish Kamat on Medium</title>
            <link>https://medium.com/@ashishkamat27?source=rss-36936ba363c2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:42:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashishkamat27/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[Building a Neural Highway: How OmniRoute Became My IDE’s Central Nervous System]]></title>
            <link>https://medium.com/@ashishkamat27/building-a-neural-highway-how-omniroute-became-my-ides-central-nervous-system-acceea93cc36?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/acceea93cc36</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[context-engineering]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 05:31:01 GMT</pubDate>
            <atom:updated>2026-08-14T05:31:01.516Z</atom:updated>
            <content:encoded><![CDATA[<p>It was 5:30 PM wednesday evening , and I was in that rare, flow-state high every dev lives for. The terminal was flying, my refactor was coming together, just few changes were pending before I am about to push my changes to review, my Claude coding assistant was nailing every context-heavy suggestion.</p><p>Then came the dreaded toast notification:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/0*5yYCqRE_NAHLF2Yv" /></figure><p>My 5-hour Anthropic window had burned out.</p><p>I stopped typing, opened my config, swapped environment variables to point to a personal OpenAI key, and hit run. Boom — conversation context wiped clean. I had to feed it my code structure all over again, burning $1.20 on a single prompt replay. Twenty minutes later, OpenAI hit a transient 503 outage, and my flow state died right there on the spot.</p><p>If you are vibe coding and building and/or using AI tools like <strong>Cursor, Claude Code, OpenClaw, Cline, or Codex</strong>, you know this dance:</p><ul><li>Subscriptions choke on arbitrary usage caps mid-thought.</li><li>Your tools live in isolated silos — Claude Code won’t talk to OpenAI, and Codex won’t touch Anthropic.</li><li>Upstream provider outages instantly brick your local dev environment.</li><li>Token costs explode because every single hit resends massive git diffs, build logs, and system prompts.</li></ul><p>That night, I decided I was done playing babysitter to API limits. I set out to build a resilient, fail-proof local setup — and that’s when I stumbled onto <strong>OmniRoute</strong>.</p><h3>What it is ?</h3><p><a href="https://omniroute.online/"><strong>OmniRoute</strong></a> is a free, open-source AI gateway that sits quietly on your machine between your local dev tools and upstream providers.</p><p>Instead of juggling a web of separate keys, configs, and endpoints across every IDE extension or terminal tool, you point everything to a single local base URL:</p><pre>http://localhost:20128/v1</pre><p>Under the hood, OmniRoute pools all your subscription accounts, API keys, and free tiers into one dynamic pipeline. It handles intelligent routing, silent failovers, and prompt compression locally before a single byte leaves your machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RgTyAOP17SfvHRaIqJO5eg.png" /></figure><h3>Why This Setup Reclaimed My Dev Workflow</h3><h4>1. Zero-Downtime 4-Tier Auto-Fallback</h4><p>OmniRoute organizes your provider access into a <strong>4-Tier Fallback Chain</strong>:</p><ol><li><strong>Tier 1: Subscription Accounts</strong> (Claude Pro, Codex Plus, GitHub Copilot, Gemini CLI)</li><li><strong>Tier 2: Paid API Keys</strong> (Anthropic, OpenAI, DeepSeek, Groq)</li><li><strong>Tier 3: High-Throughput / Low-Cost Providers</strong> (OpenRouter, Together, Fireworks)</li><li><strong>Tier 4: Free-Tier Gateways</strong> (90+ free options like Pollinations, Kiro, Qoder, LongCat)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/0*qhWKhGX2y8BCDlev" /></figure><h4>2. Built-in Prompt Compression (Save 15%–75% Token Spend)</h4><p>It ships with a 5-mode prompt compression engine (from <em>Lite</em> to <em>Standard/Caveman</em>, <em>Aggressive</em>, and <em>Ultra</em>). It strips out fluff, redundant whitespace, and repetitive system messages on the fly — drastically slashing token consumption when feeding massive codebases into paid APIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/0*tiLuf5GdCHxZhfCP" /></figure><h4>3. Context Relay</h4><p>Normally, switching models mid-session erases your thread context. OmniRoute’s <strong>Context Relay</strong> creates a compact summary during rotations, injecting it as a system prompt to the new provider so your session stays intact.</p><h4>4. Protocol Translation Across 160+ Providers</h4><p>Whether a provider uses OpenAI Chat Completions, Anthropic Messages API, Gemini’s schema, or Codex’s Responses API, OmniRoute translates payload formats back and forth on the fly.</p><h3>Setup Guide</h3><p><strong>Step 1: Fire Up the Gateway</strong></p><p>Run OmniRoute locally using NPM or Docker.</p><p><strong>Via NPM:</strong></p><pre>npm install -g omniroute<br>omniroute</pre><p><strong>Via Docker:</strong></p><pre>docker run -d \<br>  -p 20128:20128 \<br>  -v omniroute-data:/app/data \<br>  --name omniroute \<br>  diegosouzapw/omniroute:latest</pre><p>Open http://localhost:20128 in your browser to launch the dashboard.</p><p>once you run/install dashboard in any of the way mentioned in Step 1, you will get dashboad like this</p><p>Follow along steps</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUBKneQtvqOhjwe9xBHS-A.png" /></figure><p>add your primary AI provider with API keys here (I also added Claude later and then Kiro as free tool to test Combo)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*80xl7BGmU_tBTv7IztYKTQ.png" /></figure><p>along with primary provider you will get all other provider for various operations and tools call with integrated MCP server inside dashboard</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JiaMRPBkaD1IyMqssvDQg.png" /></figure><p>Like Image/Video/Audio provider integration all in one place</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ROg3RCQ_1z3zzFVc9CTYA.png" /></figure><p><strong>Step 2: Build Config routing stack</strong></p><p>Inside the dashboard:</p><ol><li>Navigate to <strong>Providers</strong> and toggle on your active accounts (Claude OAuth, OpenAI API, Kiro, etc.).</li><li>Go to <strong>Combos</strong> and create a routing rule named coding-stack.</li></ol><p>A combo is a chain of models OmniRoute routes across automatically. Quota runs out, a provider fails, or costs spike — the combo silently slides to the next model. This is what makes OmniRoute unbreakable. 🛡️</p><p>Here is wizard for combo to set</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gQ26VzX78UEcL9doBqfD4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpELlD3Aa5ohW3dWEoVR9A.png" /></figure><p>By default routing and selecting fallback model is auto mode, However we can select any on 19 combo to customized how our fallback model selection should work based on our requirement</p><p>YOu can select any of strategies which best worked for you as follows</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cbrgioNwYwjXLkV12y4k8w.png" /></figure><p>Refer: <a href="https://github.com/diegosouzapw/OmniRoute/blob/release/v3.8.50/README.md#-or-build-your-own--19-routing-strategies">https://github.com/diegosouzapw/OmniRoute/blob/release/v3.8.50/README.md#-or-build-your-own--19-routing-strategies</a></p><p>Here is how my provider topology diagram looks like (combied OpenAI, Claude, Kiro with opencode/vscode as IDE)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzf0PkQW7TQWMMH2ncX1Xw.png" /></figure><p><strong>Step 3: Wire Up Your Local Tools</strong></p><p>Reconfigure your workspace tools to point to your new local gateway endpoint.</p><p>You will need to create Omniroute API key on dashboard to use this endpoint as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsGAfLOMj0PAMf0Dw0lc0g.png" /></figure><p>Here is how I configure for claude in vscode</p><blockquote>below is sample project having custom <strong>settings.local.json</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOxEQOlKxYU8sRBPKetFdQ.png" /></figure><p>and let me run claude CLI here. you can see its loading model as auto/best-free (Warnings on top can be ignored)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xct7YLKxckxsRfheAPrd0Q.png" /></figure><p>Lets test with actual query like How is waeather today in Bengaluru ?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0RSx4tQhNiMuobdku0SVog.png" /></figure><p>As you noticed instead of using model like Opus, Sonnet, Fabel etc. its used Ominroute API gatway route and able to answer queries</p><h3><strong>What next ?</strong></h3><p>It also provided many more features like which you can explore like :</p><ul><li>built in MCP server to use with any AI tools/ Agents</li><li>Cost and Budgeting Analytics dashboards</li><li>A2A protocol for agent communication</li><li>Agentic features like Memory, Agentic bridge, Chaos mode, A2A server etc.</li><li>Observabilty built in</li><li>LLM evaluation and playground</li><li>Smart Compression using RTK and Caveman</li><li>etc</li></ul><p>I will try to cover more on this in next blog</p><h3>FAQ &amp; Final Thoughts</h3><ol><li><strong>Is it enterprise-ready?</strong></li></ol><p><strong>No</strong>, at present not,its I can say we need to still evaluate more on ths, it has bugs, reliance on open models rather than frontier models, and suitability limited only to personal projects at presnt, but good open source support and worrth to try out.</p><p><strong>2. Is it secure?</strong></p><p><strong>Not that much</strong>, it has security concerns, as testing triggered Google security alerts and raised risks around handling sensitive data reported by few users.</p><p><strong>3</strong>. <strong>Response time ?</strong></p><p>Little slow compared to actual model calls due to API gateway in between which is little obvious but sometimes it takes more than usual since tool is new.</p><p>So try this out this tool, and share your experience.</p><p>Happy vibe coding !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acceea93cc36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kagent: Agentic AI for Kubernetes (AI meets cloudnative)]]></title>
            <link>https://medium.com/@ashishkamat27/kagent-agenetic-ai-for-kubernetes-8ad778c2eb81?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ad778c2eb81</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[ai-reliability]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Sun, 25 May 2025 18:50:55 GMT</pubDate>
            <atom:updated>2025-05-30T02:01:29.526Z</atom:updated>
            <content:encoded><![CDATA[<p>In the era of Artificial Intelligence, Generative AI, Large Language models and yes new buzz word <strong>Agentic AI</strong> and to support it new protocols (or again Buzz Word) have been launched called Model Context Protocol a.k.a <strong>MCP</strong> or MCP Servers.</p><p>In this blog we will be focusing on How agentic ai can help Platform Engineers and DevOps Professional especially for those who works on <strong>cloud native</strong> platform and especially on <strong>Kubernetes </strong>environments.</p><p>Lets begin with newly launched Open Source agentic AI framework <a href="https://kagent.dev/"><strong>Kagent</strong></a>, from <a href="https://www.solo.io/">Solo.io</a> for DevOps and platform engineers to run AI agents in Kubernetes, automating complex operations and troubleshooting tasks.</p><p>We will be covering more on this in following manner:</p><ol><li>What is Kagent</li><li>Installation steps</li><li>Integration with Open AI/LLama or any LLM model</li><li>Agents and interaction Demo</li><li>Future Scope</li></ol><h3>1. What is Kagent</h3><ul><li>Its is an open-source programming framework that brings the power of agentic AI to cloud-native environments.</li><li>Built specifically for DevOps and platform engineers,</li><li>Enables AI agents to run directly in Kubernetes clusters to automate operations, troubleshoot issues, and solve complex cloud-native challenges.</li></ul><h3>2. Installation</h3><p>Kagent on kubernetes cluster can be installed in many ways.<br>Here on minikube clusters we have done in following ways as suggested in documentation</p><p><strong>Option 1 using curl and bash script</strong></p><pre># Download/run the install script<br>curl https://raw.githubusercontent.com/kagent-dev/kagent/refs/heads/main/scripts/get-kagent | bash</pre><p>other ways of installation:</p><p><strong>Option 2 Helm ways</strong></p><pre>helm install kagent-crds oci://ghcr.io/kagent-dev/kagent/helm/kagent-crds --namespace kagent --create-namespace<br>helm install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent --namespace kagent --values values.yaml</pre><p>Here for this blog I have installed using <strong>Option 1.</strong><br>It also gives command-line inteface to interact with kubernetes cluster as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8oojcnYsJzG7wo--djUmA.png" /></figure><h3>3. Integration with LLM</h3><p>Here for simplicity purpose I have used <strong>Open AI API Key</strong> but you can integrate later with any other models</p><p>To interact with Open AI you will need Open AI API key to be exported (Note: this will have limitations in terms of tokens and may give you rate limit error )</p><p>Here are steps to get your key:<br>1. Go to <a href="https://platform.openai.com/">https://platform.openai.com/</a> and Do Login/SignUp</p><p>2. Go to your profile and click on API keys</p><p>3. Specify Key Name and Select project</p><p>Refer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lq_NLEttFpXHLI2LVsmWAg.png" /></figure><p>Once you get the key export and run kagent install as follows:</p><pre>export OPENAI_API_KEY=&quot;your-api-key-here&quot;<br>kagent install</pre><p>If everything goes well after running kagent will give prompt shown above:</p><p>run kagent (or in kagent prompt just get agent)</p><pre>Welcome to kagent CLI. Type &#39;help&#39; to see available commands.<br>kagent &gt;&gt; get agent<br>+---+--------------------------------+----+----------------------------+<br>| # | NAME                           | ID | CREATED                    |<br>+---+--------------------------------+----+----------------------------+<br>| 1 | k8s-agent                      | 8  | 2025-05-25T07:05:05.560862 |<br>| 2 | argo-rollouts-conversion-agent | 7  | 2025-05-25T07:05:05.500932 |<br>| 3 | istio-agent                    | 6  | 2025-05-25T07:05:05.463344 |<br>| 4 | promql-agent                   | 5  | 2025-05-25T07:05:05.386848 |<br>| 5 | helm-agent                     | 4  | 2025-05-25T07:05:05.350318 |<br>| 6 | observability-agent            | 3  | 2025-05-25T07:05:05.288692 |<br>| 7 | cilium-crd-agent               | 9  | 2025-05-25T07:05:05.220041 |<br>| 8 | kgateway-agent                 | 2  | 2025-05-25T07:05:05.182235 |<br>| 9 | RoundRobin Team                | 1  | 2025-05-25T07:05:02.983488 |<br>+---+--------------------------------+----+----------------------------+</pre><p>running kagent dashboard (or inside kagent CLI just dashboard), will give UI as follows for first time</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pOmmUtCN07DkMbI0M2soGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NuXGWdDxKwgXn0tQ.png" /></figure><p><strong>A] LLM Model selection</strong></p><p>Since OPEN AI is selected It will get preference (but you will get choice of selections for other models as well)</p><p><strong>B] Agent Selection</strong><br>In this you will add the name, description, and system prompt that allows you to define the AI Agent Purpose.</p><p><em>Agents — “An AI agent is an application that can interact with users in natural language. Agents use LLMs to generate responses to user queries and can also execute actions on behalf of the user.”</em></p><p>refer (for creation of our custom agent we have selected k8s-agent and helm-agent which is already provided by kagent)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AF0f9VEH78e9HVdPiNkydA.png" /></figure><p><strong>C] Tools Selection</strong></p><p>It allows us to give the permission it needs to have on the kubernetes cluster. The Kubernetes API Permissions are listed there and it must be selected for the Agent to perform its duties.</p><p><em>Tools — “ Tools are functions that the agent can use to interact with its environment. For example, a Kubernetes agent might have tools for observabilty.</em></p><p>refer below (Eg helm agent have following list of Tools/functionalities which agent here helm-agent can do on our behalf , Eg GetRepositories, GetCharts, Install/deploy chart):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PPr1bda2g64q_8UfRl41Ww.png" /></figure><h3>4. Agents and interaction Demo</h3><p>Now our agent is ready lets test it out</p><p>Eg 1: As a user I want to see How many namespaces currently present and no of pods in each pods<br>(behind scene It is interacted with k8s-agent which I recently added in new my current agent configurations and return me result using avaialble tools configured for agents)</p><p>Below Screenshot for list of namespaces available in my cluster (here minikube)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lCRzqCeUwCKpeaby1L2XXA.png" /></figure><p>And here pods in each namespace</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DPijT8nAG4cu-_myrUPT1Q.png" /></figure><p>Lets test our agent if it can perform helm related operations or not (since new agent we created is capable of handling both of k8s and helm agent)</p><p>Eg 2: Now here I am telling agent to install observability stack (prometheus + grafana) in my current cluster</p><p>See How agent is handling intelligently and creating plan what to do as shown in below screenshots which includes</p><ul><li>adding reposistories (if not exist → helm repo add)</li><li>update repositories (to fetch latest helm charts from added repos → helm repo update)</li><li>install/upgrade those charts in monitoring namespace and create namespace also if not exit (helm upgrade &lt;chart-name&gt; &lt;repo-name&gt;)</li><li>confirm if its successfully deployed</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rYxzCxykxYlyjnn52Ov-vA.png" /></figure><p>And Voila! It actually happening in system without any user interventions</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VnftgrG-gTXuC3WYcyL8gg.png" /></figure><p>And good news! Its also predicted what can be my next queries and given commands before hand without even asking (ie accessing prometheus and grafana dashboards locally)<br>refer below screenshots</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WZwb-53N44525o3FOgbPGQ.png" /></figure><h3>5. Future Scope</h3><p>As you can see agentic AI is so powerful and making DevOps and Platform Engineers life much easier, but in future there is much wider scope for same <br>We can use of available MCP Servers and there tools, integrate with such agents (here Kagent) to let use AI especially agentic AI as much as possible in our daily life. I will cover more on this in my next blogs</p><p>Example includes:</p><ol><li>We can use to save our AWS cost by asking agent to create reports, identify trends and manage cost, provide recommendations and take actions on its own.</li><li>For observability dashboards, i.e identify pattern and trends in Logs and metrics, fix alerts by analysing and running runbooks, fix False alerts</li><li>Repository management which includes Code reviews, pipeline triggers, user access management, code fixes, static/dynamic code analysis, CI/CD</li><li>ArgoCD applications, rollouts and workflow management (update, delete, create etc).</li><li>Machine learning model EDA, trainings, developments and deployments.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ad778c2eb81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AIaC: Artificial Intelligence Infrastructure-as-Code Generator.]]></title>
            <link>https://medium.com/@ashishkamat27/aiac-artificial-intelligence-infrastructure-as-code-generator-8a41cff014e2?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a41cff014e2</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[go]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 04:02:23 GMT</pubDate>
            <atom:updated>2025-05-20T13:38:51.310Z</atom:updated>
            <content:encoded><![CDATA[<p>with the launch of ChatGPT in Dec 2022 #AI and its use cases, videos, even Memes tutorials are booming everywhere.<br>As a Cloud DevOps Engineer working in retail domain my job was always challenging which includes reading documentation, code snippets, videos and many more to perform my daily duties such as:</p><ul><li>writing scripts for automation of tasks using shell, python</li><li>creating Dockerfile and images for micro-services</li><li>creating Kubernetes objects, helm charts</li><li>creating logging and monitoring dashboards for deployed services</li><li>creating infrastructure as a code using terraform and many more things</li></ul><p>for above daily tasks to do, I always wanted to have some tool/bot or scripts to help me to give all my answers at one go instead of browsing through documents of different tools.</p><p>With that in mind I found one of the good open source tool <strong>AIaC </strong>developed by <a href="https://aiac.dev/">Firefly</a></p><p>In this article we will see <strong>AIaC</strong> as follows:</p><ul><li>Installation</li><li>Configuration</li><li>Use Cases</li><li>Demo</li></ul><h3>Installation</h3><ul><li><strong>On Mac</strong>:</li></ul><pre>brew install gofireflyio/aiac/aiac</pre><ul><li><strong>Using Docker</strong>:</li></ul><pre>docker pull ghcr.io/gofireflyio/aiac</pre><ul><li><strong>From source:</strong></li></ul><pre>git clone https://github.com/gofireflyio/aiac.git<br>cd aiac<br>go build</pre><h3>Configuration</h3><ol><li>Create your OpenAI API key <a href="https://beta.openai.com/account/api-keys">here</a>.</li><li>Click “Create new secret key” and copy it.</li><li>Provide the API key via the OPENAI_API_KEY environment variable or via the --api-key command line flag.</li></ol><h3>Use Cases</h3><p>after typing <strong>aiac </strong>on command prompt you will get something like this:</p><pre>aiac    <br>Usage: aiac &lt;command&gt;<br><br>Flags:<br>  -h, --help                  Show context-sensitive help.<br>      --api-key=STRING        OpenAI API key ($OPENAI_API_KEY)<br>  -o, --output-file=&quot;-&quot;       Output file to push resulting code to, defaults to<br>                              stdout<br>  -r, --readme-file=STRING    Markdown file to push explanations to (available<br>                              only in ChatGPT mode)<br>  -s, --save                  Save AIaC response without retry prompt<br>  -q, --quiet                 Print AIaC response to stdout and exit<br>                              (non-interactive mode)<br><br>Commands:<br>  get (generate) &lt;what&gt; ...<br>    Generate IaC code</pre><p>By default, <strong>aiac</strong> prints the extracted code to standard output and asks if it should save or re-generate the code</p><p>To run using docker</p><pre>docker run \<br>-it \<br>-e OPENAI_API_KEY=[PUT YOUR KEY HERE] \<br>ghcr.io/gofireflyio/aiac get terraform for ec2</pre><h3>Demo</h3><p><strong>Demo 1: </strong>Lets create multistage Dockerfile for Go application</p><pre>aiac get multistage dockerfile for golang application with comments</pre><p>and in a moment it will give code like this:</p><pre># This is a multi-stage Dockerfile for building a Go web application.<br><br># First, we specify the build stage.<br>FROM golang:1.11-alpine AS build-env<br># Create the working directory<br>RUN mkdir /app<br># Set the working directory<br>WORKDIR /app<br># Copy all the source files into the container<br>COPY . .<br># Build the application<br>RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o main .<br><br># Now create the release stage, using scratch as base image<br>FROM scratch<br># Copy the binary from the build stage<br>COPY --from=build-env /app/main ./<br># Set the working directory<br>WORKDIR /app<br># Expose service port<br>EXPOSE 8080<br># Run the web application<br>CMD [&quot;./main&quot;]<br><br>✗ Hit [S/s] to save the file or [R/r] to retry [Q/q] to quit: </pre><p>Now in above since we havent specified output file it will generate code in stdout</p><p>Lets try one more demo and now we will save to file</p><p><strong>Demo 2:</strong></p><pre> aiac get k8s objects for go app with comments in current directory -o go-app.yml -s</pre><p>sample code is generated as below and get saved to mentioned file</p><pre>§§ 1000<br>+# Generate k8s objects for Go App With Comments in Current Directory<br>+<br>+This guide will help you create Kubernetes objects to deploy a Go app in your current directory with added comments.<br>+<br>+```yaml<br>+apiVersion: apps/v1 <br>+kind: Deployment <br>+metadata: <br>+  name: go-app-deployment<br>+  annotations: <br>+    # Add any optional comments here<br>+spec: <br>+  replicas: 1<br>+  selector: <br>+    matchLabels: <br>+      app: go-app<br>+  template: <br>+    metadata: <br>+      labels: <br>+        app: go-app<br>+    spec: <br>+      containers:<br>+      - name: go-app-container<br>+        image: &lt;APP_IMAGE_NAME&gt;<br>+        ports: <br>+        - containerPort: 8080<br>+```<br>+<br>+Next, we need to create a `Service` object so that your pods are accessible from outside the cluster:<br>+<br>+```yaml<br>+apiVersion: v1<br>+kind: Service<br>+metadata: <br>+  name: go-app-service <br>+  annotations: <br>+    # Add any optional comments here<br>+spec: <br>+  selector: <br>+    app: go-app <br>+  ports: <br>+  - protocol: TCP <br>+    port: 80 <br>+    targetPort: 8080<br>+  type: LoadBalancer<br>+```<br>+<br>+Finally, you need to create an Ingress object so that your services can be reached from outside the cluster:<br>+<br>+```yaml<br>+apiVersion: networking.k8s.io/v1beta1<br>+kind: Ingress<br>+metadata: <br>+  name: go-app-ingress<br>+  annotations: <br>+    # Add any optional comments here<br>+spec: <br>+  rules: <br>+  - host: &lt;YOUR_URL&gt;<br>+    http: <br>+      paths: <br>+      - path: /<br>+        backend: <br>+          serviceName: go-app-service <br>+          servicePort: 80<br>+```<br>+<br>+Now you can easily deploy your Go app to a Kubernetes cluster with these objects and the added comments. Good luck!<br>Code saved successfully at /Users/aakamat/Desktop/DevOps/kube-chatbot/goalng-app/go-app.yml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kK0FEH_F56RFd67e0L26Ig.png" /></figure><p><strong>Demo 3</strong>: Lets create Infrastructure to deploy our code</p><pre>aiac get terraform code to deploy kubernetes object to eks cluster In custom VPC with HA and IAM configs -o main.tf -s</pre><p>and alas! I got sample code as follows which also got saved in <strong><em>main.tf</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7JgDO_629Ax6yGs33r9qiw.png" /></figure><p>Now lets check if we can get sample pipeline code (gitlab-ci.yml used here)</p><pre>aiac get gitlab pipeline file for CI CD for  go app in current directory with comments into eks cluster -o .gitlab-ci.yml -s</pre><p>and yes I have got sample code for this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HkeMardSRJj78v4B8Vhf-A.png" /></figure><p>As you can see from above using AI I am able to:</p><ul><li>create Go lang application</li><li>create Dockerfile for above Go application</li><li>create k8s object for above docker image</li><li>create infrastructure as a code using terraform</li><li>create pipeline code using .gitlab-ci</li></ul><p>Although code shown in demo is not exact and perfect and may change from project to project, organisation to organisation as there might be lots of standards, best practices and compliances which make this code reformatting and restructured.</p><p>But with the help of <strong>AIaC, </strong>as a Cloud DevOps Engineer I can save lot of time which I need to spend for researching code, read docs for various tools, create CI-CD pipeline and create automation code for same.</p><p>There are many more we can do and imagination and ideas are limitless. so lets use AI for make your day today DevOps life easy and simple.</p><p><strong>Refernces</strong>:</p><ul><li><a href="https://github.com/gofireflyio/aiac#readme">https://github.com/gofireflyio/aiac#readme</a></li><li><a href="https://aiac.dev/">https://aiac.dev/</a></li><li><a href="https://beta.openai.com/docs/introduction">https://beta.openai.com/docs/introduction</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a41cff014e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 DevOps Questions you should ask yourself]]></title>
            <link>https://medium.com/@ashishkamat27/top-10-devops-questions-you-should-ask-yourself-e6f50959635?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6f50959635</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Wed, 15 Nov 2017 17:18:32 GMT</pubDate>
            <atom:updated>2017-11-15T17:18:32.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBXc9eJ1YRFLtkNI_djaAw.png" /><figcaption>DevOps</figcaption></figure><p>DevOps Culture is becoming really important and all big, medium, small sized companies looking forward to bring this culture into their firm. As per report from Gartner survey 40 % companies already adopted this culture and reach to Its maturity model and tasting its success at the end of 2017.</p><p>If you are planning to adopt this culture soon (in first quarter of 2018) and improve your release cycle by making delivery faster and less buggy, here is list of Q that might help you to understand and adopt this culture faster.</p><h4>Q1 How is DevOps different from Traditional Software Development?</h4><ul><li>Focus on flow of value, not conformance to project plan</li><li>Production-first mindest</li><li>Culture of shared ownsership and cooperation</li><li>Rapid iteration with fast feedback loops</li><li>Automate, automate, automate</li><li>Infrastructure is treated as flexible rsource.</li></ul><h4>Q2 What DevOps practices can I levarage to expediate software deliery and improve quality?</h4><ul><li>Continous Integration</li><li>Continous Deployment</li><li>Continuous Testing</li><li>Applicaton Performace Monitoring (APM)</li><li>Testing in production</li></ul><h4>Q 3 Effective Continuous Integration</h4><ul><li>Put everything under source control</li><li>Automate the build process</li><li>Unit Testing /Code Analysis as part of build</li><li>Fix broken build quickly</li><li>Monitor build quality</li><li>Build once, deploy many times</li></ul><h4>Q4 Continuous Deployment</h4><ul><li>Put everything in a source control</li><li>Never deploy or configure resources manually — sript and automate</li><li>Make it fast — move to Cloud if that’s what it takes</li><li>Make your deployments idempotent</li></ul><h4>Q5 How do I use Infrastructure as a Code and configuration as a Code to improve scalabilty?</h4><ul><li>Treat Infrastructure as a flexible resource</li><li>Never deploy or configure resources manually — script and automate</li><li>Parameterize your scripts so that you’re using the same script in every enviornment</li><li>Always “deploy everything” (idempotency)</li><li>Architect for scale</li></ul><h4>Q6 What type of testing should I conduct and how do I conduct these test?</h4><ul><li>Builds: Unit Tests(no external dependencies)</li><li>Dev/Int environments: Integration/ Functional Tests</li><li>Staging: Load Tests</li><li>Production: Smoke/Availabilty Tests</li><li>Production/ A/B Testing</li><li>Manual/ Exploratory Testing — but prefer autoamtion</li></ul><h4>Q 7 How do Developers and Operations team work together to manage software release effectively ?</h4><ul><li>Put everything into source ontrol</li><li>Never deploy or configure resources manually — script and automate</li><li>Work together -shared ownership</li><li>Shared Ownership — especially of Production (Operations)</li></ul><h4>Q 8 How Do I integrate hypothesis-driven development into our software development process?</h4><ul><li>Formulate hypothesi with clearly measurable criteria</li><li>Deploy — quiclky</li><li>Monitor (APM)</li><li>(Dont be afraid) Fail fast</li><li>Learm from Production- groom the backlog accordingly</li></ul><h4>Q 9 What DevOps tools or practices can help me learn from Production ?</h4><ul><li>Application Performance Monitoring Insights, Log Analysis, Nagios, New Relic</li><li>Monitor “business metrics” as well performance and availabilty</li><li>Measure value from the user perspective</li></ul><h4>Q 10 If I want DevOps, should I use Scrum or Learn or Kanban?</h4><ul><li>Yes, yes, Yes !! Any iterative framework that minimizes cycle time work well</li><li>Culture is a critical component of DevOps, so invest in it.</li><li>Take the best of Scrum| Learn Kanban and adapt it to your team and environment</li><li>Keep “delivering value” the key focus</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6f50959635" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Must Have Bitbucket Add-ons: Part 3]]></title>
            <link>https://medium.com/@ashishkamat27/must-have-bitbucket-add-ons-part-3-688f5641bd63?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/688f5641bd63</guid>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[sonarqube]]></category>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[aml]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Tue, 10 Oct 2017 15:46:29 GMT</pubDate>
            <atom:updated>2017-10-10T15:46:32.346Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the last part of the 3 parts series of “Must have Bitbucket add-ons”</p><p>In last 2 parts we have seen</p><p>a) <strong>Smart commit add-on</strong> (Free add-on) used to include operations triggers comments that would be directly get displayed on Jira/ Bitbucket Dashboard</p><p>b) Work-Zone add-on (Paid) which is used to manage your entire branching and merging workflow with setup of permissions and hooks with list of users defined.</p><p>Now In this final part we are going to look out very interesting and yet important add-on which is <strong><em>Sonar for Bitbucket Server (previously known as Stash)</em></strong></p><h3>A] Introduction</h3><p>This add-on integrates SonarQube’s useful metrics and defect hunting tools into Bitbucket Server’s pull requests. Detected code violations, uncovered and duplicate code lines are directly shown in Bitbucket Server’s diff view. By only showing them on changed lines of the pull request, the code review peers can focus on the code that should be integrated into the target branch.</p><p>For every found Sonar issue, a Bitbucket Server task can be created by just one click so that fixing it is not forgotten. Sonar metrics like technical debt are shown on the pull request overview. To ensure a good quality of new code changes, this add-on provides merge checks to disallow code being merged in if it doesn’t meet the configured quality requirements</p><h3>B] Features</h3><p>i) <strong>Shows Sonar codes in pull request</strong></p><p>Shows issues found by Sonar directly in the pull request diff view. Provides a context menu which allows you to see issue details in Sonar, to mark an issue as a false positive or to create a comment or task for it.</p><p><strong>ii) Visualize Code coverage and Duplicate code lines</strong></p><p>Shows code coverage directly in your pull request diff view. Also marks duplicated code lines and offers links to directly go to the affected code lines in Bitbucket Server.</p><p><strong>iii) Pull request statistic and quality merge check</strong></p><p>Shows Sonar statistics in the pull request overview and provides merge checks based on SonarQube’s quality gates and other quality metrics like technical debt, code coverage, issues based on severity and duplicated code</p><p>iv) Automatically Create Project in Sonar against specific branch.</p><p>v) Automatically deletes Sonar Project after pull request merged and branch is deleted from Bitbucket (clubbed with delete source branch when PR is merged checkbox)</p><h3><strong>C] Architecture</strong></h3><p>Here there is a slight change in the architecture, instead of Bamboo, I have used Jenkins as CI Server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*6VsYSotr8YqnlLa5d2tn6Q.png" /></figure><p>As shown above in architecture,</p><p>1. Developer pushes the changed code on Remote (Bitbucket/Stash Server).</p><p>2. For the changed code Stash triggers Jenkins build for respective branch.</p><p>3. Build/CI Server will run sonar analysis and publishes result in Sonar against given branch.</p><p>4. CI server notifies build status for the given branch.</p><p>5. Developer then create pull request in Stash/Bitbucket server to merge his changes.</p><p>6. For the created pull request Bit bucket Server then collect all relevant data and display against pull request.</p><p>7. Peers/Reviewers discuss Issues found against pull request and assign accordingly to resolve quickly</p><h3>D] Installation</h3><p>1. Click the admin drop-down on your Stash instance and choose Add-ons.</p><p>2. Click Find new add-ons from the left-hand side of the page.</p><p>3. Locate Sonar for Stash via search.</p><p>4. Click Install to download and install Sonar for Stash.</p><p>5. You’re done!</p><h3>E] Configuration</h3><p>As shown In architecture, It is Integrated with 3 tools, viz;</p><p>i) Bitbucket Dashboard</p><p>ii) Sonarqube Server</p><p>iii) Jenkins CI Server</p><p>So we will split up this Configuration in 3 parts</p><p><strong>I] Bitbucket Server</strong></p><p>again here we need to do configuration at 3 levels</p><p><strong>a) Global level</strong></p><p>Sonar for Bitbucket Server needs to have access to a SonarQube server. This can be configured in Bitbucket’s administration view under “Settings” &gt; “Sonar for Bitbucket”:</p><p>Note that you only have to provide a login and password if your SonarQube server does not allow anonymous login.</p><p><strong>b) Project/Repository level</strong></p><p>Sonar for Bit-bucket server allows configuring what information it shows on a pull request and under which conditions it should disallow merges of new code. These settings can be found in Bitbucket’s repository settings under “Sonar for Bitbucket”.</p><p>It is again divided into 3 sections:</p><p>i) Sonar Project</p><p>For every repository, a Sonar project base key needs to be configured. This is the Sonar project key without the branch suffix .Sonar for Bitbucket lists all available project keys it gets from the configured Sonar server.</p><p>When doing code reviews in this repository, Sonar for Stash will add the branch names to this project base key to get Sonar information from the SonarQube server.</p><p>You need to select <strong>Build type</strong> for Stash by which your Build server going to trigger you Sonar instance. You need to select one of the option from available<strong>. Compatibility mode</strong> is recommended if none of them is working for you.</p><p>You can also define a replacement for illegal branch characters in Sonar. Note that the default “_” is fine for Bamboo and Jenkins server.</p><p>ii) Sonar Feaures</p><p>For every repository you can define which features of Sonar should be shown in its pull request diff view. It is possible to restrict the issues being shown to a certain minimum severity, to only show test coverage for unit or integration tests (or both), and if the Sonar statistics should be shown on the pull request overview screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/601/1*Tr2O23HWFimQ52z2V_9OFg.png" /></figure><p>iii) Sonar Merge Checks</p><p>Quality based merge checks prevent code from being merged into your project that does not meet configurable quality requirements. In this section of the configuration screen, you can define these quality levels based on Sonar’s technical debt, a maximum increase of new Sonar issues of a certain severity, a maximum increase of duplicated code and a minimum test coverage percentage:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*qtKBwqh9_LIEpTXU.png" /></figure><p><strong>II] Jenkins</strong></p><p>for Jenkins we need to do following:</p><p>a. Installation and configuration of “Bitbucket/Stash Web hook for Jenkins”</p><p>b. Jenkins Sonar plugin configuration</p><p>c. Jenkins Job configuration</p><p><strong>a) Installation and configuration of web-hook</strong></p><p>The detailed instruction of this setting can be found on following URL:</p><p><a href="https://blog.mikesir87.io/2013/04/continuous-integration-with-stash-and-jenkins/">Continuous Integration with Stash and Jenkins</a></p><p><strong>b) Jenkins Sonar plugin Configuration</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*D-9dMqzONoqc1P9N.png" /></figure><p><strong>c) Jenkins Job configuration</strong></p><p>Before we can configure the execution of Sonar, we have to do some precondition work in order to be able to replace illegal branch characters in our branch names . The currently built Git branch can be accessed in Jenkins with the build variable <strong>$GIT_BRANCH</strong>. Because the Jenkins Git plug-in includes the “origin/” prefix in the branch names, we also have to remove that one. Both steps together lead to the following shell command that needs to be executed BEFORE the post-build Sonar action:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/468/1*HnLKxGo6pdDu4or3pNKG6g.png" /></figure><p>To inject the environment variable sonar-branch as shown above, you also need to install the <a href="https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin">Jenkins EnvInject Plugin</a>.</p><p>Next we need to pass argument as -Dsonar.branch=$SONAR_BRANCH inside Project properties defined under section “Invoke stand-alone Sonar analysis”</p><p>Now when Jenkins performs Standalone sonar analysis using sonar runner It will be passed as sonar-runner -Dsonar.branch=$SONAR_BRANCH. Where $SONAR_BRANCH will be replaced by $GIT_BRANCH which is modified by above written shell script at run time.</p><h3>F] In Action</h3><p>find out here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FTVV7gEjPRHc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DTVV7gEjPRHc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FTVV7gEjPRHc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/20b05d221323c87d8b4d0f40b82a5221/href">https://medium.com/media/20b05d221323c87d8b4d0f40b82a5221/href</a></iframe><h3>G] Pricing</h3><p>more details can be found out here:</p><p><a href="https://marketplace.atlassian.com/plugins/ch.mibex.stash.sonar4stash/server/pricing">Sonar for Bitbucket Server</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=688f5641bd63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Must have Bitbucket add-ons: Part 2]]></title>
            <link>https://medium.com/@ashishkamat27/must-have-bitbucket-add-ons-part-2-e7bd0258c49b?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7bd0258c49b</guid>
            <category><![CDATA[repositories]]></category>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Sun, 01 Oct 2017 12:28:00 GMT</pubDate>
            <atom:updated>2017-10-01T12:28:00.612Z</atom:updated>
            <content:encoded><![CDATA[<p>In last section of this series of “Must have bitbucket add-ons”, we have seen one plugin nameed Smart Commit</p><p>In this section I am going to focus on Add-on related to SCM Workflow:</p><h3><strong>2) Workzone for Bitbucket</strong></h3><p><strong>A] Introduction</strong></p><p>Workzone allows you to control your SCM workflow in Bitbucket. Workzone helps enterprises to implement their Bitbucket based SCM process in a straightforward and intuitive way.</p><p><strong>B] Features</strong></p><p>a) <strong>Predefined Pull Request Reviewers.</strong></p><p>· Configure pre-defined (mandatory/suggested) reviewers for branches and a Pull Request will include these reviewers automatically.</p><p>b) <strong>Automatic Pull Request Merge.</strong></p><p>· Workzone can merge the Pull Request automatically when all or a percentage of reviewers have approved and/or on successful build results.</p><p>· Workzone can delete the source branch of a Pull Request after successful automatic merge.</p><p>c) <strong>Organize Workflow.</strong></p><p>· Allow or block push operations to a branch once a Pull Request has been created and un-approve all approvals on a Pull Request should the originating branch be updated.</p><p>· Block/Allow merging Pull Requests based on configurable merge conditions.</p><p><strong>C] Installation</strong></p><p>1. Log into your Bitbucket/Stash Server instance as an admin.</p><p>2. Click the admin dropdown and choose <strong>Atlassian Marketplace</strong></p><p>3. Click <strong>Find new add-ons</strong> from the left-hand side of the page.</p><p>4. Locate <strong>Workzone: BitbucketPullRequest Workflow</strong> via search</p><p>5. Click <strong>Try free</strong> to begin a new trial or <strong>Buy now</strong> to purchase a license for <strong>Workzone: BitbucketPullRequest Workflow</strong></p><p>6. Enter your information and click <strong>Generate license</strong> when redirected to MyAtlassian.</p><p>7. Click <strong>Apply license.</strong></p><p><strong>D] Configuration</strong></p><p>Since It is managing your entire SCM workflow, unlike <strong>Smart commit</strong> plugin (discussed in Part 1), you need to to some basic and one time configuration depending on how your SCM workflow looks like</p><p>Lets look for the configuration:</p><p><strong>I] Global level</strong></p><p>Here you need to do configuration for following things: (Inside Bitbucket -&gt;Manage Add-ons-&gt;Workzone for Bitbucket-&gt;Configure)</p><p>a) Notification about Pull request via Email.</p><p>b) Enforcing Merge Condition</p><p>c) Auto merge feature.</p><p>d) Setting Limit for Reviewer Groups.</p><p><strong>II] Project level</strong></p><p>Here you need to specify various configurations which are segregated in 3 parts as</p><p>1) Properties</p><p>2) Reviewers</p><p>3) Merge</p><ol><li><strong>Properties</strong></li></ol><p>Here you can do following task</p><p><strong>a. Push after Pull request</strong></p><p>If disabled, push against Open Pull request’s source branch is rejected.</p><p><strong>b. Disapprove outgoing pull request</strong></p><p>If Enabled and Code is pushed against Open Pull request’s source branch, it will cancel all approvals for that pull request.</p><p><strong>2. Reviewers</strong></p><p>Here you need to specify reviewers for each branch against which pull request is to be opened.</p><p>You can either select</p><p>a) branch from Branch tab</p><p>b) Branch pattern for Source and Destination from Advanced tab.</p><p>In both cases you need to Specify</p><p>a Users and Groups</p><p>b Mandatory Reviewers.</p><p><strong>3) Merge</strong></p><p>Here you need to do configuration for Auto-merge Rejecting Merge, etc.</p><p>Like Reviewer You can either select</p><p>a branch from Branch tab</p><p>b Branch pattern for Source and Destination from Advanced tab.</p><p>To do so you need to provide following parameters:</p><p>a Source Branch [optional]</p><p>b Destination branch</p><p>c Reviewers approval Quota</p><p>d Required Successful builds</p><p>Under Advanced Section you can</p><p>Specify/modify Merge Condition</p><p>a Adding Triggers like:</p><p>· Delete Source branch</p><p>Watch build results -If Pull request has required successful builds and meeting merge condition then Merge Pull request automatically.</p><p>Watch working video here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuBZL-_juaIo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuBZL-_juaIo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuBZL-_juaIo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/366ff18910ef735f89646aa70df57ebd/href">https://medium.com/media/366ff18910ef735f89646aa70df57ebd/href</a></iframe><p><strong>E] Pricing</strong></p><p>See more about pricing and other details on following link:</p><p><a href="https://marketplace.atlassian.com/plugins/com.izymes.workzone/server/pricing">Workzone: PullRequest Workflow</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7bd0258c49b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Must have Bitbucket add-ons: Part 1]]></title>
            <link>https://medium.com/@ashishkamat27/must-have-bitbucket-add-ons-9f280a51fd1?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f280a51fd1</guid>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[bitbucket]]></category>
            <category><![CDATA[plugins]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Sun, 01 Oct 2017 11:33:14 GMT</pubDate>
            <atom:updated>2017-10-01T11:43:15.350Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are familier with Atlassian Stack, you must have come across tool called “Bitbucket”. It is basically a Repository management tool which is available on 2 types of variants: mainly a) cloud b) Server.</p><p>In this series of sessions I am going to explain all availble, and must have bitbucket add-ons:</p><p>I will focusing on following points for each add-on</p><ol><li>Introduction and Need</li><li>Setup</li><li>Use cases</li><li>Pricing</li></ol><p>Lets begin</p><h3><strong>1. Smart Commit</strong></h3><p><strong>A] Introduction</strong></p><p>Smart Commits allows users over commits to execute special actions during the development. Each commit message can define some special actions. These actions will be executed if the change sets will be pushed to the remote repository. After the change-sets have been received in Bit-bucket, Bitbucket will parse the change-sets regarding some special keywords and related parameters. If the parser will find a valid key and parameters, the corresponding action will be executed. Actions can relate to all Atlasssian products like JIRA or Bitbucket</p><p><strong>B] Features</strong></p><p><em>i) Just specify action to be performed inside commit message.</em></p><p>ii) <em>Reduce overhead from developer</em>.</p><p>iii) <em>Can create pull request by just mentioning in commit.</em></p><p><em>iv) Can log work on Jira.</em></p><p><em>v) Can change status of Jira issue.</em></p><p>vi) <em>Mention user name inside comment which will get reflected inside Jira.</em></p><p><em>vii) Add reviewers by just mentioning inside commit.</em></p><p>viii) <em>Can add comment to Jira issue and Pull request.</em></p><p><strong>C] Installation/Setup</strong></p><p>1. Log into your Bitbucket instance as an admin.</p><p>2. Click the admin dropdown and choose Add-ons.The Manage add-ons screen loads.</p><p>3. Click Find new add-ons from the left-hand side of the page.</p><p>4. Locate “Smart Commits for Bitbucket” via search. Results include add-on versions compatible with your Bitbucket instance.</p><p>5. Click Install to download and install your add-on.</p><p><strong>D] Supported Actions</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*i42A9s3KVbRNE680qRnSvQ.png" /></figure><p>You can find out more information on following link:</p><p><a href="https://confluence.atlassian.com/fisheye/using-smart-commits-298976812.html">Using Smart Commits - Atlassian Documentation</a></p><p><strong>E] Pricing</strong></p><p>Its free.</p><p>find out more about pricing on following link:</p><p><a href="https://marketplace.atlassian.com/plugins/com.lb.software.stash.smart.commit.lb-software-stash-smart-commit/server/overview">Smart Commits for Bitbucket</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f280a51fd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Well Architected Framework: AWS (Summary)]]></title>
            <link>https://medium.com/@ashishkamat27/well-architected-framework-aws-summary-3513ac05f192?source=rss-36936ba363c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3513ac05f192</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ashish Kamat]]></dc:creator>
            <pubDate>Sat, 30 Sep 2017 18:57:11 GMT</pubDate>
            <atom:updated>2017-09-30T18:57:11.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*clILqctXiykAeJom." /></figure><p><strong>1) Security:</strong></p><p>The ability to protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies.</p><p><strong>2) Reliability</strong></p><p>The ability of a system to recover from infrastructure or service failures, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues.</p><p><strong>3) Performance Efficiency</strong></p><p>The ability to use computing resources efficiently to meet system requirements, and to maintain that efficiency as demand changes and technologies evolve</p><p><strong>4) Cost optimization</strong></p><p>The ability to avoid or eliminate unneeded cost or suboptimal resources.</p><p><strong>5) Operational Excellence</strong></p><p>The ability to run and monitor systems to deliver business value and to continually improve supporting processes and procedures.</p><p>following are design principles you should consider during designing fault tolerant, scalable, fully available architecture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*Io6onzuqrxOdZXsMY45IQw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3513ac05f192" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>