Skip to content

Commit 195f24a

Browse files
authored
Update KnownBehaviour.md
1 parent 8803ed8 commit 195f24a

File tree

1 file changed

+23
-11
lines changed

1 file changed

+23
-11
lines changed

cd3_automation_toolkit/documentation/user_guide/KnownBehaviour.md

Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -56,10 +56,7 @@
5656

5757
The service api is designed in such a way that it expects an empty list for match all. And it sends back an empty list in the response every time. Hence this behaviour from terraform side. This can be safely ignored.
5858

59-
- Export process for non greenfield tenancies v6.0 or higher doesn't support OCI objects having duplicate names like for Policies, for VCNs having same names with in a region or subnets having same names within a VCN. You will get output similiar to below when terraform plan is run (Option 3 with non-gf_tenancy set to true)
60-
61-
***_Error: Duplicate resource "oci_identity_policy" configuration_***
62-
59+
6360
- Export process for non greenfield tenancies v6.0 or higher will try to revert SGW for a VCN to point to all services if it was existing for just object storage. You will get output similiar to below when terraform plan is run (Option 3 with non-gf_tenancy set to true).
6461

6562
```
@@ -104,13 +101,28 @@
104101
}
105102
```
106103

107-
### Modification Process
108-
- When there is a change to any of the instance parameters, the volume policy assignment will get recreated. Example: If you want to add a NSG to the instance, you will be notified on a read to the boot volume ocids, modification to the instance and, a create and destruction of the policy assignment. Screenshot below for reference. This behaviour is expected and in order to not have the backup policy recreated, comment the depends_on statement in modules/compute/data.tf at line around 35.
109-
110-
![image](https://user-images.githubusercontent.com/122371432/214506185-58c8702f-de87-4fb1-8a29-1a7623b699c4.png)
111-
112-
<br><br>
113-
<div align='center'>
104+
- If the description field is having any newlines in the tenancy then the export of the compoennt and tf synch will show output similair to below:
105+
106+
```
107+
# module.iam-policies[“ConnectorPolicy_notifications_2023-03-06T21-54-41-655Z”].oci_identity_policy.policy will be updated in-place
108+
~ resource “oci_identity_policy” “policy” {
109+
~ description = <<-**EOT**
110+
This policy is created for the ‘OCI_To_Sentinel’ service connector
111+
Date: Mon, 06 Mar 2023 21:54:41 GMT
112+
User: oracleidentitycloudservice/[email protected]
113+
Tenant: test
114+
Connection Source: notifications
115+
**EOT**
116+
id = “ocid1.policy.oc1..aaaaaaaa5gct2n6vz4arggmeow27rivu5vro6jjb6ccuq5u2phulghgwx”
117+
name = “ConnectorPolicy_notifications_2023-03-06T21.54.41.655Z”
118+
# (9 unchanged attributes hidden)
119+
# (1 unchanged block hidden)
120+
}
121+
Plan: 0 to add, 1 to change, 0 to destroy.
122+
```
123+
124+
This is how terraform handles newlines in the fields. Pleage ignore this and proceed with terraform apply.
125+
114126

115127
| <a href="/cd3_automation_toolkit/documentation/user_guide/RestructuringOutDirectory.md">:arrow_backward: Prev</a> | <a href="/cd3_automation_toolkit/documentation/user_guide/FAQ.md">Next :arrow_forward:</a> |
116128
| :---- | -------: |

0 commit comments

Comments
 (0)