WDT 3.0 Doc Updates (#1340)

* updating docs for WDT-689

* updating docs for WDT-706

* for remote online update doc changes

* update for -remote option

* update Slack URL

* Move RCU doc (#1363)

* Move RCU doc

* update the description

* Update RNs (#1364)

Update RNs and move previously existing RN content.

* start on 3.0 release notes so far

* adding deprecation logging to the 3.0 release notes

* Documentation for verrazzano section of model

* Update Model Help Tool (#1373)

* Add doc for archive helper (#1372)

* updating release notes

* updating 3.0 rel;ease notes with changes up to yesterday

* minor edit

* completing release notes for WDT 3.0

* fixing typo

* fixing previous error

* another typo

---------

Co-authored-by: Johnny Shum <[email protected]>
Co-authored-by: Rosemary Marano <[email protected]>
Co-authored-by: Richard Killen <[email protected]>

Author: 4 people

documentation/2.0/.vscode/settings.json renamed to documentation/3.0/.vscode/settings.json

@@ -15,6 +15,7 @@ weight: 1
 - [Model semantics](#model-semantics)
 - [Declaring named MBeans to delete](#declaring-named-mbeans-to-delete)
 - [Using multiple models](#using-multiple-models)
+- [Upgrading from WDT 1.x to WDT 2.x YAML files](#upgrading-from-wdt-1x-to-wdt-2x-yaml-files)
 
 ### Overview
 
@@ -264,7 +265,7 @@ In addition to deleting named mbeans, you can remove items from a list. Most pra
   JMSSystemResource:
       BPMJMSModule:
           Target: soa_cluster,'!AdminServer'
-              
+
 ```
 In this example, the BPMJMSModule has the AdminServer target removed from the target list.
 
@@ -360,3 +361,53 @@ topology:
             ListenPort: 7000
             Notes: Server 1
 ```
+
+### Upgrading from WDT 1.x to WDT 2.x YAML files
+
+Beginning in 2.0, WebLogic Deploy Tooling now incorporates the SnakeYAML parser for reading and writing model files.
+This may require some changes to existing models in order to be parsed correctly.
+   - Model elements that use [delete notation]({{< relref "/concepts/model#declaring-named-mbeans-to-delete" >}}) need to be escaped in single or double quotation marks.
+   ```yaml
+   topology:
+       Server:
+           '!ms1':
+           ms2:
+   ```
+
+
+   - Model elements under the same parent should be indented to the exact same level. The previous YAML parser did not enforce this restriction,
+   but it is standard for YAML. In this example, each cluster is indented four spaces.
+   ```yaml
+   topology:
+       Cluster:
+           cluster1:
+               ClientCertProxyEnabled: True
+           cluster2:
+               WeblogicPluginEnabled: true
+   ```
+
+
+
+- Object lists in the `kubernetes` section of the model now should be specified in a hyphenated list format,
+similar to how they appear in the domain resource file produced for [WebLogic Kubernetes Operator](https://oracle.github.io/weblogic-kubernetes-operator/managing-domains/domain-resource/).
+
+   ```yaml
+       clusters:
+       - clusterName: 'cluster1'
+         allowReplicasBelowMinDynClusterSize: true
+       - clusterName: 'cluster2'
+         allowReplicasBelowMinDynClusterSize: true
+   ```
+
+   - The "named object list" format is deprecated now, and will cause warning messages to be displayed.
+   ```yaml
+       clusters:
+         'cluster1':
+           allowReplicasBelowMinDynClusterSize: true
+         'cluster2':
+           allowReplicasBelowMinDynClusterSize: true
+   ```
+
+
+- The deprecated argument `-model_sample` has been removed from the Model Help Tool.
+The Model Help Tool has used model sample format, by default, since release 1.9.2.

documentation/2.0/archetypes/default.md renamed to documentation/3.0/archetypes/default.md

@@ -136,7 +136,13 @@ This key element specifies which method should be used for retrieving the value
 
 #### `access`
 
-By default, an attribute is read write in both WLST and MODEL. This element is used to set an attribute to read-only. The two read-only attributes are `RO` and `ROD`. The latter indicates that the attribute is read-only and will not be written into the domain. However, it will be discovered by the Discover Domain Tool into the model.
+By default, an attribute is read write in both WLST and MODEL. This element is used to set an attribute to read-only
+or ignored.  The two attribute values are:
+
+- `RO`       indicates that the attribute is read-only and will not be written into the domain; however, it will be
+             discovered and written into the model by the Discover Domain Tool.
+- `IGNORED`  indicates that the attribute is both known and tolerated in the model but is never discovered or written
+             into the domain.
 #### `preferred_model_type`
 
 This key element specifies the preferred data type that should be used to put data in the model during discovery. As an example, list values can be represented in the model as comma-separated text, such as `"value1, value2"`, or as a YAML list, such as `["value1", "value2"]`. If the list values can contain commas, a YAML list must be used.