docs: Removed Docs for regional content

Signed-off-by: Stefan Genov <[email protected]>

docs/versions/latest/Components/Archetypes/vRA 8.x/General/Content.md

@@ -16,15 +16,6 @@ By default the `content.yaml` looks like this.
 ```yaml
 blueprint:
 subscription:
-flavor-mapping:
-  - small
-  - medium
-image-mapping:
-storage-profile:
-region-mapping:
-  cloud-account-tags:
-    export-tag: "env:dev"
-    import-tags: ["env:dev", "env:test"]
 custom-resource:
 resource-action:
 catalog-entitlement:
@@ -51,8 +42,6 @@ Contents are exported by different rules.
   - subscription
   - policies
 
-Importing regional content doesn't use the `content.yaml` when pushing content it is working as previously pushes whatever there is the package.
-
 #### Export Rules for content types
 
 - Empty array [] - nothing is exported  
@@ -67,40 +56,13 @@ Importing regional content doesn't use the `content.yaml` when pushing content i
   - subscription
   - policies
 
-#### Exporting regional content
-
-To export regional content, cloud account(s) with given tag(s) should be given.
-
-- Empty array [] - nothing is exported  
-- List of items - the given items are exported in all regions linked to cloud accounts with given tag.
-
-  If they are added to the manifest, but not present on the server - they are skipped.
-
-- Null (nothing given) - everything is being exported in all regions linked to cloud accounts with given tag  
-  - flavor-mapping
-  - image-mapping
-  - storage-profile
-
-#### Export all content in all regions linked to cloud accounts with given tag
-
-To export all content in all regions linked to cloud accounts, the tag for export should be defined. If not defined, nothing will be exported.
-
 #### Examples
 
 Example of `content.yaml` file.
 
 ```yaml
 blueprint: # will export all 
 subscription: # will export all 
-flavor-mapping: # only "small" and "meduim" will be exported in all regions linked to cloud accounts with given tag 
-  - small
-  - medium
-image-mapping: [] # nothing will be exported 
-storage-profile: [] # nothing will be exported 
-region-mapping:  # export only items linked to cloud accounts with given tags 
-  cloud-account-tags:
-    export-tag: "env:dev"
-    import-tags: ["env:dev", "env:test"]
 catalog-item:  # export according to filter
   - Project Blueprints__WindowsVM
   - Project Blueprints__LinuxVm

docs/versions/latest/Components/Archetypes/vRA 8.x/General/Core Concepts.md

@@ -65,27 +65,6 @@ The catalog items in the vRA Service Broker consists of different type of conten
 
 Blueprint type catalog items have different versions that corelate to the released versions of the Blueprints. Only the current version of the latest blueprint version is targeted.
 
-### Regional Content
-
-The vRA 8.x philosophy is built around the concept of infrastructure definition capable of resource provisioning - compute, network, storage and other types of resources - that builds up an abstract model for resource description. This allows workload placement to happen dynamically based on various explicit or implicit rules. Part of this abstract model is the definition of various mappings and profiles that provide common higher-level definitions of underlying infrastructure objects. These definitions take the form of various mappings and profiles:
-
-- flavor mappings - common designation of compute resource t-shirt or other sizing
-- image mappings - common designation of VM images
-- storage profiles - a set of storage policies and configurations used for workload placement
-- network profiles - a set of network-related configurations used for network resource placement
-
-These abstractions are related to the regions within the cloud accounts and their capabilities. They utilize the various underlying resources which are automatically collected and organized into "fabrics" by vRA. As such, they contain information about resources in the various connected regions and for the purpose of this project are collectively called **regional content**.
-
-Exporting (pulling) and importing (pushing) of regional content is achieved using a mapping definition specified in the content manifest (content.yaml): `region-mappping`. It contains a set of mapping criteria used for exporting and importing of content. The vRA-NG package manager handles the `export-tag` and `import-tags` entries of the `cloud-account-tags` section of `region-mapping`.
-
-#### Export Regional Content
-
-When exporting regional content defined in the respective content categories - `image-mapping`, `flavor-mapping`, `storage-profile`, etc., the vRA-NG package manager takes into account the tag that is defined in the `export-tag` entry and exports content that is related to a cloud account(s) containing this tag. The content is stored in a directory within a unique regional directory bearing the name of the cloud account and the cloud zone id. The cloud account and zone combination are persisted for reference to the originating environment.
-
-#### Import Regional Content
-
-The vRA-NG package manager uses the `import-tags` entry from the content manifest (content.yaml) to (re)create regional content targeting cloud accounts that contain one or more of the import tags. The content is taken from all of the regional folders and regardless of its origin, it is imported to the target environment based on the `import-tags`, i.e. related to cloud accounts possessing one or more of the import tags list.
-
 [//]: # (Optional Section)
 [//]: # (## Previous:)
 

docs/versions/latest/Components/Archetypes/vRA 8.x/General/Getting Started.md

@@ -68,15 +68,6 @@ catalog
             └── ABX Action.yaml       
         └── subscriptions
             └── subscription.json
-        └── regions
-            └── cloud-account-name~region-id
-                └── flavor-mappings
-                    └── small.json
-                └── image-mappings
-                    └── mapping.json
-                └── storage-profiles
-                    └── profile.json
-                └── src-region-profile.json
         └── custom-resources
             └── customResource.json
         └── resource-actions

docs/versions/latest/Components/Archetypes/vRA 8.x/General/Known Issues.md

@@ -4,9 +4,7 @@ A list of known vRA 8.x archetype issues
 
 ## Table Of Contents
 
-1. [Custom Resources Known Issues](../Components/Custom%20Resources.md#known-issues)
-2. [Blueprints Known Issues](../Components/Blueprints.md#known-issues)
-3. [All Local Data Is Pushed](#all-local-data-is-pushed-to-vra)
+1. [All Local Data Is Pushed](#all-local-data-is-pushed-to-vra)
 
 ### All local data is pushed to vRA
 

docs/versions/latest/Components/Archetypes/vRA 8.x/README.md

@@ -10,9 +10,6 @@ Supported content:
 
 - `blueprint`
 - `subscription`
-- `flavor-mapping`
-- `image-mapping`
-- `storage-profile`
 - `custom-resource`
 - `catalog-entitlement`
 - `catalog-item`