RubyGems - emass_client - Versions diffs - 3.12.0 → 3.22.0 - Mend

emass_client 3.12.0 → 3.22.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (212) hide show

data/lib/emass_client/api/artifacts_api.rb CHANGED Viewed

@@ -1,12 +1,12 @@
 =begin
 #Enterprise Mission Assurance Support Service (eMASS)
-#The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC:
+#The eMASS Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.  The eMASS API provides an interface for application to communicate eMASS Services. For information on how to register and use the eMASS API reference the [eMASS API Getting Started](eMASSGettingStarted.md).  Additional information about eMASS can be obtain by contacting the National Industrial Security Program (NISP). Points of Contact are:
-The version of the OpenAPI document: v3.12
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
+The version of the OpenAPI document: v3.22
+Contact: disa.global.servicedesk.mbx.ma-ticket-request@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.1.0-SNAPSHOT
+Generator version: 7.12.0-SNAPSHOT
 =end
@@ -20,31 +20,31 @@ module EmassClient
       @api_client = api_client
     end
     # Add one or many artifacts in a system
-    # <strong>Information</strong><br> The body of a request through the Artifacts POST endpoint accepts a single binary file. Two  Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within  an eMASS system will be enforced by the API for both methods. <br><br> For POST requests that should result in a single artifact, the request should include the file. <br><br> For POST requests that should result in the creation of many artifacts, the request should include  a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This  .zip file should contain one or more files corresponding to existing artifacts or new artifacts that  will be created upon successful receipt. <br><br> Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact  existing within the application, the file associated with the artifact will be updated. If no artifact  is matched via filename to the application, a new artifact will be created with the following  default values. Any values not specified below will be null <ul>   <li>isTemplate: false</li>   <li>type: Other</li>   <li>category: Evidence</li> </ul> To update values other than the file itself, please submit a PUT request.<br>  <strong>Business Rules</strong><br> Artifact cannot be saved if the fields below exceed the following character limits: <ul>   <li>Filename - 1,000 characters</li>   <li>Name - 100 characters</li>   <li>Description - 10,000 characters</li>   <li>Reference Page Number - 50 characters</li> </ul> Artifact cannot be saved if the file does not have an allowable file extension/type:      .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt,     .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg,     .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx  Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system.  Artifact cannot be saved if the file size exceeds 30MB.  Artifact cannot be saved if the following fields are missing data: <ul>   <li>Filename (filename)</li>   <li>Type (type)</li>   <li>Category (category)</li> </ul>  Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future.
+    # <strong>Information About Adding Artifacts</strong><br>  The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods. <br><br> For POST requests that should result in a single artifact, the request should include the file. <br><br> For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. <br><br> Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null <ul>   <li>isTemplate: false</li>   <li>type: Other</li>   <li>category: Evidence</li> </ul>  To update values other than the file itself, please submit a PUT request.<br>  <strong>Business Rules</strong><br>  Artifact cannot be saved if the fields below exceed the following character limits: <ul>   <li>Filename - 1,000 characters</li>   <li>Name - 100 characters</li>   <li>Description - 10,000 characters</li>   <li>Reference Page Number - 50 characters</li> </ul>  Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system.  Artifact cannot be saved if the file size exceeds 30MB.  Artifact cannot be saved if the following fields are missing data: <ul>   <li>Filename (filename)</li>   <li>Type (type)</li>   <li>Category (category)</li> </ul> Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param zipper [File]
+    # @param filename [File] The file to upload. Must be a .zip file if isBulk is set to true, otherwise any acceptable artifact file. Max 30MB per artifact.
     # @param [Hash] opts the optional parameters
-    # @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected.  When set to true, a .zip file is expected which  can contain multiple artifact files\&quot;  (default to false)
-    # @option opts [Boolean] :is_template
-    # @option opts [String] :type
-    # @option opts [String] :category
+    # @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files.  (default to false)
+    # @option opts [Boolean] :is_template Is the artifact a template?  Indicates whether an artifact is a template
+    # @option opts [String] :type The type of artifact. Possible values are:  Procedure, Diagram, Policy, Labor, Document, Image, Other, Scan Result, Auditor Report. May also accept custom artifact type values set by system administrators.
+    # @option opts [String] :category The category of artifact. Possible values are:  Implementation Guidance, Evidence.  May also accept custom artifact category values set by system administrators.
     # @return [ArtifactsResponsePutPost]
