Draft Resources

Overview

A draft resource in Clophi is a pre-configured, tested resource template designed to be deployable with minimal modification. Draft resources are the fastest way to create infrastructure in Clophi.

Drafts fall into two broad categories:

• General-purpose drafts cover the foundational building blocks of Azure infrastructure: for example, a virtual network with a default subnet, or a storage account with standard configuration.
• Scenario-specific drafts provides resource configurations for particular use cases: for example, a network interface pre-paired with a public IP, ready to attach to a VM that needs internet exposure.

Every draft Clophi ships has been tested against Azure and is ready to deploy once you provide the values specific to your environment.

Loading a Draft

Open a resource form and click to a draft from the drafts section.

The form populates with the draft's defaults, and the right tab loads two pieces of information alongside:

• The draft resource documentation, so you can investigate any property as you adjust it.
• The code tab, which shows the fundamental ARM configuration the draft is producing.

Required fields that you still need to provide are marked with prompts like **Please provide a name for Virtual Network**. Fill those in, adjust anything else you want to customize, and continue building out the rest of your infrastructure project.

Creating Custom Drafts

Drafts aren't limited to what Clophi ships. You can author your own draft resources from any configuration you've built, save them with a meaningful name and adequate documentation, and decide who in your organization can use them.

Visibility

Each draft you create has a visibility setting:

• Personal: Only you can view and load the draft. Use this for configurations you're iterating on or reusing across your own projects.
• Organization: Every member of your organization can view and load the draft and use it as the basis for their own designs.

Governance through shared drafts

Organization-wide drafts are how teams use Clophi to enforce standards. Publish a draft for a hardened storage account and your engineers start from your security baseline by default. Publish a draft for a cost-optimized App Service plan and your team picks up the pricing posture your finance partners agreed to. The same pattern applies to naming conventions, tagging, network isolation, or any other organizational practice you want to make the default rather than the exception.