Resources and data sources

View in Terraform Registry

The Azion Terraform Provider v2.0 configures the Azion Platform with two kinds of block. A resource creates, updates, and deletes an object on Azion, and a data source queries information about objects that already exist. A singular name such as azion_workload is often both a resource and the data source that reads one object, and its plural, azion_workloads, is the data source that lists them.

Each section below covers one product: its resources, its data sources, and a configuration block that uses them. Every name links its Terraform Registry page.

Workloads

These resources and data sources manage workloads and their deployments. For more information, refer to Workloads resources.

Resource	Description
`azion_workload`	Creates and manages a workload.
`azion_workload_deployment`	Creates and manages a workload deployment.

Data source	Description
`azion_workloads`	Lists workloads.
`azion_workload`	Reads one workload.
`azion_workload_deployments`	Lists workload deployments.
`azion_workload_deployment`	Reads one deployment.

This block creates a workload and a deployment of it, then queries the existing workloads:

HCL

01# Create a workload

02resource "azion_workload" "example" {

03 name = "my-workload"

05 application_id = azion_application_main_setting.app.id

07 active = true

08}

10# Create a deployment

11resource "azion_workload_deployment" "example" {

12 workload_id = azion_workload.example.id

14 active = true

15}

17# Query existing workloads

18data "azion_workloads" "all" {}

Connectors

These resources and data sources manage connectors, which link an application to an external origin. For more information, refer to Connectors resources.

Resource	Description
`azion_connector`	Creates and manages a connector.

Data source	Description
`azion_connectors`	Lists connectors.
`azion_connector`	Reads one connector.

This block creates a connector to an HTTPS origin, then queries the existing connectors:

HCL

01# Create a connector

02resource "azion_connector" "example" {

03 name = "my-connector"

05 origin = {

06 address = "origin.example.com"

07 protocol = "https"

08 }

09}

11# Query existing connectors

12data "azion_connectors" "all" {}

Applications

These resources and data sources manage applications and their settings: cache settings, device groups, Rules Engine rules, and function instances. For more information, refer to Applications resources.

Resource	Description
`azion_application_main_setting`	Creates and manages the main settings of an application.
`azion_application_cache_setting`	Creates and manages a cache setting.
`azion_application_device_group`	Creates and manages a device group.
`azion_application_rule_engine`	Creates and manages a Rules Engine rule.
`azion_application_functions_instance`	Creates and manages a function instance in an application.

Data source	Description
`azion_application_main_settings`	Queries the main settings of applications.
`azion_application_cache_settings`	Lists cache settings.
`azion_application_cache_setting`	Reads one cache setting.
`azion_application_device_groups`	Lists device groups.
`azion_application_device_group`	Reads one device group.
`azion_application_rules_engine`	Lists Rules Engine rules.
`azion_application_rule_engine`	Reads one Rules Engine rule.
`azion_application_functions_instances`	Lists function instances.
`azion_application_functions_instance`	Reads one function instance.

This block creates an application and a cache setting that honors the cache policy of the origin:

HCL

01# Create an Application

02resource "azion_application_main_setting" "app" {

03 name = "my-application"

05 active = true

06}

08# Configure cache

09resource "azion_application_cache_setting" "cache" {

10 application_id = azion_application_main_setting.app.id

11 name = "cache-default"

13 browser_cache_settings = "honor"

14 cdn_cache_settings = "honor"

15}

Edge DNS

These resources and data sources manage Edge DNS zones, records, and DNSSEC. The names keep the intelligent_dns form that the provider uses. For more information, refer to Edge DNS resources.

Resource	Description
`azion_intelligent_dns_zone`	Creates and manages a DNS zone.
`azion_intelligent_dns_record`	Creates and manages a DNS record.
`azion_intelligent_dns_dnssec`	Manages the DNSSEC settings of a zone.

Data source	Description
`azion_intelligent_dns_zones`	Lists DNS zones.
`azion_intelligent_dns_zone`	Reads one DNS zone.
`azion_intelligent_dns_records`	Lists DNS records.
`azion_intelligent_dns_dnssec`	Reads the DNSSEC settings of a zone.

This block creates a zone and an A record in it, then queries the existing zones:

HCL

01# Create a DNS zone

02resource "azion_intelligent_dns_zone" "zone" {

03 name = "example.com"

04 domain = "example.com"

06 active = true

07}

09# Create a DNS record

10resource "azion_intelligent_dns_record" "www" {

11 zone_id = azion_intelligent_dns_zone.zone.id

12 name = "www"

13 type = "A"

14 ttl = 3600

16 value = "192.0.2.1"

17}

19# Query existing DNS zones

20data "azion_intelligent_dns_zones" "all" {}

Security

These resources and data sources manage firewalls, their Rules Engine rules and function instances, Web Application Firewall (WAF) settings, and network lists. For more information, refer to Security resources.