-    def add_artifacts_by_system_id(system_id, zipper, opts = {})
-      data, _status_code, _headers = add_artifacts_by_system_id_with_http_info(system_id, zipper, opts)
+    def add_artifacts_by_system_id(system_id, filename, opts = {})
+      data, _status_code, _headers = add_artifacts_by_system_id_with_http_info(system_id, filename, opts)
       data
     end
     # Add one or many artifacts in a system
-    # &lt;strong&gt;Information&lt;/strong&gt;&lt;br&gt; The body of a request through the Artifacts POST endpoint accepts a single binary file. Two  Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within  an eMASS system will be enforced by the API for both methods. &lt;br&gt;&lt;br&gt; For POST requests that should result in a single artifact, the request should include the file. &lt;br&gt;&lt;br&gt; For POST requests that should result in the creation of many artifacts, the request should include  a single file with the extension \&quot;.zip\&quot; only and the parameter isBulk should be set to true. This  .zip file should contain one or more files corresponding to existing artifacts or new artifacts that  will be created upon successful receipt. &lt;br&gt;&lt;br&gt; Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact  existing within the application, the file associated with the artifact will be updated. If no artifact  is matched via filename to the application, a new artifact will be created with the following  default values. Any values not specified below will be null &lt;ul&gt;   &lt;li&gt;isTemplate: false&lt;/li&gt;   &lt;li&gt;type: Other&lt;/li&gt;   &lt;li&gt;category: Evidence&lt;/li&gt; &lt;/ul&gt; To update values other than the file itself, please submit a PUT request.&lt;br&gt;  &lt;strong&gt;Business Rules&lt;/strong&gt;&lt;br&gt; Artifact cannot be saved if the fields below exceed the following character limits: &lt;ul&gt;   &lt;li&gt;Filename - 1,000 characters&lt;/li&gt;   &lt;li&gt;Name - 100 characters&lt;/li&gt;   &lt;li&gt;Description - 10,000 characters&lt;/li&gt;   &lt;li&gt;Reference Page Number - 50 characters&lt;/li&gt; &lt;/ul&gt; Artifact cannot be saved if the file does not have an allowable file extension/type:      .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt,     .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg,     .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx  Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system.  Artifact cannot be saved if the file size exceeds 30MB.  Artifact cannot be saved if the following fields are missing data: &lt;ul&gt;   &lt;li&gt;Filename (filename)&lt;/li&gt;   &lt;li&gt;Type (type)&lt;/li&gt;   &lt;li&gt;Category (category)&lt;/li&gt; &lt;/ul&gt;  Artifact cannot be saved if the Last Review Date (&#x60;lastReviewedDate&#x60;) is set in the future.
+    # &lt;strong&gt;Information About Adding Artifacts&lt;/strong&gt;&lt;br&gt;  The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods. &lt;br&gt;&lt;br&gt; For POST requests that should result in a single artifact, the request should include the file. &lt;br&gt;&lt;br&gt; For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \&quot;.zip\&quot; only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. &lt;br&gt;&lt;br&gt; Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null &lt;ul&gt;   &lt;li&gt;isTemplate: false&lt;/li&gt;   &lt;li&gt;type: Other&lt;/li&gt;   &lt;li&gt;category: Evidence&lt;/li&gt; &lt;/ul&gt;  To update values other than the file itself, please submit a PUT request.&lt;br&gt;  &lt;strong&gt;Business Rules&lt;/strong&gt;&lt;br&gt;  Artifact cannot be saved if the fields below exceed the following character limits: &lt;ul&gt;   &lt;li&gt;Filename - 1,000 characters&lt;/li&gt;   &lt;li&gt;Name - 100 characters&lt;/li&gt;   &lt;li&gt;Description - 10,000 characters&lt;/li&gt;   &lt;li&gt;Reference Page Number - 50 characters&lt;/li&gt; &lt;/ul&gt;  Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system.  Artifact cannot be saved if the file size exceeds 30MB.  Artifact cannot be saved if the following fields are missing data: &lt;ul&gt;   &lt;li&gt;Filename (filename)&lt;/li&gt;   &lt;li&gt;Type (type)&lt;/li&gt;   &lt;li&gt;Category (category)&lt;/li&gt; &lt;/ul&gt; Artifact cannot be saved if the Last Review Date (&#x60;lastReviewedDate&#x60;) is set in the future.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param zipper [File]
+    # @param filename [File] The file to upload. Must be a .zip file if isBulk is set to true, otherwise any acceptable artifact file. Max 30MB per artifact.
     # @param [Hash] opts the optional parameters
