<?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 Sachin Upmanyu on Medium]]></title>
        <description><![CDATA[Stories by Sachin Upmanyu on Medium]]></description>
        <link>https://medium.com/@sachinupmanyu?source=rss-8d43519f5214------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JXEyldNUcBAesnBh.</url>
            <title>Stories by Sachin Upmanyu on Medium</title>
            <link>https://medium.com/@sachinupmanyu?source=rss-8d43519f5214------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:10:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sachinupmanyu/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[SFCC - Automating On-Demand Sandboxes]]></title>
            <link>https://sachinupmanyu.medium.com/sfcc-automating-on-demand-sandboxes-53a114d245f0?source=rss-8d43519f5214------2</link>
            <guid isPermaLink="false">https://medium.com/p/53a114d245f0</guid>
            <category><![CDATA[b2c]]></category>
            <category><![CDATA[sfcc]]></category>
            <category><![CDATA[salesforce-commerce-cloud]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Sachin Upmanyu]]></dc:creator>
            <pubDate>Sat, 06 Feb 2021 10:03:09 GMT</pubDate>
            <atom:updated>2021-02-06T13:09:43.728Z</atom:updated>
            <content:encoded><![CDATA[<h3>SFCC - Automating On-Demand Sandbox Operations</h3><p>Salesforce provides us limited no of Sandbox credits, and as a primary On-Demand Sandbox Owner, it falls upon you to use those credits judiciously. To achieve this you might have calculated the no of hours you need to keep your sandboxes up in a day, and how long it would take you to consume your allocated credits.</p><p>The key here is to being consistent in starting and stopping your sandboxes at specified time, because if you fail to start sandboxes on time it would impact development and if you fail to stop sandboxes on time, you’ll overrun your allocated credits sooner then it should.</p><p>As a Sandbox Owner for your organisation, there are 2 ways you can manage your On-Demand Sandboxes, from Salesforce provided Swagger APIs or by using the SFCC-CI tool. There is also an another way of having a user friendly GUI application from which you can manage Sandboxes, monitor your credit usages and get insight on when you’d next need to buy credits based on your usages, but Salesforce doesn’t provide such an application, So, I have worked to build such application and hoping to release it soon for the community.</p><p>Meanwhile, you can follow this guide to create your own process of automatically starting/stopping On-Demand Sandboxes based on a schedule.</p><p>Benefits of automating Sandbox start/stop operations.</p><ol><li><strong>Better control over credit usages:</strong></li></ol><p>You can define a schedule on which Sandboxes need to be up, this will help in get a more accurate estimation of how long your credits will last, as there won’t be any human intervention needed.</p><p><strong>2. No need to daily remember to start/stop Sandboxes</strong></p><p>Sandboxes will automatically start and stop daily at the time you specify, no need to set reminders for them.</p><p>We will be using the SFCC-CI tool in this guide to setup a cron to manage the Sandboxes. This guide assumes you are working on a Linux distro and have some experience with shell scripts, if not, help can be taken from a developer having this experience.</p><p><strong>Step 1: Setup sfcc-ci tool</strong></p><p>Install the SFCC-CI tool <a href="https://github.com/SalesforceCommerceCloud/sfcc-ci#installation-instructions">from here</a>.</p><p>You’ll need to have access to the github repositories to download this. If you don’t have access to them, <a href="https://trailhead.salesforce.com/en/content/learn/modules/b2c-developer-resources-and-tools/b2c-developer-access-repositories#set-up-git-hub-account">follow this Trailhead module for steps</a>.</p><blockquote>After sfcc-ci is installed, you should see the help documentation when you run sfcc-ci in terminal</blockquote><p><strong>Step 2: You’ll need to have the ability to create API keys to proceed further</strong></p><ol><li>Log into your account.demandware.com portal.</li><li>Go to “API Client” navigation.</li><li>Select your organisation from the dropdown, and click on “Add API Client”.</li><li>Enter “Display Name”, set the password(and note it down somewhere, we’ll need this later), make sure “Access Control” is enabled, Add the organisation.</li><li>Provide “tenantFilter” in Default Scope.</li><li>Add these in Redirect URIs section, we might need these if we authenticate using this key from Swagger APIs or using client:auth sfcc-ci command.</li></ol><p><a href="https://admin.us01.dx.commercecloud.salesforce.com/oauth2-redirect.html">https://admin.us01.dx.commercecloud.salesforce.com/oauth2-redirect.html</a><br><a href="http://localhost:8080/">http://localhost:8080</a></p><p>7. Save the form.</p><p><strong>Step 3: Disable MFA for Organisation</strong></p><p>This needs to be confirmed with all concerned Stakeholders, even though we will still have MFA enforced for all other roles.</p><ol><li>Go to Organisations navigation</li><li>Select your Organisation</li><li>At the bottom of the page uncheck MFA enabled for all users in the organization.</li><li>Under Users with the following roles need to authenticate using a second factor. section, add all roles except Sandbox API User role.</li></ol><p><strong>Step 4: Create a user for automating sfcc-ci commands</strong></p><p>If you haven’t already, create a new user with limited role just for managing Sandbox automation.</p><ol><li>Add a user in your organisation.</li><li>Assign Sandbox API User Role.</li><li>Note the username and password for this user, we’ll need this later.</li></ol><p><strong>Step 5: Create a shell script</strong></p><ol><li>Create a shell script with sfcc-ci client:auth login command.</li><li>Add actions for start/stop for each sandbox.</li><li>Create different shell scripts for start and stop actions.</li><li>Logout after all actions are done (sfcc-ci auth:logout).</li><li>All paths must be absolute paths in this script including commands and file paths, otherwise cron won’t know which files/commands to run.</li><li>You can also take reference from the screenshot attached below, this file contains example of starting a single Sandbox, you can replicate this line and change the Sandbox ids to manage as many Sandboxes you want, ideally there should be different files for Start and Stop Operations.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*uCFqV8XtiHppBh2kjrrwoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*tOud8PCqrBVHOT4X-W6jdw.png" /><figcaption>example of a start operation(left), stop operation(right)</figcaption></figure><p><strong>Step 6: Create a dw.json for maintaining your login credentials</strong></p><p>For storing credentials we have multiple options of using dw.json, .env file or setting up environment variables, in this example we will be creating a dw.json file</p><ol><li>Create a dw.json file in same folder where you are keeping you shell scripts.</li><li>The sfcc-ci client:auth used in shell scripts above, looks for a dw.json file and automatically authenticate the user based on credentials stored in dw.json.</li><li>Sample dw.json file, you’ll need to replace placeholders with the credentials noted previously.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*NiM5PoRSF1E7MBAiynHmaw.png" /><figcaption>sample dw.json file</figcaption></figure><p><strong>Step 7: Create a file for logging Cron outputs</strong></p><ol><li>Create a file anywhere you want.</li><li>When cron runs this file will be overwritten with latest output of cron.</li><li>Note the file path, it will be used when creating a cron entry.</li></ol><p><strong>Step 8: Create a Cron entry</strong></p><ol><li>Run in terminal: crontab -e (to edit crontab).</li><li>Create entries for all your scripts.</li><li>Provide schedule when they should run, <a href="https://crontab.guru/#0_10_*_*_1-5">you can use this link to create the format needed for Cron scheduling</a>.</li><li>Before that do a test with limited action(like authenticating and stopping a single sandbox) cron running every minute, and check the output in log file, if all ok, create the final entries and schedules for your cron.</li><li>You can also use Slack notification to be sent when cron runs, refer <a href="https://www.cloudsavvyit.com/289/how-to-send-a-message-to-slack-from-a-bash-script/">https://www.cloudsavvyit.com/289/how-to-send-a-message-to-slack-from-a-bash-script/</a></li><li>Example cron entry running every weekday 10 AM in the morning</li></ol><p>0 10 * * 1–5 sh &lt;path-to-folder&gt;/&lt;script-name&gt;.sh &gt; &lt;path-to-log-file&gt;/&lt;log-filename&gt;.txt 2&gt;&amp;1</p><p><strong>Step 9: Enjoy a beer</strong></p><p>Well done! You have automated the menial work you needed to do on a daily basis. Your On-Demand Sandboxes will start/stop based on the schedule you have defined in Cron, as long as your workstation where you have stored the shell scripts is running and you have internet access 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53a114d245f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My journey with Linux: beginner to power user]]></title>
            <link>https://sachinupmanyu.medium.com/my-journey-with-linux-beginner-to-power-user-2f72b2d66b77?source=rss-8d43519f5214------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f72b2d66b77</guid>
            <category><![CDATA[foss]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[power-user]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Sachin Upmanyu]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 17:39:07 GMT</pubDate>
            <atom:updated>2020-07-16T17:39:07.450Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A programmer managing different servers on multiple monitors" src="https://cdn-images-1.medium.com/max/1024/0*nPztCBmjcM2z2VMK" /><figcaption>Photo by <a href="https://unsplash.com/@arianismmm?utm_source=medium&amp;utm_medium=referral">Arian Darvishi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>⚠️ This is not a technical post, this is intended to be a light-hearted story containing a series of life events &amp; anecdotes, where i’ll try to write how &amp; why I got interested in Linux, and how being a power user in Linux helped me in my career.</p><p>First, as an introduction, I grew up in a joint family, where we were 4 brother(3 cousins, if you will) and a sister, My sister chose commerce in her senior secondary instead of Science/Maths, so she’s disowned anyway 😅.</p><p>Growing up our Eldest brother Sid(<a href="https://fedoraproject.org/wiki/User:Siddhart">Siddharth Upmanyu</a>) who was also Fedora India Ambassador, had a deep impact on all of us. and it was from him that I first learned about Linux and Open Source software.</p><p>In 2006, I completed my Senior Secondary(12th Grade). But till then my only physical interaction with “computers” was during our 1 hour Computer Class, where systems rarely worked, and when they worked we’d (mis)use them to play <a href="https://en.wikipedia.org/wiki/Dangerous_Dave">Dangerous Dave</a>.</p><p>After 12th Grade, I enrolled for engineering entrance exam mainly because my brothers were already pursuing their engineering degree, and it seemed like a normal choice to get myself enrolled too. I cleared the entrance exam &amp; chose Information Technology as preferred stream, because why not!</p><p>Around second year in my college I borrowed one of my cousin’s old desktop (because that’s what you do in joint families, ohh.. i borrowed and crashed his bike too 😆 ). It was the first time I had a personal computer, all to my self, and now I could play Dave even outside Computer Class(Yay!).</p><p>But, Inspired by Sid, Instead of wasting time playing video games, I decided to learn more about Linux &amp; FOSS.</p><p>So me &amp; my roommate at that time, ordered a CD(free of cost) from fedora’s site, which used to take 6 weeks to be shipped &amp; delivered(and at that time we didn’t know how to copy &amp; burn a bootable cd, so if the CD gets corrupted, it would take another 6 weeks for it to be delivered).</p><p>We were somehow able to install Fedora in my desktop after few days’ effort. As we had no idea how install or operate this OS, everything was a challenge. Even extracting a tarball took us almost a week(yeah!), and the issues were compounded by lack of internet connection, so we’d go to nearby cyber cafe(yes they used to exist), search for terminal commands, write them on paper, and try them at home.</p><p>After initial weeks, we had a basic idea of Fedora and different apps, and after that the golden age of Fedora exploration began. We spent weeks and months breaking, fixing and reinstalling the system. In a few months we had invested lots of time in fixing hardware, software issues, learning skills like LAN networking, compiling software from source code, mastering GRUB, and best of all, brainstorming sessions on these extraordinary challenges.</p><p>This was a very unique period in my college time, learned a lot of new things ..ohh.. and we also watched every movie that we could get access to, in any language that we could find (personal favourites: all the movies where Akira Kurosawa &amp; Toshiro Mifune collaborated).</p><p>Later on I shifted with my college mates, and there I came across books on RHCE exam, which my roommate was preparing for. As an avid reader I just had to read it. Back then I used to read anything &amp; everything (from <a href="https://play.google.com/store/apps/details?id=com.xerseys.baankelalcomics&amp;hl=en_IN">bankelal</a> to <a href="https://www.goodreads.com/work/quotes/6517-the-madman">Khalil Gibran</a>). So I sat with those books(RHCE), and finished them in a couple of days. As I already had lots of hands-on experience I was able to grasp the concepts quickly, but also learned a lot of new things in the process.</p><p>By now I considered myself a power user in multiple Linux based OSs: Fedora, Ubuntu, OpenSuse, and tried lots of new distros also. I could write complex shell scripts, fix most of installation/setup related issues, install and manage services(Mainly LAMP), configure Local Network and so on.</p><p>The timeline around 2008–09, was the time I felt Linux evangelism was at it’s highest(around me), there were lots of activities/events in Colleges, promoting Linux and actively debating people on Open Source VS Closed Source. Windows was WinBlows &amp; Apple was stupid at best &amp; evil at worst.</p><p>I think the debate between open source and closed source has always been on moral grounds and the apparent dumbing down of our interaction with Software, where corporations choose what’s best for the end-users, rather than giving them the flexibility to choose themselves. But unfortunately this approach has broadly worked, and I also find myself tilted towards this direction, as I neither have time nor energy to deal with Software/hardware issues, now I just want everything to work out of the box(Which IMHO Ubuntu has excelled in, and is a great combination of usability &amp; flexibility).</p><p>But enough of FOSS vs Proprietary.</p><p>Summing up, The skills I acquired having hands-on experience in Linux based systems, are still serving me in my day to day Job.</p><p>It’s useful in every aspect of my job, from simple things like keeping my PC updated/lag-free, fixing minor hardware related issues, to Job deliverable. Having experience as a power user in Linux, it was comparatively easier for me to grasp DevOps practises, Managing server infrastructure and creating server architecture.</p><p>It certainly gave me edge over “normal” developers and helped me survive in startup culture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f72b2d66b77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up Development environment for Salesforce]]></title>
            <link>https://sachinupmanyu.medium.com/setting-up-development-environment-for-salesforce-332180ba3242?source=rss-8d43519f5214------2</link>
            <guid isPermaLink="false">https://medium.com/p/332180ba3242</guid>
            <category><![CDATA[salesforce-productivity]]></category>
            <category><![CDATA[sfdx]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-development]]></category>
            <category><![CDATA[visual-studio-code]]></category>
            <dc:creator><![CDATA[Sachin Upmanyu]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 19:32:14 GMT</pubDate>
            <atom:updated>2020-07-13T19:32:14.517Z</atom:updated>
            <content:encoded><![CDATA[<p>Traditionally Salesforce Development has been done over Eclipse or Developer Console, and version control has been tricky to setup.</p><p>SFDX was made generally available in Oct 2017, and since then it has come a long way. With SFDX, we now have the choice and flexibility to choose our Development tools.</p><p><strong>Briefly, what is SFDX</strong></p><ul><li>It is a set of Tools to facilitate modern development practice.</li><li>SFDX CLI: Enables you to move away from Traditional IDEs(Eclipse, Developer Console) and use other popular IDEs (Visual Studio Code, Illuminated Cloud).</li><li>Scratch Orgs: Instead of creating Sandboxes for development, create short-term Salesforce environment to develop new features, run CI / CD pipelines.</li></ul><p>If you are looking to setup your Salesforce development environment around SFDX, and introducing some automation to make your life easier, this post might be helpful for you.</p><p>We will be looking to setup</p><ul><li><strong>SFDX CLI</strong> → To manage scratch orgs, push/retrieve code changes from org.</li><li><strong>Visual Studio Code → </strong>This is where we’ll write our code, ditch Developer Console.</li><li><strong>Rollbar Integration for Apex →</strong>Monitor handled/unhandled exceptions, helps in debugging.</li><li><strong>Slack Integrations for GitLab, Rollbar →</strong>Slack will be our hub for notifications.</li></ul><h4><strong>Setting up the CLI</strong></h4><p>First, Go through Official Documentation and Prerequisites for understanding and installing SFDX CLI.</p><ul><li><a href="https://trailhead.salesforce.com/en/content/learn/modules/sfdx_app_dev/sfdx_app_dev_setup_dx">Trailhead Module</a></li><li><a href="https://developer.salesforce.com/docs/atlas.en-us.224.0.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm">Before you begin</a></li><li><a href="https://developer.salesforce.com/docs/atlas.en-us.224.0.sfdx_setup.meta/sfdx_setup/sfdx_setup_install_cli.htm#sfdx_setup_install_cli">Installation Guide</a></li></ul><ol><li>Mainly there are 2 ways you can utilise SFDX CLI for development, with sandboxes or with Scratch Orgs.</li><li>If you want to create 2nd generation packages, or setup automated testing with CI pipeline, you’ll be needing Scratch Orgs and will need to enable Dev Hub for this (check “Before you begin” link).</li><li>If you are unable to provide licenses, you’ll need to give up on Scratch Orgs and instead use Sandboxes for development.</li></ol><h4><strong>Setting up Visual Studio Code:</strong></h4><p>But first, Prerequisites.</p><ol><li><strong>Install Git</strong></li></ol><ul><li>Windows: <a href="https://git-scm.com/download/win">https://git-scm.com/download/win</a></li><li>Ubuntu: sudo apt install git git-gui</li></ul><blockquote>git-gui is a minimalistic GUI tool, remove if not needed.</blockquote><p>2. <strong>Install Java 8 </strong>: needed for running the Apex Language Server</p><p><em>Windows:</em></p><ul><li><a href="https://java.com/en/download/help/windows_manual_download.xml">Download Link</a></li><li>Set Java Home: setx -m JAVA_HOME “C:\Progra~1\Java\jdk1.8.0_XX”</li></ul><blockquote>Imp: Cross check the path if it actually exists and points to correct directory before setting path</blockquote><ul><li>Check if Java Home has been set correctly echo %JAVA_HOME%</li></ul><p><em>Linux(Ubuntu):</em></p><ul><li><a href="https://drive.google.com/file/d/1eT-iFtsviykP5RFzoU6X-kedMSEqLg0l/view?usp=sharing">Download this Google Drive folder (241 MB)</a></li><li>Install Dependency: sudo apt install unzip</li><li>Extract folder and CD into it.</li><li>Make the install script executable: sudo a+x install-java.sh</li><li>Run the installation script: sudo ./install-java.sh -f jdk-8u241-linux-x64.tar.gz</li><li><a href="https://www.linuxuprising.com/2019/02/install-any-oracle-java-jdk-version-in.html">Check the complete guide by “Logix”</a> (steps taken from here).</li><li>Check if Java Home is set correctly: echo $JAVA_HOME</li></ul><blockquote>If JAVA_HOME is not set, follow next steps</blockquote><ul><li>Open the bashrc file for editing: nano ~/.bashrc</li><li>Add this line in end: export JAVA_HOME=/usr/lib/jvm/jdk1.8.0_241</li></ul><blockquote>Imp: Cross check the path if it actually exists and points to correct directory before adding to .bashrc</blockquote><ul><li>Reload the file for changes to take effect: source ~/.bashrc</li><li>If you run into any other installation issues, <a href="https://developer.salesforce.com/tools/vscode/en/troubleshooting#set-your-java-version">refer to this guide</a>.</li></ul><p>3. <strong>Download &amp; Install </strong><a href="https://code.visualstudio.com/"><strong>Visual Studio Code</strong></a></p><p>4. <strong>Setup Extensions</strong></p><ul><li>Easiest method for doing a vanilla setup is to install <a href="https://marketplace.visualstudio.com/items?itemName=salesforce.salesforcedx-vscode">this extension pack</a>.</li><li>Second method(which i personally prefer) would be to setup a master Visual Studio Code configuration with <a href="https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync">“Settings Sync” extension</a>.</li></ul><p>Settings Sync has advantage of creating a master configuration tailored for your particular project which can be shared and enforced on other dev machines. For example, you can control which extensions are installed in dev machines, their configurations, user settings &amp; keyboard shortcuts.</p><p>Run these commands to check if all tools have been installed successfully.</p><ol><li>$ sfdx</li><li>$ git --help</li><li>$ echo $JAVA_HOME // <em>for Linux</em></li><li>$ echo %JAVA_HOME% // <em>for Windows</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tOSr56l3UoJXkFc6jJs9gQ.gif" /><figcaption>Check if executables are properly setup</figcaption></figure><h3><strong>Rollbar Integration for Apex</strong></h3><ul><li>Get real-time error notifications with stack traces for Apex.</li><li>You’ll need to create an account for Rollbar and can start with a free plan with 5000 events per month limit.</li><li><a href="https://docs.rollbar.com/docs/salesforce-apex">Check Integration guide</a> with Salesforce on how to setup.</li><li>After this you’ll be able to write custom log messages to Rollbar.</li></ul><pre>try {</pre><pre>...</pre><pre>} catch (Exception exc) {</pre><pre>    rollbar.Rollbar.log(exc);</pre><pre>}</pre><ul><li><em>Pro tip</em> : put unique strings with your logs for easy searching.</li></ul><p>for example: rollbar.Rollbar.log(&#39;Logger_XcEr6T7y: Logging Custom Message&#39;);</p><h3>Slack Integrations</h3><p>Slack is a great collaboration tool, it provides integrations with many third party tools, and creates an eco-system where all your alerts/notifications can accumulate at a single place.</p><p>For starters, we are integrating GitLab &amp; Rollbar.</p><p><strong>Integrate GitLab:</strong></p><ul><li>To get updates for any git activity (get instant notifications for push, CI/CD pipeline updates, Issue, MR updates).</li><li>Create a separate channel for your project’s GitLab updates.</li><li><a href="https://docs.gitlab.com/ee/user/project/integrations/slack.html">Check Official Implementation Guide</a>.</li></ul><p><strong>Integrate Rollbar:</strong></p><ul><li>Get instant crash, handled/unhandled exception notification in Slack.</li><li>Again, it’s better to create a separate channel in Slack for these alerts.</li><li><a href="https://docs.rollbar.com/docs/slack">Check Official Implementation Guide</a>.</li></ul><p>Additionally, you can look to integrate SonarQube with your CI/CD pipeline for static code analysis.</p><p>While this post doesn’t cover all the topics in depth, I hope this will give an idea and help setup your Salesforce development environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=332180ba3242" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>