Update creating repository sections in Content Management Guide

Additional options for managing file content with Pulp 3 required changes to procedures

[doc] Manage File Content with Pulp3

https://issues.redhat.com/browse/SAT-3109

guides/common/assembly_managing-custom-file-type-content.adoc

@@ -2,14 +2,14 @@
 = Managing {customfiletypetitle} Content
 
 In {Project}, you might require methods of managing and distributing SSH keys and source code files or larger files such as virtual machine images and ISO files.
-To achieve this, (customproduct)s in {ProjectName} include repositories for {customfiletype}s.
+To achieve this, {customproduct}s in {ProjectName} include repositories for {customfiletype}s.
 This provides a generic method to incorporate arbitrary files in a product.
 
 You can upload files to the repository and synchronize files from an upstream {ProjectServer}.
 When you add files to a {customfiletype} repository, you can use the normal {Project} management functions such as adding a specific version to a Content View to provide version control and making the repository of files available on various {SmartProxyServer}s.
 Clients must download the files over HTTP or HTTPS using `curl -O`.
 
-You can create a file type repository in {ProjectServer} only in a (customproduct), but there is flexibility in how you create the file type repository.
+You can create a file type repository in {ProjectServer} only in a {customproduct}, but there is flexibility in how you create the file type repository.
 You can create an independent file type repository in a directory on the system where {Project} is installed, or on a remote HTTP server, and then synchronize the contents of that directory into {Project}.
 This method is useful when you have multiple files to add to a {Project} repository.
 

guides/common/modules/proc_creating-a-custom-file-type-repository.adoc

@@ -10,7 +10,7 @@ To use the CLI instead of the {ProjectWebUI}, see the xref:cli-creating-a-custom
 
 To create a {customproduct}, complete the following procedure:
 
-. In the {ProjectWebUI}, navigate to *Content* > *Products*, click *Create Product* and enter the following details:
+. In the {ProjectWebUI}, navigate to *Content* *>* *Products*, click *Create Product*, and enter the following details:
 . In the *Name* field, enter a name for the product.
 {Project} automatically completes the *Label* field based on what you have entered for *Name*.
 . Optional: From the *GPG Key* list, select the GPG key for the product.
@@ -30,6 +30,18 @@ To create a repository for your {customproduct}, complete the following procedur
 Clear this field if the repository does not require authentication.
 . In the *Upstream Password* field, enter the corresponding password for the upstream repository.
 Clear this field if the repository does not require authentication.
+. Optional: In the *Upstream Authentication Token* field, provide the token of the upstream repository user for authentication.
+Leave this field empty if the repository does not require authentication.
+. Optional: Check the *Mirror on Sync* checkbox to have this repository mirror the source repository during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *HTTP Proxy Policy* field, select the desired HHTP proxy.
+The default value is `Global Default`.
+. Optional: Check the *Publish via HTTP* to have this repository published using HTTP during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *GPG Key* field, select the GPG key for the repository.
+. Optional: In the *SSL CA Cert* field, select the SSL CA Certificate for the repository.
+. Optional: In the *SSL Client cert* field, select the SSL Client Certificate for the repository.
+. Optional: In the *SSL Client Key* field, select the SSL Client Key for the repository.
 . Click *Save*.
 
 [id="cli-creating-a-custom-file-type-repository_{context}"]

guides/common/modules/proc_creating-a-local-file-repository.adoc

@@ -25,7 +25,7 @@ endif::[]
 +
 [options="nowrap" subs="+quotes,attributes"]
 ----
-# {package-install-project} python-pulp-manifest
+# {package-install-project} python3-pulp_manifest
 ----
 . Create a directory that you want to use as the file type repository in the HTTP server's public folder:
 +
@@ -68,6 +68,18 @@ To import files from a file type repository in a local directory, complete the f
 . Select the *Verify SSL* check box to check the SSL certificate for the repository or clear the *Verify SSL* check box.
 . Optional: In the *Upstream Username* field, enter the upstream user name that you require.
 . Optional: In the *Upstream Password* field, enter the corresponding password for your upstream user name.
+. Optional: In the *Upstream Authentication Token* field, provide the token of the upstream repository user for authentication.
+Leave this field empty if the repository does not require authentication.
+. Optional: Check the *Mirror on Sync* checkbox to have this repository mirror the source repository during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *HTTP Proxy Policy* field, select the desired HHTP proxy.
+The default value is `Global Default`.
+. Optional: Check the *Publish via HTTP* to have this repository published using HTTP during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *GPG Key* field, select the GPG key for the repository.
+. Optional: In the *SSL CA Cert* field, select the SSL CA Certificate for the repository.
+. Optional: In the *SSL Client cert* field, select the SSL Client Certificate for the repository.
+. Optional: In the *SSL Client Key* field, select the SSL Client Key for the repository.
 . Select *Save* to save this repository entry.
 
 .Updating a File Type Repository

guides/common/modules/proc_creating-a-remote-file-repository.adoc

@@ -38,7 +38,7 @@ endif::[]
 +
 [options="nowrap" subs="+quotes"]
 ----
-# yum install python-pulp-manifest
+# yum install python3-pulp_manifest
 ----
 . Create a directory that you want to use as the file type repository in the HTTP server's public folder:
 +
@@ -84,6 +84,18 @@ For more information see xref:Creating_a_Custom_File_Type_Repository_{context}[]
 Clear this field if the repository does not require authentication.
 . In the *Upstream Password* field, enter the corresponding password for the upstream repository.
 Clear this field if the repository does not require authentication.
+. Optional: In the *Upstream Authentication Token* field, provide the token of the upstream repository user for authentication.
+Leave this field empty if the repository does not require authentication.
+. Optional: Check the *Mirror on Sync* checkbox to have this repository mirror the source repository during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *HTTP Proxy Policy* field, select the desired HHTP proxy.
+The default value is `Global Default`.
+. Optional: Check the *Publish via HTTP* to have this repository published using HTTP during synchronization.
+It defaults to `true` (checked).
+. Optional: In the *GPG Key* field, select the GPG key for the repository.
+. Optional: In the *SSL CA Cert* field, select the SSL CA Certificate for the repository.
+. Optional: In the *SSL Client cert* field, select the SSL Client Certificate for the repository.
+. Optional: In the *SSL Client Key* field, select the SSL Client Key for the repository.
 . Click *Save*.
 . To update the file type repository, navigate to *Content* > *Products*.
 Select the name of a product that contains the repository that you want to update.