-    # @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected.  When set to true, a .zip file is expected which  can contain multiple artifact files\&quot;  (default to false)
-    # @option opts [Boolean] :is_template
-    # @option opts [String] :type
-    # @option opts [String] :category
+    # @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files.  (default to false)
+    # @option opts [Boolean] :is_template Is the artifact a template?  Indicates whether an artifact is a template
+    # @option opts [String] :type The type of artifact. Possible values are:  Procedure, Diagram, Policy, Labor, Document, Image, Other, Scan Result, Auditor Report. May also accept custom artifact type values set by system administrators.
+    # @option opts [String] :category The category of artifact. Possible values are:  Implementation Guidance, Evidence.  May also accept custom artifact category values set by system administrators.
     # @return [Array<(ArtifactsResponsePutPost, Integer, Hash)>] ArtifactsResponsePutPost data, response status code and response headers
-    def add_artifacts_by_system_id_with_http_info(system_id, zipper, opts = {})
+    def add_artifacts_by_system_id_with_http_info(system_id, filename, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: ArtifactsApi.add_artifacts_by_system_id ...'
       end
@@ -52,17 +52,9 @@ module EmassClient
       if @api_client.config.client_side_validation && system_id.nil?
         fail ArgumentError, "Missing the required parameter 'system_id' when calling ArtifactsApi.add_artifacts_by_system_id"
       end
-      # verify the required parameter 'zipper' is set
-      if @api_client.config.client_side_validation && zipper.nil?
-        fail ArgumentError, "Missing the required parameter 'zipper' when calling ArtifactsApi.add_artifacts_by_system_id"
-      end
-      allowable_values = ["Procedure", "Diagram", "Policy", "Labor", "Document", "Image", "Other", "Scan Result", "Auditor Report", "unknown_default_open_api"]
-      if @api_client.config.client_side_validation && opts[:'type'] && !allowable_values.include?(opts[:'type'])
-        fail ArgumentError, "invalid value for \"type\", must be one of #{allowable_values}"
-      end
-      allowable_values = ["Implementation Guidance", "Evidence", "unknown_default_open_api"]
-      if @api_client.config.client_side_validation && opts[:'category'] && !allowable_values.include?(opts[:'category'])
-        fail ArgumentError, "invalid value for \"category\", must be one of #{allowable_values}"
+      # verify the required parameter 'filename' is set
+      if @api_client.config.client_side_validation && filename.nil?
+        fail ArgumentError, "Missing the required parameter 'filename' when calling ArtifactsApi.add_artifacts_by_system_id"
       end
       # resource path
       local_var_path = '/api/systems/{systemId}/artifacts'.sub('{' + 'systemId' + '}', CGI.escape(system_id.to_s))
@@ -74,7 +66,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['multipart/form-data'])
       if !content_type.nil?
@@ -83,7 +75,7 @@ module EmassClient
       # form parameters
       form_params = opts[:form_params] || {}
-      form_params['Zipper'] = zipper
+      form_params['filename'] = filename
       form_params['isTemplate'] = opts[:'is_template'] if !opts[:'is_template'].nil?
       form_params['type'] = opts[:'type'] if !opts[:'type'].nil?
       form_params['category'] = opts[:'category'] if !opts[:'category'].nil?
@@ -115,7 +107,7 @@ module EmassClient
     end
     # Remove one or many artifacts in a system
-    # Remove the Artifact(s) matching `systemId` path parameter and request body artifact(s) file name<br><br> <b>Note:</b> Multiple files can be deleted by providing multiple file names at the CL (comma delimited)  Example: --files file1.txt, file2.txt
+    # Remove the Artifact(s) matching `systemId` path parameter and request body artifact(s) file name<br><br>
     # @param system_id [Integer] **System Id**: The unique system record identifier.
     # @param artifacts_request_delete_body_inner [Array<ArtifactsRequestDeleteBodyInner>] Delete artifact files for the given System Id
     # @param [Hash] opts the optional parameters
