|
20 | 20 | | Name | Required | Default | Description | |
21 | 21 | | ---- | -------- | ------- | ----------- | |
22 | 22 | | compartment_ocid | Y | | The target compartment OCID in which all provisioned resources will be created. | |
23 | | -| service_name | N | | Display name prefix for all generated resources. If not specified, this will be automatically generated. | |
| 23 | +| stack_display_name | N | | Display name prefix for all generated resources. If not specified, this will be automatically generated. | |
24 | 24 |
|
25 | | -## KMS Variables |
| 25 | +## Vault Variables |
26 | 26 | | Name | Required | Default | Description | |
27 | 27 | | ---- | -------- | ------- | ----------- | |
28 | 28 | | kms_key_id | Y | | The OCID for the encryption key used for the provided credentials. | |
29 | | -| kms_crypto_endpoint | Y | | The crypto endpoint for the KMS vault. | |
| 29 | +| kms_crypto_endpoint | Y | | The crypto endpoint for the vault. | |
| 30 | + |
| 31 | +## Notification Details |
| 32 | +| Name | Required | Default | Description | |
| 33 | +| ---- | -------- | ------- | ----------- | |
| 34 | +| notification_topic_id | N | | The target notification topic OCID to send events. | |
30 | 35 |
|
31 | 36 | ## Network Details |
32 | 37 | | Name | Required | Default | Description | |
33 | 38 | | ---- | -------- | ------- | ----------- | |
34 | 39 | | use_existing_vcn | N | false | Select this option to support deployment of Essbase components into an existing virtual cloud network (VCN). | |
35 | | -| existing_vcn_compartment_id | if `use_existing_vcn=true` | | The OCID the compartment containing the target VCN. | |
36 | 40 | | existing_vcn_id | if `use_existing_vcn=true` | | An existing VCN in which to create the compute resources. | |
37 | | -| existing_application_subnet_compartment_id | if `use_existing_vcn=true` | | The compartment containing the target application subnet. | |
38 | 41 | | existing_application_subnet_id | if `use_existing_vcn=true` | | An existing subnet for the target Essbase instance. | |
39 | | -| existing_bastion_subnet_compartment_id | if `use_existing_vcn=true` | | The compartment containing the target bastion subnet. | |
40 | 42 | | existing_bastion_subnet_id | if `use_existing_vcn=true` | | An existing subnet for creating the bastion host | |
41 | | -| existing_load_balancer_subnet_compartment_id | Y, if `use_existing_vcn=true` | | The compartment containing the target load balancer subnets. | |
42 | 43 | | existing_load_balancer_subnet_id | if `use_existing_vcn=true` | | An existing subnet to use for the load balancer. | |
43 | 44 | | existing_load_balancer_subnet_id_2 | if `use_existing_vcn=true` | | An existing subnet to use for the second load balancer node. This field is required only if you are not using regional subnets. | |
44 | 45 | | vcn_cidr | N | 10.0.0.0/16 | The CIDR to assign to the new virtual cloud network (VCN) to create for this service. | |
| 46 | +| vcn_dns_label | N | | The DNS label to assign to the VCN. If not provided, the value will be randomly generated. | |
45 | 47 | | application_subnet_cidr | N | 10.0.1.0/24 | The CIDR to assign to the subnet for the target Essbase compute node. This will be created as a regional subnet. | |
46 | 48 | | bastion_subnet_cidr | N | 10.0.3.0/24 | The CIDR to assign to the subnet for the bastion host. This will be created as a regional subnet. | |
47 | 49 | | load_balancer_subnet_cidr | N | 10.0.4.0/24 | The CIDR to assign to the subnet for the load balancer. This will be created as regional subnet. | |
48 | | -| create_private_application_subnet | N | false | Create a private subnet for the Essbase node. A bastion host will be also created. | |
49 | 50 |
|
50 | 51 | ## Load Balancer Details |
51 | 52 | | Name | Required | Default | Description | |
52 | 53 | | ---- | -------- | ------- | ----------- | |
53 | 54 | | create_load_balancer | N | false | Provision a load balancer in Oracle Cloud Infrastructure. The load balancer will be provisioned with a demo certificate. The use of demo certificate is not recommended for production workloads. | |
| 55 | +| create_public_load_balancer | N | true | Provision the load balancer with a public IP address. | |
54 | 56 | | load_balancer_shape | N | 100Mbps | Select which load balancer shape. | |
55 | 57 |
|
56 | 58 | ## Bastion Details |
57 | 59 | | Name | Required | Default | Description | |
58 | 60 | | ---- | -------- | ------- | ----------- | |
59 | | -| bastion_instance_shape | N | VM.Standard.E2.1 | The shape for the bastion compute instance. | |
| 61 | +| create_bastion | N | false | Create a bastion host. | |
| 62 | +| bastion_instance_shape | if `create_bastion=true` | VM.Standard.E2.1 | The shape for the bastion compute instance. | |
| 63 | +| bastion_availability_domain | if `create_bastion=true` | | The target availability domain for the bastion. | |
60 | 64 |
|
61 | 65 | ## Essbase instance details |
62 | 66 | | Name | Required | Default | Description | |
63 | 67 | | ---- | -------- | ------- | ----------- | |
64 | 68 | | instance_shape | N | VM.Standard2.4 | The shape for the Essbase compute instance. | |
65 | 69 | | instance_availability_domain | Y | | Availability domain in region | |
66 | | -| ssh_public_key | Y | | Use the corresponding private key to access the Essbase compute instance. | |
| 70 | +| instance_hostname_label_prefix | N | | Prefix for the hostname label to which the compute instance will be assigned. If not provided, a randomly generated value will be used. | |
| 71 | +| ssh_authorized_keys | Y | | Use the corresponding private key to access the Essbase compute instance. | |
67 | 72 | | data_volume_size | N | 1024 | Define the target size of the data volume, which stores the Essbase application data. | |
68 | | -| config_volume_size | N | 512 | Define the target size of the configuration volume, which stored the Essbase system data, such as logs. | |
| 73 | +| config_volume_size | N | 64 | Define the target size of the configuration volume, which stored the Essbase system data, such as logs. | |
| 74 | +| temp_volume_size | N | 64 | Defined the target size of runtime temporary data. | |
69 | 75 | | essbase_admin_username | N | admin | The name of the Essbase system administrator. | |
70 | | -| essbase_admin_password_encrypted | Y | | The password for the Essbase system administrator, encrypted with the provided KMS key. Use a password that starts with a letter, is between 8 and 30 characters long, contains at least one number, and, optionally, any number of the special characters (`$` `#` `_`). For example, `Ach1z0#d`. | |
| 76 | +| essbase_admin_password_encrypted | Y | | The password for the Essbase system administrator, encrypted with the provided vaule key. Use a password that starts with a letter, is between 8 and 30 characters long, contains at least one number, and, optionally, any number of the special characters (`$` `#` `_`). For example, `Ach1z0#d`. | |
71 | 77 | | rcu_schema_prefix | N | | Schema prefix to use when running RCU. A value with be automatically generated if not specified. | |
72 | | -| assign_instance_public_ip | N | true | If the subnet allows for a public ip address, assign one to the Essbase instance. | |
| 78 | +| create_public_essbase_instance | N | false | Create the Essbase compute instance with a public IP address. | |
| 79 | +| enable_essbase_monitoring | N | false | If enabled, the Essbase compute instance will emit telemetry data to the OCI Monitoring service. | |
| 80 | +| enable_embedded_proxy | N | true | Expiremental: If disabled, the Essbase compute instance will not enable an Apache http proxy for IDCS integration. | |
73 | 81 |
|
74 | 82 | ## Security Details |
75 | 83 | | Name | Required | Default | Description | |
76 | 84 | | ---- | -------- | ------- | ----------- | |
77 | 85 | | security_mode | N | idcs | Choose embedded LDAP or integration with Identity Cloud Service (IDCS). The use of embedded LDAP is not recommended for production workloads. | |
78 | | -| idcs_client_tenant | if `security_mode=idcs` | | The ID of your Identity Cloud Service instance, which typically has the format idcs-<guid>, and is part of the host name that you use to access Identity Cloud Service. | |
| 86 | +| idcs_tenant | if `security_mode=idcs` | | The ID of your Identity Cloud Service instance, which typically has the format idcs-<guid>, and is part of the host name that you use to access Identity Cloud Service. | |
79 | 87 | | idcs_client_id | if `security_mode=idcs` | | The client ID for the IDCS application. | |
80 | | -| idcs_client_secret_encrypted | if `security_mode=idcs` | | The client secret for the IDCS application, encrypted with the provided KMS key. | |
| 88 | +| idcs_client_secret_encrypted | if `security_mode=idcs` | | The client secret for the IDCS application, encrypted with the provided vault key. | |
81 | 89 | | idcs_external_admin_username | if `security_mode=idcs` | | A user id to be registered as an Essbase administrator. This user must exist in the provided Identity Cloud Service instance. | |
82 | 90 |
|
83 | 91 | ## Database Details |
84 | 92 | | Name | Required | Default | Description | |
85 | 93 | | ---- | -------- | ------- | ----------- | |
86 | 94 | | use_existing_db | N | false | Select this option to enable support of an existing database for the internal Essbase repository. | |
87 | 95 | | existing_db_type | N | Autonomous Database | Select which database you will use | |
88 | | -| existing_db_compartment_id | N | | Target database compartment | |
89 | 96 | | existing_db_id | N | | Target ATP database in which to create the Essbase schema. | |
90 | | -| db_admin_password_encrypted | if `existing_db_type=Autonomous Database` | | The password for the database administrator, encrypted with the provided KMS key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$` `#` `_`). For example, `BEstr0ng_#12`. | |
| 97 | +| db_admin_password_encrypted | if `existing_db_type=Autonomous Database` | | The password for the database administrator, encrypted with the provided vault key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$` `#` `_`). For example, `BEstr0ng_#12`. | |
91 | 98 | | db_license_model | N | LICENSE_INCLUDED | | |
92 | | -| existing_oci_db_system_id | N | | Target database system in which to create the Essbase schema. | |
93 | | -| existing_oci_db_system_dbhome_id | N | | The database home within the DB System | |
94 | 99 | | existing_oci_db_system_database_id | N | | The database within the DB System in which to create the Essbase schema. | |
95 | 100 | | existing_oci_db_system_database_pdb_name | N | | The name of the pdb in the target database. Required if not using the default pdb created during database provision. | |
96 | 101 | | oci_db_admin_username | N | SYS | The username for the database administrator. | |
97 | | -| oci_db_admin_password_encrypted | if `existing_db_type=OCI` | | The password for the database administrator, encrypted with the provided KMS key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$` `#` `_`). For example, `BEstr0ng_#12`. | |
| 102 | +| oci_db_admin_password_encrypted | if `existing_db_type=OCI` | | The password for the database administrator, encrypted with the provided vault key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$` `#` `_`). For example, `BEstr0ng_#12`. | |
0 commit comments