<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>dxp on Kunal Shetye&#39;s Blog</title>
    <link>https://kunalshetye.com/tags/dxp/</link>
    <description>Recent content in dxp on Kunal Shetye&#39;s Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Jun 2022 15:47:23 +0200</lastBuildDate><atom:link href="https://kunalshetye.com/tags/dxp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DXP and Github Workflows</title>
      <link>https://kunalshetye.com/posts/dxp-and-github-workflows/</link>
      <pubDate>Wed, 22 Jun 2022 15:47:23 +0200</pubDate>
      
      <guid>https://kunalshetye.com/posts/dxp-and-github-workflows/</guid>
      <description>Prerequisistes  Access to a DXP Environment Access to Github Basic Understanding of CI/CD pipelines and YAML An existing CMS12 website connected to DXP  Generate API Keys I&amp;rsquo;ve generated a seperate API Key for usage from Github which only has access to my integration environment because I want to deploy to production by hand and avoid &amp;ldquo;accidental&amp;rdquo; releases to production. You could however choose to let github deloy the site to the production environment if you like.</description>
    </item>
    
  </channel>
</rss>