@@ -126,7 +118,7 @@ module EmassClient
     end
     # Remove one or many artifacts in a system
-    # Remove the Artifact(s) matching &#x60;systemId&#x60; path parameter and request body artifact(s) file name&lt;br&gt;&lt;br&gt; &lt;b&gt;Note:&lt;/b&gt; Multiple files can be deleted by providing multiple file names at the CL (comma delimited)  Example: --files file1.txt, file2.txt
+    # Remove the Artifact(s) matching &#x60;systemId&#x60; path parameter and request body artifact(s) file name&lt;br&gt;&lt;br&gt;
     # @param system_id [Integer] **System Id**: The unique system record identifier.
     # @param artifacts_request_delete_body_inner [Array<ArtifactsRequestDeleteBodyInner>] Delete artifact files for the given System Id
     # @param [Hash] opts the optional parameters
@@ -152,7 +144,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['application/json'])
       if !content_type.nil?
@@ -235,7 +227,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # form parameters
       form_params = opts[:form_params] || {}
@@ -267,23 +259,23 @@ module EmassClient
     end
     # Update one or many artifacts in a system
-    # Updates an artifact for given `systemId` path parameter<br><br>  **Request Body Required Fields** - `filename` - `isTemplate` - `type` - `category`  <strong>Information</strong><br> The PUT request will replace all existing data with the field/value combinations included in the request body.   If any fields are not included, the absent fields will become null.     The fields `name` and `isTemplate` are non-nullable fields. If not specified in the PUT command they will default to the following:   - `name=filename`   - `isTemplate=false`    Also, note that one-to-many fields (`controls` and `ccis`) will also be replaced with the values specified in the PUT.  If existing `control or cci` mappings exist in eMASS, the values in the PUT will not append, but  rather replace all existing control and cci mappings with the values in the request body.
+    # Updates an artifact for given `systemId` path parameter<br><br> **Request Body Required Fields** - `filename` - `isTemplate` - `type` - `category`  The example request provides all optional fields  <strong>Information About Updating Artifacts</strong><br>  The PUT request will replace all existing data with the field/value combinations included in the request body.  If any fields are not included, the absent fields will become null.  The fields `name` and `isTemplate` are non-nullable fields. If not specified in the PUT command they will default to the following:   - `name=filename`   - `isTemplate=false`  Also, note that one-to-many fields (`controls` and `ccis`) will also be replaced with the values specified in the PUT.  If existing `control or cci` mappings exist in eMASS, the values in the PUT will not append, but rather replace all existing control and cci mappings with the values in the request body.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] See &#x60;information&#x60; above for additional instructions
+    # @param artifacts_required_fields [Array<ArtifactsRequiredFields>] See &#x60;information&#x60; above for additional instructions
     # @param [Hash] opts the optional parameters
     # @return [ArtifactsResponsePutPost]
-    def update_artifact_by_system_id(system_id, request_body, opts = {})
-      data, _status_code, _headers = update_artifact_by_system_id_with_http_info(system_id, request_body, opts)
+    def update_artifact_by_system_id(system_id, artifacts_required_fields, opts = {})
+      data, _status_code, _headers = update_artifact_by_system_id_with_http_info(system_id, artifacts_required_fields, opts)
       data
     end
     # Update one or many artifacts in a system
