emasser 1.0.0 → 1.0.6

data/emass_client/ruby_client/lib/swagger_client.rb

@@ -1,161 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-# Common files
-require 'swagger_client/api_client'
-require 'swagger_client/api_error'
-require 'swagger_client/version'
-require 'swagger_client/configuration'
-
-# Models
-require 'swagger_client/models/artifacts_delete'
-require 'swagger_client/models/artifacts_delete_inner'
-require 'swagger_client/models/artifacts_get'
-require 'swagger_client/models/artifacts_request_put_body'
-require 'swagger_client/models/artifacts_response_del'
-require 'swagger_client/models/artifacts_response_del_data'
-require 'swagger_client/models/artifacts_response_get'
-require 'swagger_client/models/artifacts_response_put_post'
-require 'swagger_client/models/cac_get'
-require 'swagger_client/models/cac_request_post_body'
-require 'swagger_client/models/cac_response_get'
-require 'swagger_client/models/cac_response_post'
-require 'swagger_client/models/cac_response_post_data'
-require 'swagger_client/models/cmmc_get'
-require 'swagger_client/models/cmmc_response_get'
-require 'swagger_client/models/connectivity_ccsd'
-require 'swagger_client/models/controls_get'
-require 'swagger_client/models/controls_put'
-require 'swagger_client/models/controls_request_put_body'
-require 'swagger_client/models/controls_response_get'
-require 'swagger_client/models/controls_response_put'
-require 'swagger_client/models/definition_transitions'
-require 'swagger_client/models/delete_milestone'
-require 'swagger_client/models/delete_poam'
-require 'swagger_client/models/empty200_response'
-require 'swagger_client/models/error'
-require 'swagger_client/models/instances_transitions'
-require 'swagger_client/models/milestone_response_get'
-require 'swagger_client/models/milestone_response_post'
-require 'swagger_client/models/milestone_response_put'
-require 'swagger_client/models/milestones_delete'
-require 'swagger_client/models/milestones_get'
-require 'swagger_client/models/milestones_post'
-require 'swagger_client/models/milestones_put'
-require 'swagger_client/models/milestones_put_post_delete'
-require 'swagger_client/models/milestones_request_post_body'
-require 'swagger_client/models/milestones_request_put_body'
-require 'swagger_client/models/milestones_required_post'
-require 'swagger_client/models/milestones_required_put'
-require 'swagger_client/models/model_200'
-require 'swagger_client/models/model_201'
-require 'swagger_client/models/model_201_meta'
-require 'swagger_client/models/model_400'
-require 'swagger_client/models/model_400_meta'
-require 'swagger_client/models/model_400_response'
-require 'swagger_client/models/model_401'
-require 'swagger_client/models/model_401_meta'
-require 'swagger_client/models/model_403'
-require 'swagger_client/models/model_403_meta'
-require 'swagger_client/models/model_404'
-require 'swagger_client/models/model_404_response'
-require 'swagger_client/models/model_405'
-require 'swagger_client/models/model_405_meta'
-require 'swagger_client/models/model_411'
-require 'swagger_client/models/model_411_meta'
-require 'swagger_client/models/model_490'
-require 'swagger_client/models/model_490_meta'
-require 'swagger_client/models/model_500'
-require 'swagger_client/models/model_500_meta'
-require 'swagger_client/models/pac_get'
-require 'swagger_client/models/pac_post'
-require 'swagger_client/models/pac_request_post_body'
-require 'swagger_client/models/pac_response_get'
-require 'swagger_client/models/pac_response_post'
-require 'swagger_client/models/poam_delete'
-require 'swagger_client/models/poam_get'
-require 'swagger_client/models/poam_post'
-require 'swagger_client/models/poam_post_put_del'
-require 'swagger_client/models/poam_put'
-require 'swagger_client/models/poam_request_post_body'
-require 'swagger_client/models/poam_request_put_body'
-require 'swagger_client/models/poam_required_post'
-require 'swagger_client/models/poam_required_put'
-require 'swagger_client/models/poam_response_delete'
-require 'swagger_client/models/poam_response_get'
-require 'swagger_client/models/poam_response_post'
-require 'swagger_client/models/poam_response_put'
-require 'swagger_client/models/register'
-require 'swagger_client/models/register_data'
-require 'swagger_client/models/register_user_request_post_body'
-require 'swagger_client/models/role_category'
-require 'swagger_client/models/roles'
-require 'swagger_client/models/ssps'
-require 'swagger_client/models/stage'
-require 'swagger_client/models/static_code_application'
-require 'swagger_client/models/static_code_request_post_body'
-require 'swagger_client/models/static_code_required_post'
-require 'swagger_client/models/static_code_required_post_application'
-require 'swagger_client/models/success200_response'
-require 'swagger_client/models/system_id_artifacts_body'
-require 'swagger_client/models/system_response'
-require 'swagger_client/models/system_roles_category_response'
-require 'swagger_client/models/system_roles_response'
-require 'swagger_client/models/system_roles_response_data'
-require 'swagger_client/models/systems'
-require 'swagger_client/models/test'
-require 'swagger_client/models/test_data'
-require 'swagger_client/models/test_results_get'
-require 'swagger_client/models/test_results_post'
-require 'swagger_client/models/test_results_request_post_body'
-require 'swagger_client/models/test_results_response_get'
-require 'swagger_client/models/test_results_response_post'
-require 'swagger_client/models/users'
-require 'swagger_client/models/workflow_definition_get'
-require 'swagger_client/models/workflow_definition_response_get'
-require 'swagger_client/models/workflow_instances_get'
-require 'swagger_client/models/workflow_instances_response_get'
-
-# APIs
-require 'swagger_client/api/artifacts_api'
-require 'swagger_client/api/artifacts_export_api'
-require 'swagger_client/api/cac_api'
-require 'swagger_client/api/cmmc_assessments_api'
-require 'swagger_client/api/controls_api'
-require 'swagger_client/api/milestones_api'
-require 'swagger_client/api/pac_api'
-require 'swagger_client/api/poam_api'
-require 'swagger_client/api/registration_api'
-require 'swagger_client/api/static_code_scans_api'
-require 'swagger_client/api/system_roles_api'
-require 'swagger_client/api/systems_api'
-require 'swagger_client/api/test_api'
-require 'swagger_client/api/test_results_api'
-require 'swagger_client/api/workflow_definitions_api'
-require 'swagger_client/api/workflow_instances_api'
-
-module SwaggerClient
-  class << self
-    # Customize default settings for the SDK using block.
-    #   SwaggerClient.configure do |config|
-    #     config.username = "xxx"
-    #     config.password = "xxx"
-    #   end
-    # If no block given, return the default Configuration object.
-    def configure
-      if block_given?
-        yield(Configuration.default)
-      else
-        Configuration.default
-      end
-    end
-  end
-end

