Factor identity examples into single template

* Factor multi-region example into distinct "concept" folder

Author: ccushing

docs/examples/concepts/multi_region/availability_domains.tf

@@ -0,0 +1,34 @@
+/*
+ * This example file demonstrates how to read AD values from multiple regions and employ filters
+ * to isolate specific ADs.
+ */
+
+data "oci_identity_availability_domains" "ad-phx" {
+  compartment_id = "${var.tenancy_ocid}"
+
+  filter {
+    name = "name"
+    values = ["\\w*-AD-1"]
+    regex = true
+  }
+}
+
+data "oci_identity_availability_domains" "ad-iad" {
+  provider = "oci.iad"
+  compartment_id = "${var.tenancy_ocid}"
+
+  filter {
+    name = "name"
+    values = ["\\w*-AD-1"]
+    regex = true
+  }
+}
+
+
+output "ad-phx" {
+  value = "${data.oci_identity_availability_domains.ad-phx.availability_domains}"
+}
+
+output "ad-iad" {
+  value = "${data.oci_identity_availability_domains.ad-iad.availability_domains}"
+}

docs/examples/concepts/multi_region/provider.tf

@@ -0,0 +1,29 @@
+/*
+ * This example file shows how to configure multiple oci providers to target different regions. 
+ */
+
+// These variables would commonly be defined as environment variablbe or sourced in a .env file 
+variable "tenancy_ocid" {}
+variable "user_ocid" {}
+variable "fingerprint" {}
+variable "private_key_path" {}
+variable "compartment_ocid" {}
+
+// This provider has no alias and consequently will be used by resources that do not specify an alias 
+provider "oci" {
+  region = "us-phoenix-1"
+  tenancy_ocid = "${var.tenancy_ocid}"
+  user_ocid = "${var.user_ocid}"
+  fingerprint = "${var.fingerprint}"
+  private_key_path = "${var.private_key_path}"
+}
+
+// This provider defines an alias and is targetable by resources by including `provider = "oci.iad"`. 
+provider "oci" {
+  region = "us-ashburn-1"
+  alias = "iad"
+  tenancy_ocid = "${var.tenancy_ocid}"
+  user_ocid = "${var.user_ocid}"
+  fingerprint = "${var.fingerprint}"
+  private_key_path = "${var.private_key_path}"
+}

docs/examples/concepts/multi_region/readme.md

@@ -0,0 +1,12 @@
+    #     ___  ____     _    ____ _     _____
+    #    / _ \|  _ \   / \  / ___| |   | ____|
+    #   | | | | |_) | / _ \| |   | |   |  _|
+    #   | |_| |  _ < / ___ | |___| |___| |___
+    #    \___/|_| \_/_/   \_\____|_____|_____|
+***
+
+## Multi-Region Provider Configuration
+
+This example demonstrates how to:
+* Define multiple OCI providers targeting different regions
+* List and filter Availability Domains across regions

docs/examples/iam/ad_multi_region/ad_multi_region.tf

@@ -0,0 +1,19 @@
+/*
+ * This example file demonstrates how to read AD values from a region and employ filters
+ * to isolate specific ADs.
+ */
+
+
+data "oci_identity_availability_domains" "ads" {
+  compartment_id = "${var.tenancy_ocid}"
+
+  filter {
+    name = "name"
+    values = ["\\w*-AD-1"]
+    regex = true
+  }
+}
+
+output "ads" {
+  value = "${data.oci_identity_availability_domains.ads.availability_domains}"
+}

docs/examples/iam/compartment/compartment.tf

@@ -0,0 +1,25 @@
+/*
+ * This example file shows how to create a compartment or reference an existing compartment as a resource.
+ *
+ * Note: the compartment resource internally resolves name collisions and returns a reference to the preexisting
+ * compartment. Compartments can not be deleted, so removing a compartment resource from your .tf file will only
+ * remove it from your statefile.
+ */
+
+resource "oci_identity_compartment" "compartment1" {
+  name = "tf-example-compartment"
+  description = "compartment created by terraform"
+}
+
+data "oci_identity_compartments" "compartments1" {
+  compartment_id = "${oci_identity_compartment.compartment1.compartment_id}"
+
+  filter {
+    name = "name"
+    values = ["tf-example-compartment"]
+  }
+}
+
+output "compartments" {
+  value = "${data.oci_identity_compartments.compartments1.compartments}"
+}