-    # Updates an artifact for given &#x60;systemId&#x60; path parameter&lt;br&gt;&lt;br&gt;  **Request Body Required Fields** - &#x60;filename&#x60; - &#x60;isTemplate&#x60; - &#x60;type&#x60; - &#x60;category&#x60;  &lt;strong&gt;Information&lt;/strong&gt;&lt;br&gt; The PUT request will replace all existing data with the field/value combinations included in the request body.   If any fields are not included, the absent fields will become null.     The fields &#x60;name&#x60; and &#x60;isTemplate&#x60; are non-nullable fields. If not specified in the PUT command they will default to the following:   - &#x60;name&#x3D;filename&#x60;   - &#x60;isTemplate&#x3D;false&#x60;    Also, note that one-to-many fields (&#x60;controls&#x60; and &#x60;ccis&#x60;) will also be replaced with the values specified in the PUT.  If existing &#x60;control or cci&#x60; mappings exist in eMASS, the values in the PUT will not append, but  rather replace all existing control and cci mappings with the values in the request body.
+    # Updates an artifact for given &#x60;systemId&#x60; path parameter&lt;br&gt;&lt;br&gt; **Request Body Required Fields** - &#x60;filename&#x60; - &#x60;isTemplate&#x60; - &#x60;type&#x60; - &#x60;category&#x60;  The example request provides all optional fields  &lt;strong&gt;Information About Updating Artifacts&lt;/strong&gt;&lt;br&gt;  The PUT request will replace all existing data with the field/value combinations included in the request body.  If any fields are not included, the absent fields will become null.  The fields &#x60;name&#x60; and &#x60;isTemplate&#x60; are non-nullable fields. If not specified in the PUT command they will default to the following:   - &#x60;name&#x3D;filename&#x60;   - &#x60;isTemplate&#x3D;false&#x60;  Also, note that one-to-many fields (&#x60;controls&#x60; and &#x60;ccis&#x60;) will also be replaced with the values specified in the PUT.  If existing &#x60;control or cci&#x60; mappings exist in eMASS, the values in the PUT will not append, but rather replace all existing control and cci mappings with the values in the request body.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] See &#x60;information&#x60; above for additional instructions
+    # @param artifacts_required_fields [Array<ArtifactsRequiredFields>] See &#x60;information&#x60; above for additional instructions
     # @param [Hash] opts the optional parameters
     # @return [Array<(ArtifactsResponsePutPost, Integer, Hash)>] ArtifactsResponsePutPost data, response status code and response headers
-    def update_artifact_by_system_id_with_http_info(system_id, request_body, opts = {})
+    def update_artifact_by_system_id_with_http_info(system_id, artifacts_required_fields, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: ArtifactsApi.update_artifact_by_system_id ...'
       end
@@ -291,9 +283,9 @@ module EmassClient
       if @api_client.config.client_side_validation && system_id.nil?
         fail ArgumentError, "Missing the required parameter 'system_id' when calling ArtifactsApi.update_artifact_by_system_id"
       end
-      # verify the required parameter 'request_body' is set
-      if @api_client.config.client_side_validation && request_body.nil?
-        fail ArgumentError, "Missing the required parameter 'request_body' when calling ArtifactsApi.update_artifact_by_system_id"
+      # verify the required parameter 'artifacts_required_fields' is set
+      if @api_client.config.client_side_validation && artifacts_required_fields.nil?
+        fail ArgumentError, "Missing the required parameter 'artifacts_required_fields' when calling ArtifactsApi.update_artifact_by_system_id"
       end
       # resource path
       local_var_path = '/api/systems/{systemId}/artifacts'.sub('{' + 'systemId' + '}', CGI.escape(system_id.to_s))
@@ -304,7 +296,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['application/json'])
       if !content_type.nil?
@@ -315,7 +307,7 @@ module EmassClient
       form_params = opts[:form_params] || {}
       # http body (model)
-      post_body = opts[:debug_body] || @api_client.object_to_http_body(request_body)
+      post_body = opts[:debug_body] || @api_client.object_to_http_body(artifacts_required_fields)
       # return_type
       return_type = opts[:debug_return_type] || 'ArtifactsResponsePutPost'

data/lib/emass_client/api/artifacts_export_api.rb CHANGED Viewed

@@ -1,12 +1,12 @@
 =begin
 #Enterprise Mission Assurance Support Service (eMASS)
-#The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC:
+#The eMASS Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.  The eMASS API provides an interface for application to communicate eMASS Services. For information on how to register and use the eMASS API reference the [eMASS API Getting Started](eMASSGettingStarted.md).  Additional information about eMASS can be obtain by contacting the National Industrial Security Program (NISP). Points of Contact are:
-The version of the OpenAPI document: v3.12
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
+The version of the OpenAPI document: v3.22
+Contact: disa.global.servicedesk.mbx.ma-ticket-request@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.1.0-SNAPSHOT
+Generator version: 7.12.0-SNAPSHOT
 =end
@@ -61,7 +61,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/octet-stream', 'application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/octet-stream', 'application/json']) unless header_params['Accept']
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/emass_client/api/cac_api.rb CHANGED Viewed

