Remove references to unused attachment command

Remove: Remove references to unused attachment command

Author: akfakmot

Migration.Tool.CLI/README.md

@@ -45,7 +45,7 @@ To perform the migration:
 Command usage:
 
 ```powershell
-Migration.Tool.CLI.exe migrate --sites --custom-modules --users --members --forms --media-libraries --attachments --page-types --pages --settings-keys --contact-management --data-protection
+Migration.Tool.CLI.exe migrate --sites --custom-modules --users --members --forms --media-libraries --page-types --pages --settings-keys --contact-management --data-protection
 ```
 
 | Parameter                   | Description                                                                                                                                                                                                                                                                                                                                                                             | Dependencies                                   |
@@ -60,7 +60,6 @@ Migration.Tool.CLI.exe migrate --sites --custom-modules --users --members --form
 | `--pages`                   | Enables migration of [pages](https://docs.kentico.com/x/AQqRBg). Pages can be migrated either to [website channel pages](https://docs.kentico.com/x/JwKQC) (default behavior) or [reusable content items](https://docs.kentico.com/x/content_items_xp) in Content hub. <br /><br />When migrating to website channel pages, the target instance must not contain pages other than those created by previous runs of the Kentico Migration Tool. <br /><br />See: [Migration details for specific object types - Pages](#pages)                                                                                                     | `--sites`, `--users`, `--page-types`           |
 | `--type-restrictions`       | Enables migration of [content type restrictions](https://docs.kentico.com/x/bw2RBg).                                                                                                                                                                                           | `--sites`, `--pagetypes`, `--pages`            |
 | `--categories`              | Enables migration of categories to taxonomies. Xperience by Kentico uses a different approach to categorization. Categories are migrated to [taxonomies](https://docs.kentico.com/x/taxonomies_xp) and selected categories for each page are assigned to pages in the target instance via a [reusable field schema](https://docs.kentico.com/x/D4_OD). See [`Categories`](#categories). | `--sites`, `--users`, `--pagetypes`, `--pages` |
-| `--attachments`             | Enables migration of page attachments to Content hub as [content item assets](https://docs.kentico.com/x/content_item_assets_xp) (page attachments are not supported in Xperience by Kentico).<br /><br />See: [Migration details for specific object types - Attachments](#attachments)                                                                                                                | `--sites`, `--custom-modules`                  |
 | `--contact-management`      | Enables migration of [contacts](https://docs.xperience.io/x/nYPWCQ) and [activities](https://docs.xperience.io/x/oYPWCQ). The target instance must not contain any contacts or activities. May run for a long time depending on the number of contacts in the source database.                                                                                                          | `--users`, `--custom-modules`                  |
 | `--data-protection`         | Enables migration of [consents](https://docs.xperience.io/x/zoB1CQ) and consent agreements.                                                                                                                                                                                                                                                                                             | `--sites`, `--users`, `--contact management`   |
 | `--forms`                   | Enables migration of [forms](https://docs.xperience.io/x/WAKiCQ) and submitted form data.<br /><br />See: [Migration details for specific object types - Forms](#forms)                                                                                                                                                                                                                 | `--sites`, `--custom-modules`, `--users`       |
@@ -815,7 +814,6 @@ By default, media libraries and attachments are migrated as content item assets
 - The media library contains folders matching the content tree structure for all pages with attachments (including empty folders for parent pages without attachments). The folders are named after the _node alias_ of the source pages.
 - Each page's folder directly contains all unsorted attachments (files added on the _Attachments_ tab in the source's _Pages_ application).
 - Attachments stored in specific page fields are placed into subfolders, named in format: _"\_\_fieldname"_. These subfolders can include multiple files for fields of the _Attachments_ type, or a single file for _File_ type fields.
-- Any "floating" attachments without an associated page are migrated into the media library root folder.
 - The migration does not include temporary attachments (created when a file upload is not finished correctly). If any are present on the source instance, a warning is logged in the [migration protocol](./MIGRATION_PROTOCOL_REFERENCE.md).
 
 The following is an example of a media library created by the Kentico Migration Tool for page attachments:

Migration.Tool.Extensions/DefaultMigrations/AssetMigration.cs

@@ -51,7 +51,7 @@ public async Task<FieldMigrationResult> MigrateValue(object? sourceValue, FieldM
 
         if (!invokedCommands.Commands.Any(x => x is MigrateMediaLibrariesCommand))
         {
-            logger.LogError($"Trying to migrate asset field value {{FieldName}}, but commands {MigrateMediaLibrariesCommand.Moniker} and {MigrateAttachmentsCommand.Moniker} were not invoked", fieldName);
+            logger.LogError($"Trying to migrate asset field value {{FieldName}}, but command {MigrateMediaLibrariesCommand.Moniker} was not invoked", fieldName);
             return new(false, null);
         }