data/emass_client/ruby_client/spec/api/artifacts_api_spec.rb

@@ -1,92 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::ArtifactsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'ArtifactsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::ArtifactsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ArtifactsApi' do
-    it 'should create an instance of ArtifactsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::ArtifactsApi)
-    end
-  end
-
-  # unit tests for add_artifacts_by_system_id
-  # Add one or many artifacts in a system
-  # &lt;strong&gt;Information&lt;/strong&gt;&lt;br&gt; The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension \&quot;.zip\&quot; only. This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. Filename uniqueness throughout eMASS will be enforced by the API.&lt;br&gt;&lt;br&gt; Upon successful receipt of a file, if a file within the .zip 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 blank. &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;Zip file information&lt;/strong&gt;&lt;br&gt; Upload a zip file 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; &lt;strong&gt;Business Rules&lt;/strong&gt;&lt;br&gt; Artifact cannot be saved if the file does not have the following file extensions:      .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 already exist in the system.  Artifact cannot be saved if the file size exceeds 30MB.
-  # @param is_template 
-  # @param type 
-  # @param category 
-  # @param zipper 
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [ArtifactsResponsePutPost]
-  describe 'add_artifacts_by_system_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_artifact
-  # 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
-  # @param body See notes above for additional information
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [ArtifactsResponseDel]
-  describe 'delete_artifact test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_system_artifacts
-  # Get one or many artifacts in a system
-  # Returns selected artifacts matching parameters to include the file name containing the artifacts.
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :filename **File Name**: The file name (to include file-extension).
-  # @option opts [String] :control_acronyms **System Acronym**: Filter query by given system acronym (single or comma separated).
-  # @option opts [String] :ccis **CCI System**: Filter query by Control Correlation Identifiers (CCIs).
-  # @option opts [BOOLEAN] :system_only **Systems Only**: Indicates that only system(s) information is retrieved.
-  # @return [ArtifactsResponseGet]
-  describe 'get_system_artifacts test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_artifact_by_system_id
-  # 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;
-  # @param body See &#x60;information&#x60; above for additional instructions
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [ArtifactsResponsePutPost]
-  describe 'update_artifact_by_system_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/emass_client/ruby_client/spec/api/artifacts_export_api_spec.rb