@@ -1,12 +1,12 @@
 =begin
 #Enterprise Mission Assurance Support Service (eMASS)
-#The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC:
+#The eMASS Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.  The eMASS API provides an interface for application to communicate eMASS Services. For information on how to register and use the eMASS API reference the [eMASS API Getting Started](eMASSGettingStarted.md).  Additional information about eMASS can be obtain by contacting the National Industrial Security Program (NISP). Points of Contact are:
-The version of the OpenAPI document: v3.12
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
+The version of the OpenAPI document: v3.22
+Contact: disa.global.servicedesk.mbx.ma-ticket-request@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.1.0-SNAPSHOT
+Generator version: 7.12.0-SNAPSHOT
 =end
@@ -20,9 +20,9 @@ module EmassClient
       @api_client = api_client
     end
     # Submit control to second role of CAC
-    #  **Request Body Required Fields** - `controlAcronym` - `comments`  **Notes:** - Comments `comments` are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters.  - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned.
+    # **Request Body Required Fields** - `controlAcronym` - `comments`  **NOTES:** - Comments `comments` are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters. - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] Add control(s) to second role of CAC
+    # @param request_body [Array<Object>] Example request body for adding control(s) to second role of CAC
     # @param [Hash] opts the optional parameters
     # @return [CacResponsePost]
     def add_system_cac(system_id, request_body, opts = {})
@@ -31,9 +31,9 @@ module EmassClient
     end
     # Submit control to second role of CAC
-    #  **Request Body Required Fields** - &#x60;controlAcronym&#x60; - &#x60;comments&#x60;  **Notes:** - Comments &#x60;comments&#x60; are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters.  - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned.
+    # **Request Body Required Fields** - &#x60;controlAcronym&#x60; - &#x60;comments&#x60;  **NOTES:** - Comments &#x60;comments&#x60; are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters. - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned.
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] Add control(s) to second role of CAC
+    # @param request_body [Array<Object>] Example request body for adding control(s) to second role of CAC
     # @param [Hash] opts the optional parameters
     # @return [Array<(CacResponsePost, Integer, Hash)>] CacResponsePost data, response status code and response headers
     def add_system_cac_with_http_info(system_id, request_body, opts = {})
@@ -57,7 +57,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['application/json'])
       if !content_type.nil?
@@ -128,7 +128,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/emass_client/api/cloud_resource_results_api.rb CHANGED Viewed

@@ -1,12 +1,12 @@
 =begin
 #Enterprise Mission Assurance Support Service (eMASS)
-#The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC:
+#The eMASS Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.  The eMASS API provides an interface for application to communicate eMASS Services. For information on how to register and use the eMASS API reference the [eMASS API Getting Started](eMASSGettingStarted.md).  Additional information about eMASS can be obtain by contacting the National Industrial Security Program (NISP). Points of Contact are:
-The version of the OpenAPI document: v3.12
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
+The version of the OpenAPI document: v3.22
+Contact: disa.global.servicedesk.mbx.ma-ticket-request@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 7.1.0-SNAPSHOT
+Generator version: 7.12.0-SNAPSHOT
 =end
@@ -20,9 +20,9 @@ module EmassClient
       @api_client = api_client
     end
     # Add one or many cloud resources and their scan results
-    # Add cloud resources and their scan results in the assets module for a system `systemId`  **Request Body Required Fields** - `provider` - `resourceId` - `resourceName` - `resourceType` - Compliance Results Object Array `complianceResults`   - `cspPolicyDefinitionId`   - `isCompliant`   - `policyDefinitionTitle`  **Example Request Body Required Fields** ``` [    {      \"provider\": \"provide name\",     \"resourceId\": \"resource identification\",     \"resourceName\": \"resource name\",     \"resourceType\": \"resource type\",     \"complianceResults\": [        {          \"cspPolicyDefinitionId\": \"CSP policy definition identification\",         \"policyDefinitionTitle\": \"policy definition title\",         \"isCompliant\": [true or false]       }      ]    }  ] ```
+    # Add cloud resources and their scan results in the assets module for a system `systemId`  **Request Body Required Fields** - `provider` - `resourceId` - `resourceName` - `resourceType` - `complianceResults` (Object Array)   - `cspPolicyDefinitionId`   - `isCompliant`   - `policyDefinitionTitle`  **Example Request Body Required Fields** ``` [   {     \"provider\": \"provide name\",     \"resourceId\": \"resource identification\",     \"resourceName\": \"resource name\",     \"resourceType\": \"resource type\",     \"complianceResults\": [       {         \"cspPolicyDefinitionId\": \"CSP policy definition identification\",         \"policyDefinitionTitle\": \"policy definition title\",         \"isCompliant\": [true or false]       }     ]   } ] ```
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] Add cloud resources and their scan results
+    # @param request_body [Array<Object>] Example request body for adding cloud resources and their scan results
     # @param [Hash] opts the optional parameters
     # @return [CloudResourcesResponsePost]
     def add_cloud_resources_by_system_id(system_id, request_body, opts = {})
