Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cloudeval.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use this path when you want to review infrastructure before deployment, share a template-backed workspace with a teammate, or skip live cloud credentials for the first pass. CloudEval’s strongest infrastructure-as-code path today is Azure ARM JSON. If your source of truth is Bicep, compile it to ARM JSON first and import the generated file.

​
What works today

  • Local ARM template file upload
  • ARM template URL
  • Parameters file upload
  • Parameters file URL
  • GitHub template URLs from the Azure Quickstart repo and similar public repos
If you provide a GitHub template URL, CloudEval can try to auto-detect a matching parameters file from the same repository when the naming pattern is recognizable.

​
Create a project from ARM JSON

1

Open the quick project flow

Open Projects, then select Create project.The dialog walks through three steps:
  • Project Details
  • Review & Create
  • Success
2

Add project details

Start with a project name, optional description, and cloud provider.Azure is the practical choice today for ARM and Bicep-backed imports.
3

Choose the template source

Paste a real template URL into Template URL. For example:
https://github.com/Azure/azure-quickstart-templates/blob/master/quickstarts/microsoft.compute/1vm-2nics-2subnets-1vnet/azuredeploy.json
CloudEval accepts common GitHub template URL shapes, including blob, tree, and raw GitHub content URLs.When the URL points at GitHub, the dialog also tries to find a matching parameters file automatically. You will see one of these states beside Parameters (optional):
  • Looking…
  • Found
  • Not found
If CloudEval finds one, it shows Auto-detected parameters file. You can still replace it with your own Parameters file URL (optional).
4

Review and create

The review step shows the selected Template Source as either:
  • File: <filename>
  • URL: <template-url>
After you choose Review & Create, CloudEval creates the project and starts setting up the backing connection in the background.
CloudEval stores the imported source, project metadata, and report outputs together so the whole review stays in one workspace.
CloudEval workspace showing imported ARM JSON, project files, report history, and source outline

​
Why this path is useful

  • Avoids live credential setup.
  • Works well for pre-deployment reviews.
  • Makes GitHub-hosted templates and local files behave like the same project workflow.

​
Next step

Use Create a project from a GitHub URL for the focused browser flow, run your first reports, or move to Review IaC before deployment for a fuller end-to-end workflow.
Last modified on May 5, 2026