@@ -1,48 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::ArtifactsExportApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'ArtifactsExportApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::ArtifactsExportApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ArtifactsExportApi' do
-    it 'should create an instance of ArtifactsExportApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::ArtifactsExportApi)
-    end
-  end
-
-  # unit tests for get_system_artifacts_export
-  # Get the file of an artifact in a system
-  # &lt;strong&gt;Sample Responce&lt;/strong&gt;&lt;br&gt;  Binary file associated with given filename.&lt;br&gt;  If &#x60;compress&#x60; parameter is specified, zip archive of binary file associated with given filename.
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param filename **File Name**: The file name (to include file-extension).
-  # @param [Hash] opts the optional parameters
-  # @option opts [BOOLEAN] :compress **Compress File**: Determines if returned file is compressed.
-  # @return [String]
-  describe 'get_system_artifacts_export test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/emass_client/ruby_client/spec/api/cac_api_spec.rb

@@ -1,60 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::CACApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'CACApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::CACApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of CACApi' do
-    it 'should create an instance of CACApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::CACApi)
-    end
-  end
-
-  # unit tests for add_system_cac
-  # Submit control to second role of CAC
-  # Adds a Control Approval Chain (CAC) for given &#x60;systemId&#x60; path parameter&lt;br&gt;&lt;br&gt; 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 body Update an existing Artifact by Id
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [CacResponsePost]
-  describe 'add_system_cac test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_system_cac
-  # Get location of one or many controls in CAC
-  # Returns the location of a system&#x27;s package in the Control Approval Chain (CAC) for matching &#x60;systemId&#x60; path parameter
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :control_acronyms **System Acronym**: Filter query by given system acronym (single or comma separated).
-  # @return [CacResponseGet]
-  describe 'get_system_cac test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/emass_client/ruby_client/spec/api/cmmc_assessments_api_spec.rb

@@ -1,46 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::CMMCAssessmentsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'CMMCAssessmentsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::CMMCAssessmentsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of CMMCAssessmentsApi' do
-    it 'should create an instance of CMMCAssessmentsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::CMMCAssessmentsApi)
-    end
-  end
-
-  # unit tests for get_cmmc_assessments
-  # Get CMMC assessment information
-  # Get all CMMC assessment after the given date &#x60;sinceDate&#x60; parameter. It is available to CMMC eMASS only.
-  # @param since_date **Date** CMMC date (Unix date format)
-  # @param [Hash] opts the optional parameters
-  # @return [CmmcResponseGet]
-  describe 'get_cmmc_assessments test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/emass_client/ruby_client/spec/api/controls_api_spec.rb

@@ -1,60 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::ControlsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'ControlsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::ControlsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ControlsApi' do
-    it 'should create an instance of ControlsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::ControlsApi)
-    end
-  end
-
-  # unit tests for get_system_controls
-  # Get control information in a system for one or many controls
-  # Returns system control information for matching &#x60;systemId&#x60; path parameter
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :acronyms **Acronym**: The system acronym(s) being queried (single value or comma delimited values).
-  # @return [ControlsResponseGet]
-  describe 'get_system_controls test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_control_by_system_id
-  # Update control information in a system for one or many controls
-  #  Update a Control for given &#x60;systemId&#x60;&lt;br&gt;  **Request Body Required Fields** - &#x60;acronym&#x60; - &#x60;responsibleEntities&#x60; - &#x60;controlDesignation&#x60; - &#x60;estimatedCompletionDate&#x60; - &#x60;implementationNarrative&#x60;  The following optional fields are required based on the Implementation Status &#x60;implementationStatus&#x60; value&lt;br&gt; | Value                    | Required Fields |--------------------------|--------------------------------------------------- | Planned  or Implemented  | &#x60;estimatedCompletionDate&#x60;, &#x60;responsibleEntities&#x60;, &#x60;slcmCriticality&#x60;, &#x60;slcmFrequency&#x60;, &#x60;slcmMethod&#x60;, &#x60;slcmReporting&#x60;, &#x60;slcmTracking&#x60;, &#x60;slcmComments&#x60; | Not Applicable           | &#x60;naJustification&#x60;, &#x60;responsibleEntities&#x60; | Manually Inherited       | &#x60;commonControlProvider&#x60;, &#x60;estimatedCompletionDate&#x60;, &#x60;responsibleEntities&#x60;, &#x60;slcmCriticality&#x60;, &#x60;slcmFrequency&#x60;, &#x60;slcmMethod&#x60;, &#x60;slcmReporting&#x60;, &#x60;slcmTracking&#x60;, &#x60;slcmComments&#x60;  If the Implementation Status &#x60;implementationStatus&#x60; value is \&quot;Inherited\&quot;, only the following fields can be updated:   - &#x60;controlDesignation&#x60;   - &#x60;commonnControlProvider&#x60;
-  # @param body Update an existing control by Id
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [ControlsResponsePut]
-  describe 'update_control_by_system_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/emass_client/ruby_client/spec/api/milestones_api_spec.rb

