Development

Decoding the Error: StatusCode=0 "ReferencedResourceNotProvisioned" in Azure

22 December 2018

Introduction # If you’re working with Azure, you might have encountered an error that looks something like this: “Failure sending request: StatusCode=0 — Original Error: Code=‘ReferencedResourceNotProvisioned’ Message=‘Cannot proceed with operation because resource used by resource is not in Succeeded state. Resource is in Updating state and the last operation that updated/is updating the resource is PutSubnetOperation.’” Though the error message can seem intimidating and cryptic at first, don’t worry. In this post, we’ll delve into what this error means and how you can resolve it. ...

Navigating Terraform Modules Stored in Package Subdirectories

24 October 2018

In the realm of Infrastructure as Code, Terraform modules can play a significant role in making your life easier. Sometimes, however, these modules don’t live at the root directory of their source package. Instead, they reside in sub-directories. Thankfully, Terraform has a smart way to help you access these nested modules. Terraform employs a unique double-slash (//) syntax to help pinpoint the exact sub-directory where the module is located. The path that follows this double-slash syntax is considered to be a sub-directory within the package or repository. ...

How to Fix the "RPC failed; HTTP 413 curl 22" Error in Nginx

12 October 2018

Understanding the Issue: ‘RPC failed; HTTP 413 curl 22’ # If you’ve stumbled upon the error message “RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 Request Entity Too Large,” you’re probably trying to push a rather hefty commit over HTTP to your server running Nginx. This error means that the size of the request you’re trying to send exceeds the limit that the server is willing to accept. ...

Install ruby gem files

27 September 2018

Install the gems on the destination machine from the local files: cd /path/to/gems gem install --force --local *.gem

The Cart Before the Horse - A DevOps Conundrum

26 September 2018

We’ve all heard the age-old saying: putting the cart before the horse. Unfortunately, in the world of DevOps, this is happening far more often than it should, and it’s time we talk about it. The crux of the issue is that, too often, the focus isn’t on solving actual problems; it’s on utilizing shiny new technologies. Picture this: A developer stumbles upon a cutting-edge piece of technology. They’re immediately enamored by its features, its capabilities, the way it’s touted as the ’next big thing. ...