IBM Cloud Terraform Provider

The flow_job_data block provides details about the execution of a Flow, including its ID, name, and the specific workitems involved in the job.

Workitems and Sources

Each workitem contains a source_type and a source defining where the templates or playbooks originate.

Supported source_type values: local, git_hub, git_hub_enterprise, git_lab, ibm_git_lab, ibm_cloud_catalog, external_scm, cos_bucket.

Git Source Configuration

If the source_type is a Git provider, the git block allows configuration via:

• git_repo_url: The URL to clone.
• git_token: Personal Access Token.
• git_branch: The branch to fetch.
• git_release: The release tag to fetch.
• git_repo_folder: The specific folder within the repo containing the template.
• computed_git_repo_url: The fully computed URL (read-only).

# Conceptual structure of flow_job_data
flow_job_data {
  flow_id   = "flow-123"
  flow_name = "deployment-flow"

  workitems {
    command_object_name = "provision-layer"
    source_type         = "git_hub"
    source {
      source_type = "git_hub"
      git {
        git_repo_url    = "https://github.com/org/repo"
        git_token       = "ghp_token"
        git_branch      = "main"
        git_repo_folder = "templates/provision"
      }
    }
  }
}

The ibm_dns_domain_registration_nameservers resource manages the custom name servers associated with a DNS domain registration. By default, when a domain is registered, it uses IBM Cloud name servers. Using this resource replaces those default name servers with custom values.

This resource is primarily used to hand over DNS management from the standard IBM Cloud DNS Registration Service to IBM Cloud Internet Services (CIS). To enable CIS for a domain, you must update the domain registration with the specific name servers provided by your CIS resource instance. This is a prerequisite for the domain in CIS to become active and serve web traffic.

resource "ibm_dns_domain_registration_nameservers" "dnstestdomain" {
    dns_registration_id = data.ibm_dns_domain_registration.dnstestdomain.id
    name_servers = ibm_cis_domain.dnstestdomain.name_servers 
}

data "ibm_dns_domain_registration" "dnstestdomain" {
    name = "dnstestdomain.com"
}

resource "ibm_cis_domain" "dnstestdomain" {
   
}

You can control which objects (such as volumes or specific resources) are included or excluded during backup/recovery operations using include_params or exclude_params. Both blocks use a similar schema to define filters based on labels or specific resource identities.

Label-based Filtering

Use the label_vector to specify objects by their labels.

• label_combination_method (String): Determines how labels are evaluated. Allowable values: AND, OR.
• label_vector (List): A two-dimensional array where each inner array contains a key and a value representing a label.

Resource-based Filtering

Use selected_resources to target specific Kubernetes-style resources.

• api_group (String): The API group (e.g., apps, kubevirt.io).
• kind (String): The resource kind (e.g., VirtualMachine).
• resource_list (List): A list of specific instances, where each instance contains:
  • entity_id (Integer): The specific entity ID.
  • name (String): The name of the entity.
  • version (String): The API version (ignored during recovery selection).

The ibm_is_backup_policy_plan data source exposes several complex nested structures:

clone_policy

Used to manage snapshot clones.

• max_snapshots (Integer): Maximum number of recent snapshots to keep per source.
• zones (List): List of zones where snapshot clones will be created.

deletion_trigger

Defines how backups are removed.

• delete_after (Integer): Maximum number of days to keep each backup after creation.
• delete_over_count (Integer): Maximum number of recent backups to keep. If absent, there is no maximum.

remote_region_policy

Defines cross-region backup rules.

• region (Required, String): The globally unique name of the target region.
• delete_over_count (Optional, Integer): Maximum number of recent remote copies to keep in this region.
• encryption_key (Optional, String): The CRN of the Key Protect Root Key or Hyper Protect Crypto Services Root Key to use for rewrapping the data encryption key. If unspecified, the source's encryption_key is used.

The ibm_is_instance_group_manager resource is used to manage the scaling behavior of an IBM Cloud VPC Instance Group. It can be used to create autoscale managers (using policies) or scheduled managers (using actions).

To build a complete scalable infrastructure, you typically use this resource in conjunction with:

• ibm_is_instance_group: To create the underlying instance group.
• ibm_is_instance_group_manager_policy: To define scaling rules (e.g., CPU utilization) for autoscale managers.
• ibm_is_instance_group_manager_action: To define specific scaling events for scheduled managers.
• ibm_is_lb and ibm_is_lb_pool: To distribute traffic across the instances managed by the group.

import "github.com/IBMCloud/terraform-provider-ibm"

# Note: This is a conceptual relationship of resources
resource "ibm_is_instance_group" "example" {
  name = "my-instance-group"
}

resource "ibm_is_instance_group_manager" "example" {
  instance_group_id = ibm_is_instance_group.example.id
  # Configuration for autoscale or scheduled management
}