emasser 1.0.0 → 1.0.1

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

@@ -1,59 +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::PACApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'PACApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::PACApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of PACApi' do
-    it 'should create an instance of PACApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::PACApi)
-    end
-  end
-
-  # unit tests for add_system_pac
-  # Submit system package for review
-  # Adds a Package Approval Chain (PAC) for given &#x60;systemId&#x60; path parameter
-  # @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 [PacResponsePost]
-  describe 'add_system_pac 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_pac
-  # Get location of system package in PAC
-  # Returns the location of a system&#x27;s package in the Package Approval Chain (PAC) for matching &#x60;systemId&#x60; path parameter
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [PacResponseGet]
-  describe 'get_system_pac 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/poam_api_spec.rb

@@ -1,103 +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::POAMApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'POAMApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::POAMApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of POAMApi' do
-    it 'should create an instance of POAMApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::POAMApi)
-    end
-  end
-
-  # unit tests for add_poam_by_system_id
-  # Add one or many POA&amp;M items in a system
-  # Add a POA&amp;M for given &#x60;systemId&#x60;&lt;br&gt;  **Request Body Required Fields** - &#x60;status&#x60; - &#x60;vulnerabilityDescription&#x60; - &#x60;sourceIdentVuln&#x60; - &#x60;pocOrganization&#x60; - &#x60;resources&#x60;  **Note**&lt;br /&gt; If a POC email is supplied, the application will attempt to locate a user already registered within the application and pre-populate any information not explicitly supplied in the request. If no such user is found, these fields are **required** within the request.&lt;br&gt; &#x60;pocFirstName&#x60;, &#x60;pocLastName&#x60;, &#x60;pocPhoneNumber&#x60;&lt;br /&gt;
-  # @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 [PoamResponsePost]
-  describe 'add_poam_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_poam
-  # Remove one or many POA&amp;M items in a system
-  # Remove the POA&amp;M matching &#x60;systemId&#x60; path parameter and &#x60;poamId&#x60; query parameter&lt;br&gt;
-  # @param body Delete the given POA&amp;M Id
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @return [PoamResponseDelete]
-  describe 'delete_poam 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_poams
-  # Get one or many POA&amp;M items in a system
-  # Returns system(s) containing POA&amp;M items for matching parameters.
-  # @param system_id **System Id**: The unique system 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).
-  # @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 [PoamResponseGet]
-  describe 'get_system_poams 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_poams_by_poam_id
-  # Get POA&amp;M item by ID in a system
-  # Returns system(s) containing POA&amp;M items 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
-  # @return [PoamResponseGet]
-  describe 'get_system_poams_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 update_poam_by_system_id
-  # Update one or many POA&amp;M items in a system
-  # Update a POA&amp;M for given &#x60;systemId&#x60;&lt;br&gt;  **Request Body Required Fields** - &#x60;poamId&#x60; - &#x60;displayPoamId&#x60; - &#x60;status&#x60; - &#x60;vulnerabilityDescription&#x60; - &#x60;sourceIdentVuln&#x60; - &#x60;pocOrganization&#x60; - &#x60;reviewStatus&#x60;  **Notes** - If a POC email is supplied, the application will attempt to locate a user already   registered within the application and pre-populate any information not explicitly supplied   in the request. If no such user is found, these fields are **required** within the request.&lt;br&gt;   &#x60;pocOrganization&#x60;, &#x60;pocFirstName&#x60;, &#x60;pocLastName&#x60;, &#x60;pocEmail&#x60;, &#x60;pocPhoneNumber&#x60;&lt;br /&gt;  - To delete a milestone through the POA&amp;M PUT the field &#x60;isActive&#x60; must be set to &#x60;false&#x60;: &#x60;isActive&#x3D;false&#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 [PoamResponsePut]
-  describe 'update_poam_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/registration_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::RegistrationApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'RegistrationApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::RegistrationApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of RegistrationApi' do
-    it 'should create an instance of RegistrationApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::RegistrationApi)
-    end
-  end
-
-  # unit tests for register_user
-  # Register user certificate and obtain an API key
-  # Returns the api-key - This API key must be provided in the request header for all endpoint calls (api-key).
-  # @param body User certificate previously provided by eMASS.
-  # @param [Hash] opts the optional parameters
-  # @return [Register]
-  describe 'register_user 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/static_code_scans_api_spec.rb

@@ -1,47 +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::StaticCodeScansApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'StaticCodeScansApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::StaticCodeScansApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of StaticCodeScansApi' do
-    it 'should create an instance of StaticCodeScansApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::StaticCodeScansApi)
-    end
-  end
-
-  # unit tests for add_static_code_scans_by_system_id
-  # Upload static code scans or Clear static code scans
-  # Upload or clear application scan findings into a system&#x27;s &#x60;systemId&#x60; assets module.  **Note:** To clear an application&#x27;s findings, use only the field &#x60;clearFindings&#x60; as the Request body and set it to true.
-  # @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 [Success200Response]
-  describe 'add_static_code_scans_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/system_roles_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::SystemRolesApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'SystemRolesApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::SystemRolesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of SystemRolesApi' do
-    it 'should create an instance of SystemRolesApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::SystemRolesApi)
-    end
-  end
-
-  # unit tests for get_system_roles
-  # Get available roles
-  # Returns all available roles
-  # @param [Hash] opts the optional parameters
-  # @return [SystemRolesResponse]
-  describe 'get_system_roles 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_roles_by_category_id
-  # Get system roles
-  # Returns the role(s) data matching parameters.
-  # @param role_category **Role Category**: The system role category been queried
-  # @param role **Role**: Accepts single value from options available at base system-roles endpoint e.g., SCA.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :policy **System Policy**: Filter query by system policy. If no value is specified and more than one policy is available, the default return is the RMF policy information.
-  # @option opts [BOOLEAN] :include_decommissioned **Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.
-  # @return [SystemRolesCategoryResponse]
-  describe 'get_system_roles_by_category_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/systems_api_spec.rb