@@ -31,9 +31,9 @@ module EmassClient
     end
     # Add one or many cloud resources and their scan results
-    # Add cloud resources and their scan results in the assets module for a system &#x60;systemId&#x60;  **Request Body Required Fields** - &#x60;provider&#x60; - &#x60;resourceId&#x60; - &#x60;resourceName&#x60; - &#x60;resourceType&#x60; - Compliance Results Object Array &#x60;complianceResults&#x60;   - &#x60;cspPolicyDefinitionId&#x60;   - &#x60;isCompliant&#x60;   - &#x60;policyDefinitionTitle&#x60;  **Example Request Body Required Fields** &#x60;&#x60;&#x60; [    {      \&quot;provider\&quot;: \&quot;provide name\&quot;,     \&quot;resourceId\&quot;: \&quot;resource identification\&quot;,     \&quot;resourceName\&quot;: \&quot;resource name\&quot;,     \&quot;resourceType\&quot;: \&quot;resource type\&quot;,     \&quot;complianceResults\&quot;: [        {          \&quot;cspPolicyDefinitionId\&quot;: \&quot;CSP policy definition identification\&quot;,         \&quot;policyDefinitionTitle\&quot;: \&quot;policy definition title\&quot;,         \&quot;isCompliant\&quot;: [true or false]       }      ]    }  ] &#x60;&#x60;&#x60;
+    # Add cloud resources and their scan results in the assets module for a system &#x60;systemId&#x60;  **Request Body Required Fields** - &#x60;provider&#x60; - &#x60;resourceId&#x60; - &#x60;resourceName&#x60; - &#x60;resourceType&#x60; - &#x60;complianceResults&#x60; (Object Array)   - &#x60;cspPolicyDefinitionId&#x60;   - &#x60;isCompliant&#x60;   - &#x60;policyDefinitionTitle&#x60;  **Example Request Body Required Fields** &#x60;&#x60;&#x60; [   {     \&quot;provider\&quot;: \&quot;provide name\&quot;,     \&quot;resourceId\&quot;: \&quot;resource identification\&quot;,     \&quot;resourceName\&quot;: \&quot;resource name\&quot;,     \&quot;resourceType\&quot;: \&quot;resource type\&quot;,     \&quot;complianceResults\&quot;: [       {         \&quot;cspPolicyDefinitionId\&quot;: \&quot;CSP policy definition identification\&quot;,         \&quot;policyDefinitionTitle\&quot;: \&quot;policy definition title\&quot;,         \&quot;isCompliant\&quot;: [true or false]       }     ]   } ] &#x60;&#x60;&#x60;
     # @param system_id [Integer] **System Id**: The unique system record identifier.
-    # @param request_body [Array<Object>] Add cloud resources and their scan results
+    # @param request_body [Array<Object>] Example request body for adding cloud resources and their scan results
     # @param [Hash] opts the optional parameters
     # @return [Array<(CloudResourcesResponsePost, Integer, Hash)>] CloudResourcesResponsePost data, response status code and response headers
     def add_cloud_resources_by_system_id_with_http_info(system_id, request_body, opts = {})
@@ -57,7 +57,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['application/json'])
       if !content_type.nil?
@@ -131,7 +131,7 @@ module EmassClient
       # header parameters
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
-      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
       # HTTP header 'Content-Type'
       content_type = @api_client.select_header_content_type(['application/json'])
       if !content_type.nil?