CMR-11422: Comment and documentation

Author: eudoroolivares2016

ingest-app/docs/api.md

@@ -173,6 +173,8 @@ The following fields are validated:
 
 **Note**: if cmr-validate-keywords header is not set explicitly, it will behave as if it was set to FALSE by default behind the scenes
 
+**Note**: cmr-validate-keywords is being deprecated by provider to prevent ESDIS providers from using it and thus putting stale keywords onto the system
+
 **Note**: that when multiple fields are present the combination of keywords are validated to match a known combination.
 
 **Note**: Among the validation fields above, [Platforms], [Instruments], [Projects], [Science Keywords], [Location Keywords] and [Data Centers] are also validated when the `Cmr-Validate-Keywords` header is not set to `true` except that  validation errors will be returned to users as warnings.

ingest-app/src/cmr/ingest/api/collections.clj

@@ -25,6 +25,8 @@
   "Returns a map of validation options with boolean values"
   [headers provider-id]
   (let [validate-keywords-value
+        ;; There is a temporary carveout for the KMS API itself until we resolve the cache delay issue either by removing the CMR cache entirely 
+        ;; or having KMS issue a cache refresh to CMR see CMR-11524.
         (if (and (not (contains? headers SEND_KMS_METADATA_FIXER_HEADER))
                  (contains? (set (ingest-config/keyword-enforced-providers)) provider-id))
           true