@@ -1,67 +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::SystemsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'SystemsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::SystemsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of SystemsApi' do
-    it 'should create an instance of SystemsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::SystemsApi)
-    end
-  end
-
-  # unit tests for get_system
-  # Get system information for a specific system
-  # Returns the system matching provided parameters
-  # @param system_id **System Id**: The unique system record identifier.
-  # @param [Hash] opts the optional parameters
-  # @option opts [BOOLEAN] :include_package **Include Package**:  Indicates if additional packages information is retrieved for queried system.
-  # @option opts [String] :policy **System Policy**: Filter query by system policy. If no value is specified and more than one policy is available, the default return is the RMF policy information.
-  # @return [SystemResponse]
-  describe 'get_system 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_systems
-  # Get system information
-  # Returns all system(s) that match the query parameters
-  # @param [Hash] opts the optional parameters
-  # @option opts [BOOLEAN] :include_package **Include Package**:  Indicates if additional packages information is retrieved for queried system.
-  # @option opts [String] :registration_type **Registration Type**: Filter record by selected registration type (single value or comma delimited values).  *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider  
-  # @option opts [String] :ditpr_id **DITPR ID**: Filter query by DoD Information Technology (IT) Portfolio Repository (DITPR).
-  # @option opts [String] :coams_id **COAMS ID**: Filter query by Cyber Operational Attributes Management System (COAMS).
-  # @option opts [String] :policy **System Policy**: Filter query by system policy. If no value is specified and more than one policy is available, the default return is the RMF policy information.
-  # @option opts [BOOLEAN] :include_ditpr_metrics **Include DITPR**: Indicates if DITPR metrics are retrieved. This query string parameter can only be used in conjunction with the following parameters:&lt;br&gt;   &lt;ul&gt;     &lt;li&gt;registrationType&lt;/li&gt;     &lt;li&gt;policy&lt;/li&gt;   &lt;/ul&gt;
-  # @option opts [BOOLEAN] :include_decommissioned **Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.
-  # @option opts [BOOLEAN] :reports_for_scorecard **DoD Cyber Hygiene Scorecard**: Indicates if the system reports to the DoD Cyber Hygiene Scorecard.
-  # @return [SystemResponse]
-  describe 'get_systems 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/test_api_spec.rb

@@ -1,45 +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::TestApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'TestApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::TestApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of TestApi' do
-    it 'should create an instance of TestApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::TestApi)
-    end
-  end
-
-  # unit tests for test_connection
-  # Test connection to the API
-  # Returns endpoint call status
-  # @param [Hash] opts the optional parameters
-  # @return [Test]
-  describe 'test_connection 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/test_results_api_spec.rb

@@ -1,62 +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::TestResultsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'TestResultsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::TestResultsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of TestResultsApi' do
-    it 'should create an instance of TestResultsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::TestResultsApi)
-    end
-  end
-
-  # unit tests for add_test_results_by_system_id
-  # Add one or many test results in a system
-  # Adds test results for given &#x60;systemId&#x60;  **Request Body Required Fields** - &#x60;cci&#x60; - &#x60;testedBy&#x60; - &#x60;testDate&#x60; - &#x60;description&#x60; - &#x60;complianceStatus&#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 [TestResultsResponsePost]
-  describe 'add_test_results_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 get_system_test_results
-  # Get one or many test results in a system
-  # Returns system test results information for matching parameters.&lt;br&gt;
-  # @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).
-  # @option opts [String] :ccis **CCI System**: Filter query by Control Correlation Identifiers (CCIs).
-  # @option opts [BOOLEAN] :latest_only **Latest Results Only**: Indicates that only the latest test resultes are retrieved (single or comma separated).
-  # @return [TestResultsResponseGet]
-  describe 'get_system_test_results 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/workflow_definitions_api_spec.rb

@@ -1,47 +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::WorkflowDefinitionsApi
-# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
-# Please update as you see appropriate
-describe 'WorkflowDefinitionsApi' do
-  before do
-    # run before each test
-    @instance = SwaggerClient::WorkflowDefinitionsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of WorkflowDefinitionsApi' do
-    it 'should create an instance of WorkflowDefinitionsApi' do
-      expect(@instance).to be_instance_of(SwaggerClient::WorkflowDefinitionsApi)
-    end
-  end
-
-  # unit tests for get_workflow_definitions
-  # Get workflow definitions in a site
-  # View all workflow schemas available on the eMASS instance filtered by  status &#x60;includeInactive&#x60; and registration type &#x60;registrationType&#x60;.
-  # @param [Hash] opts the optional parameters
-  # @option opts [BOOLEAN] :include_inactive **Include Inactive**: If no value is specified, the default returns false to not include outdated workflow definitions.
-  # @option opts [String] :registration_type **Registration Type**: Filter record by selected registration type (single value or comma delimited values).  *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider  
-  # @return [WorkflowDefinitionResponseGet]
-  describe 'get_workflow_definitions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end