@@ -1,105 +0,0 @@
-=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.   The `emasser` is a command-line interface (CLI) tool that implements all of the  eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.</br><br>  <strong>Register CLI</strong></br> New users will need to register 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) where {url}/api/register (POST) is used to register the client certificate.</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: 
-
-OpenAPI spec version: v3.2
-Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
-Generated by: https://github.com/swagger-api/swagger-codegen.git
-Swagger Codegen version: 3.0.26
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for SwaggerClient::MilestonesApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'MilestonesApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::MilestonesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of MilestonesApi' do
-    it 'should create an instance of MilestonesApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::MilestonesApi)
-    end
-  end
-
-  # unit tests for add_milestone_by_system_id_and_poam_id
-  # Add milestones to one or many POA&amp;M items in a system
-  # Adds a milestone for given &#x60;systemId&#x60; and &#x60;poamId&#x60; path parameters  **Request Body Required Fields** - &#x60;description&#x60; - &#x60;scheduledCompletionDate&#x60;
-  # @param body Update an existing milestone
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param poam_id **POA&amp;M Id**: The unique POA&amp;M record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [MilestoneResponsePost]
-  describe 'add_milestone_by_system_id_and_poam_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_milestone
-  # Remove milestones in a system for one or many POA&amp;M items
-  # Remove the POA&amp;M matching &#x60;systemId&#x60; path parameter&lt;br&gt; **Notes**&lt;br&gt; To delete a milestone the record must be inactive by having the field isActive set to false (&#x60;isActive&#x3D;false&#x60;).
-  # @param body Delete the given Milestone Id
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param poam_id **POA&amp;M Id**: The unique POA&amp;M record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [Empty200Response]
-  describe 'delete_milestone test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_system_milestones_by_poam_id
-  # Get milestones in one or many POA&amp;M items in a system
-  # Returns system containing milestones for matching parameters.
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param poam_id **POA&amp;M Id**: The unique POA&amp;M record identifier.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :scheduled_completion_date_start **Date Started**: Filter query by the scheduled completion start date (Unix date format).
-  # @option opts [String] :scheduled_completion_date_end **Date Ended**: Filter query by the scheduled completion start date (Unix date format).
-  # @return [MilestoneResponseGet]
-  describe 'get_system_milestones_by_poam_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_system_milestones_by_poam_id_and_milestone_id
-  # Get milestone by ID in POA&amp;M item in a system
-  # Returns systems containing milestones for matching parameters.
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param poam_id **POA&amp;M Id**: The unique POA&amp;M record identifier.
-  # @param milestone_id **Milestone Id**: The unique milestone record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [MilestoneResponseGet]
-  describe 'get_system_milestones_by_poam_id_and_milestone_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_milestone_by_system_id_and_poam_id
-  # Update one or many POA&amp;M items in a system
-  # Updates a milestone for given &#x60;systemId&#x60; and &#x60;poamId&#x60; path parameters  **Request Body Required Fields** - &#x60;milestoneId&#x60; - &#x60;description&#x60; - &#x60;scheduledCompletionDate&#x60;
-  # @param body Update an existing control by Id
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param poam_id **POA&amp;M Id**: The unique POA&amp;M record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [MilestoneResponsePut]
-  describe 'update_milestone_by_system_id_and_poam_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end