Resource	Description
`azion_firewall_main_setting`	Creates and manages the main settings of a firewall.
`azion_firewall_rule_engine`	Creates and manages a Rules Engine rule of a firewall.
`azion_firewall_functions_instance`	Creates and manages a function instance in a firewall.
`azion_network_list`	Creates and manages a network list.
`azion_waf`	Creates and manages a WAF.
`azion_waf_rule_set`	Creates and manages a WAF rule set.

Data source	Description
`azion_firewall_main_settings`	Lists firewalls.
`azion_firewall_main_setting`	Reads one firewall.
`azion_firewall_rules_engine`	Lists the Rules Engine rules of firewalls.
`azion_firewall_rule_engine`	Reads one Rules Engine rule of a firewall.
`azion_firewall_function_instances`	Lists the function instances of firewalls.
`azion_firewall_functions_instance`	Reads one function instance of a firewall.
`azion_network_lists`	Lists network lists.
`azion_network_list`	Reads one network list.
`azion_wafs`	Lists WAFs.
`azion_waf`	Reads one WAF.
`azion_waf_rule_sets`	Lists WAF rule sets.
`azion_waf_rule_set`	Reads one WAF rule set.

This block creates a firewall in waf mode and a network list of two IP ranges:

HCL

01# Create a Firewall

02resource "azion_firewall_main_setting" "firewall" {

03 name = "my-firewall"

05 active = true

06 mode = "waf"

07}

09# Create a Network List

10resource "azion_network_list" "allowlist" {

11 name = "allowlist-ips"

12 list_type = "ip_cidr"

14 items = [

15 "192.0.2.0/24",

16 "10.0.0.0/8"

17 ]

18}

Certificates

These resources and data sources manage digital certificates. For more information, refer to Certificates resources.

Resource	Description
`azion_digital_certificate`	Creates and manages a digital certificate.

Data source	Description
`azion_digital_certificates`	Lists digital certificates.
`azion_digital_certificate`	Reads one digital certificate.

This block creates a certificate from a certificate file and a private key file in the module folder, then queries the existing certificates:

HCL

01# Create a certificate

02resource "azion_digital_certificate" "cert" {

03 name = "my-certificate"

05 certificate = file("${path.module}/cert.pem")

06 private_key = file("${path.module}/key.pem")

07}

09# Query existing certificates

10data "azion_digital_certificates" "all" {}

Functions

This resource and these data sources manage Functions. No reference page of the provider covers them.

Resource	Description
`azion_function`	Creates and manages a function.

Data source	Description
`azion_functions`	Lists functions.
`azion_function`	Reads one function.

Custom pages

This resource and these data sources manage custom pages. No reference page of the provider covers them.

Resource	Description
`azion_custom_page`	Creates and manages a custom page.

Data source	Description
`azion_custom_pages`	Lists custom pages.
`azion_custom_page`	Reads one custom page.

Complete example

This configuration pins the provider to version 2.0.0 and creates an application with a cache setting, a connector, a workload with a deployment, and a firewall. It outputs the IDs of the application, the workload, and the connector, and reads your personal token from the api_token variable that the Azion Terraform Provider quickstart declares.

HCL

01terraform {

02 required_providers {

03 azion = {

04 source = "aziontech/azion"

05 version = "2.0.0"

06 }

07 }

08}

10provider "azion" {

11 api_token = var.api_token

12}

14# Application

15resource "azion_application_main_setting" "app" {

16 name = "my-application"

17 active = true

18}

20# Cache Setting

21resource "azion_application_cache_setting" "cache" {

22 application_id = azion_application_main_setting.app.id

23 name = "cache-default"

24 browser_cache_settings = "honor"

25 cdn_cache_settings = "honor"

26}

28# Connector

29resource "azion_connector" "origin" {

30 name = "my-origin"

31 origin = {

32 address = "origin.example.com"

33 protocol = "https"

34 }

35}

37# Workload

38resource "azion_workload" "main" {

39 name = "my-workload"

40 application_id = azion_application_main_setting.app.id

41 active = true

42}

44# Workload Deployment

45resource "azion_workload_deployment" "main" {

46 workload_id = azion_workload.main.id

47 active = true

48}

50# Firewall

51resource "azion_firewall_main_setting" "firewall" {

52 name = "my-firewall"

53 active = true

54 mode = "waf"

55}

57# Outputs

58output "application_id" {

59 value = azion_application_main_setting.app.id

60}

62output "workload_id" {

63 value = azion_workload.main.id

64}

66output "connector_id" {

67 value = azion_connector.origin.id

68}

Azion Terraform Provider

What the provider manages and how it reaches the Azion API.

Azion Terraform Provider quickstart

Install Terraform, configure the provider and your token, and apply a first configuration.

Terraform Provider best practices

How to organize code, store state, protect secrets, and pin provider versions.

Migrate from provider v1.x to v2.0

The resources v2.0 removes, renames, and adds, and how to move a v1.x configuration to it.