emass_client 3.9.10 → 3.12.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (152) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +56 -41
  3. data/lib/emass_client/api/artifacts_api.rb +14 -11
  4. data/lib/emass_client/api/artifacts_export_api.rb +3 -3
  5. data/lib/emass_client/api/cac_api.rb +7 -7
  6. data/lib/emass_client/api/cloud_resource_results_api.rb +79 -5
  7. data/lib/emass_client/api/cmmc_assessments_api.rb +3 -3
  8. data/lib/emass_client/api/container_scan_results_api.rb +79 -5
  9. data/lib/emass_client/api/controls_api.rb +5 -5
  10. data/lib/emass_client/api/enterprise_artifacts_dashboards_api.rb +168 -0
  11. data/lib/emass_client/api/enterprise_poam_dashboards_api.rb +168 -0
  12. data/lib/emass_client/api/enterprise_security_controls_dashboards_api.rb +241 -0
  13. data/lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb +168 -0
  14. data/lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb +241 -0
  15. data/lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb +168 -0
  16. data/lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb +241 -0
  17. data/lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb +168 -0
  18. data/lib/emass_client/api/hardware_baseline_dashboards_api.rb +168 -0
  19. data/lib/emass_client/api/milestones_api.rb +6 -6
  20. data/lib/emass_client/api/pac_api.rb +11 -11
  21. data/lib/emass_client/api/poam_api.rb +12 -9
  22. data/lib/emass_client/api/ports_and_protocols_dashboards_api.rb +168 -0
  23. data/lib/emass_client/api/privacy_compliance_dashboards_api.rb +168 -0
  24. data/lib/emass_client/api/registration_api.rb +3 -3
  25. data/lib/emass_client/api/software_baseline_dashboards_api.rb +168 -0
  26. data/lib/emass_client/api/static_code_scans_api.rb +5 -5
  27. data/lib/emass_client/api/system_a20_summary_dashboard_api.rb +95 -0
  28. data/lib/emass_client/api/system_aa_summary_dashboard_api.rb +95 -0
  29. data/lib/emass_client/api/system_associations_dashboard_api.rb +95 -0
  30. data/lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb +95 -0
  31. data/lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb +95 -0
  32. data/lib/emass_client/api/system_roles_api.rb +5 -13
  33. data/lib/emass_client/api/system_status_dashboard_api.rb +95 -0
  34. data/lib/emass_client/api/systems_api.rb +26 -26
  35. data/lib/emass_client/api/test_api.rb +3 -3
  36. data/lib/emass_client/api/test_results_api.rb +14 -11
  37. data/lib/emass_client/api/threat_risks_dashboards_api.rb +241 -0
  38. data/lib/emass_client/api/users_dashboard_api.rb +95 -0
  39. data/lib/emass_client/api/workflow_definitions_api.rb +3 -3
  40. data/lib/emass_client/api/workflow_instances_api.rb +6 -3
  41. data/lib/emass_client/api_client.rb +5 -4
  42. data/lib/emass_client/api_error.rb +3 -3
  43. data/lib/emass_client/configuration.rb +3 -3
  44. data/lib/emass_client/models/artifacts_get.rb +28 -23
  45. data/lib/emass_client/models/artifacts_request_delete_body_inner.rb +15 -20
  46. data/lib/emass_client/models/artifacts_response_del.rb +15 -20
  47. data/lib/emass_client/models/artifacts_response_del_data_inner.rb +15 -20
  48. data/lib/emass_client/models/artifacts_response_get.rb +15 -20
  49. data/lib/emass_client/models/artifacts_response_put_post.rb +15 -20
  50. data/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +29 -25
  51. data/lib/emass_client/models/cac_get.rb +15 -20
  52. data/lib/emass_client/models/cac_response_get.rb +15 -20
  53. data/lib/emass_client/models/cac_response_post.rb +15 -20
  54. data/lib/emass_client/models/cac_response_post_data_inner.rb +29 -25
  55. data/lib/emass_client/models/cloud_resources_delete.rb +225 -0
  56. data/lib/emass_client/models/cloud_resources_delete_body_inner.rb +215 -0
  57. data/lib/emass_client/models/{cloud_resources_post.rb → cloud_resources_post_delete.rb} +32 -28
  58. data/lib/emass_client/models/cloud_resources_response_post.rb +16 -21
  59. data/lib/emass_client/models/cmmc_get.rb +15 -20
  60. data/lib/emass_client/models/cmmc_response_get.rb +15 -20
  61. data/lib/emass_client/models/connectivity_ccsd.rb +15 -20
  62. data/lib/emass_client/models/container_resources_delete_body_inner.rb +215 -0
  63. data/lib/emass_client/models/{containers_resources_post.rb → containers_resources_post_delete.rb} +32 -28
  64. data/lib/emass_client/models/containers_response_delete.rb +225 -0
  65. data/lib/emass_client/models/containers_response_post.rb +16 -21
  66. data/lib/emass_client/models/controls_get.rb +66 -39
  67. data/lib/emass_client/models/controls_put.rb +29 -25
  68. data/lib/emass_client/models/controls_response_get.rb +15 -20
  69. data/lib/emass_client/models/controls_response_put.rb +15 -20
  70. data/lib/emass_client/models/dashboard_mock_response.rb +15 -20
  71. data/lib/emass_client/models/dashboard_mock_response_pagination.rb +15 -20
  72. data/lib/emass_client/models/definition_transitions.rb +15 -20
  73. data/lib/emass_client/models/instances_transitions.rb +15 -20
  74. data/lib/emass_client/models/milestone_response_delete.rb +225 -0
  75. data/lib/emass_client/models/milestone_response_get.rb +15 -20
  76. data/lib/emass_client/models/milestone_response_get_milestone.rb +15 -20
  77. data/lib/emass_client/models/milestone_response_post.rb +15 -20
  78. data/lib/emass_client/models/milestone_response_put.rb +15 -20
  79. data/lib/emass_client/models/milestones_get.rb +15 -20
  80. data/lib/emass_client/models/milestones_put_post_delete.rb +29 -25
  81. data/lib/emass_client/models/milestones_request_delete_body_inner.rb +15 -20
  82. data/lib/emass_client/models/milestones_required_post.rb +19 -20
  83. data/lib/emass_client/models/milestones_required_put.rb +21 -20
  84. data/lib/emass_client/models/mock_object.rb +15 -20
  85. data/lib/emass_client/models/pac_get.rb +20 -45
  86. data/lib/emass_client/models/pac_post.rb +29 -25
  87. data/lib/emass_client/models/pac_response_get.rb +15 -20
  88. data/lib/emass_client/models/pac_response_post.rb +15 -20
  89. data/lib/emass_client/models/poam_get.rb +217 -36
  90. data/lib/emass_client/models/poam_post_put_del.rb +29 -25
  91. data/lib/emass_client/models/poam_request_delete_body_inner.rb +15 -20
  92. data/lib/emass_client/models/poam_response_delete.rb +15 -20
  93. data/lib/emass_client/models/poam_response_get_poams.rb +15 -20
  94. data/lib/emass_client/models/poam_response_get_systems.rb +15 -20
  95. data/lib/emass_client/models/poam_response_post.rb +15 -20
  96. data/lib/emass_client/models/poam_response_put.rb +15 -20
  97. data/lib/emass_client/models/register.rb +15 -20
  98. data/lib/emass_client/models/register_data.rb +15 -20
  99. data/lib/emass_client/models/register_user_request_post_body.rb +17 -20
  100. data/lib/emass_client/models/response200.rb +21 -22
  101. data/lib/emass_client/models/response201.rb +15 -20
  102. data/lib/emass_client/models/response201_meta.rb +21 -22
  103. data/lib/emass_client/models/response400.rb +15 -20
  104. data/lib/emass_client/models/response400_meta.rb +21 -22
  105. data/lib/emass_client/models/response401.rb +15 -20
  106. data/lib/emass_client/models/response401_meta.rb +21 -22
  107. data/lib/emass_client/models/response403.rb +15 -20
  108. data/lib/emass_client/models/response403_meta.rb +21 -22
  109. data/lib/emass_client/models/response404.rb +21 -22
  110. data/lib/emass_client/models/response405.rb +15 -20
  111. data/lib/emass_client/models/response405_meta.rb +21 -22
  112. data/lib/emass_client/models/response411.rb +15 -20
  113. data/lib/emass_client/models/response411_meta.rb +21 -22
  114. data/lib/emass_client/models/response490.rb +15 -20
  115. data/lib/emass_client/models/response490_meta.rb +21 -22
  116. data/lib/emass_client/models/response500.rb +15 -20
  117. data/lib/emass_client/models/response500_meta.rb +21 -22
  118. data/lib/emass_client/models/role_category.rb +15 -20
  119. data/lib/emass_client/models/roles.rb +15 -20
  120. data/lib/emass_client/models/ssps.rb +15 -20
  121. data/lib/emass_client/models/stage.rb +15 -20
  122. data/lib/emass_client/models/{static_code_application.rb → static_code_application_post.rb} +18 -23
  123. data/lib/emass_client/models/static_code_post.rb +29 -25
  124. data/lib/emass_client/models/static_code_request_post_body.rb +16 -21
  125. data/lib/emass_client/models/static_code_request_post_body_application.rb +15 -20
  126. data/lib/emass_client/models/static_code_response_post.rb +15 -20
  127. data/lib/emass_client/models/success200_response.rb +15 -20
  128. data/lib/emass_client/models/success200_response_data_inner.rb +29 -25
  129. data/lib/emass_client/models/system_response.rb +15 -20
  130. data/lib/emass_client/models/system_roles_category_response.rb +15 -20
  131. data/lib/emass_client/models/system_roles_response.rb +15 -20
  132. data/lib/emass_client/models/system_roles_response_data_inner.rb +15 -20
  133. data/lib/emass_client/models/systems.rb +248 -33
  134. data/lib/emass_client/models/systems_response.rb +15 -20
  135. data/lib/emass_client/models/test.rb +15 -20
  136. data/lib/emass_client/models/test_data.rb +15 -20
  137. data/lib/emass_client/models/test_results_get.rb +26 -21
  138. data/lib/emass_client/models/test_results_post.rb +29 -25
  139. data/lib/emass_client/models/test_results_response_get.rb +15 -20
  140. data/lib/emass_client/models/test_results_response_post.rb +15 -20
  141. data/lib/emass_client/models/users.rb +15 -20
  142. data/lib/emass_client/models/workflow_definition_get.rb +15 -20
  143. data/lib/emass_client/models/workflow_definition_response_get.rb +15 -20
  144. data/lib/emass_client/models/workflow_instance_get.rb +15 -20
  145. data/lib/emass_client/models/workflow_instance_response_get.rb +15 -20
  146. data/lib/emass_client/models/workflow_instances_get.rb +15 -20
  147. data/lib/emass_client/models/workflow_instances_response_get.rb +15 -20
  148. data/lib/emass_client/models/workflow_instances_response_get_pagination.rb +15 -20
  149. data/lib/emass_client/version.rb +4 -4
  150. data/lib/emass_client.rb +31 -7
  151. metadata +30 -6
  152. data/lib/emass_client/api/dashboards_api.rb +0 -2139
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #Enterprise Mission Assurance Support Service (eMASS)
3
3
 
4
- #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` endpoint 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:
4
+ #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:
5
5
 
6
- The version of the OpenAPI document: v3.10
6
+ The version of the OpenAPI document: v3.12
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.1.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -83,6 +83,7 @@ module EmassClient
83
83
  # Show invalid properties with the reasons. Usually used together with valid?
84
84
  # @return Array for valid properties with the reasons
85
85
  def list_invalid_properties
86
+ warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
86
87
  invalid_properties = Array.new
87
88
  invalid_properties
88
89
  end
@@ -90,6 +91,7 @@ module EmassClient
90
91
  # Check to see if the all the properties in the model are valid
91
92
  # @return true if the model is valid
92
93
  def valid?
94
+ warn '[DEPRECATED] the `valid?` method is obsolete'
93
95
  true
94
96
  end
95
97
 
@@ -119,37 +121,30 @@ module EmassClient
119
121
  # @param [Hash] attributes Model attributes in the form of hash
120
122
  # @return [Object] Returns the model itself
121
123
  def self.build_from_hash(attributes)
122
- new.build_from_hash(attributes)
123
- end
124
-
125
- # Builds the object from hash
126
- # @param [Hash] attributes Model attributes in the form of hash
127
- # @return [Object] Returns the model itself
128
- def build_from_hash(attributes)
129
124
  return nil unless attributes.is_a?(Hash)
130
125
  attributes = attributes.transform_keys(&:to_sym)
131
- self.class.openapi_types.each_pair do |key, type|
132
- if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key)
133
- self.send("#{key}=", nil)
126
+ transformed_hash = {}
127
+ openapi_types.each_pair do |key, type|
128
+ if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
129
+ transformed_hash["#{key}"] = nil
134
130
  elsif type =~ /\AArray<(.*)>/i
135
131
  # check to ensure the input is an array given that the attribute
136
132
  # is documented as an array but the input is not
137
- if attributes[self.class.attribute_map[key]].is_a?(Array)
138
- self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
133
+ if attributes[attribute_map[key]].is_a?(Array)
134
+ transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
139
135
  end
140
- elsif !attributes[self.class.attribute_map[key]].nil?
141
- self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
136
+ elsif !attributes[attribute_map[key]].nil?
137
+ transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
142
138
  end
143
139
  end
144
-
145
- self
140
+ new(transformed_hash)
146
141
  end
147
142
 
148
143
  # Deserializes the data based on type
149
144
  # @param string type Data type
150
145
  # @param string value Value to be deserialized
151
146
  # @return [Object] Deserialized data
152
- def _deserialize(type, value)
147
+ def self._deserialize(type, value)
153
148
  case type.to_sym
154
149
  when :Time
155
150
  Time.parse(value)
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #Enterprise Mission Assurance Support Service (eMASS)
3
3
 
4
- #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` endpoint 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:
4
+ #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:
5
5
 
6
- The version of the OpenAPI document: v3.10
6
+ The version of the OpenAPI document: v3.12
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.1.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -89,6 +89,7 @@ module EmassClient
89
89
  # Show invalid properties with the reasons. Usually used together with valid?
90
90
  # @return Array for valid properties with the reasons
91
91
  def list_invalid_properties
92
+ warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
92
93
  invalid_properties = Array.new
93
94
  invalid_properties
94
95
  end
@@ -96,6 +97,7 @@ module EmassClient
96
97
  # Check to see if the all the properties in the model are valid
97
98
  # @return true if the model is valid
98
99
  def valid?
100
+ warn '[DEPRECATED] the `valid?` method is obsolete'
99
101
  true
100
102
  end
101
103
 
@@ -126,37 +128,30 @@ module EmassClient
126
128
  # @param [Hash] attributes Model attributes in the form of hash
127
129
  # @return [Object] Returns the model itself
128
130
  def self.build_from_hash(attributes)
129
- new.build_from_hash(attributes)
130
- end
131
-
132
- # Builds the object from hash
133
- # @param [Hash] attributes Model attributes in the form of hash
134
- # @return [Object] Returns the model itself
135
- def build_from_hash(attributes)
136
131
  return nil unless attributes.is_a?(Hash)
137
132
  attributes = attributes.transform_keys(&:to_sym)
138
- self.class.openapi_types.each_pair do |key, type|
139
- if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key)
140
- self.send("#{key}=", nil)
133
+ transformed_hash = {}
134
+ openapi_types.each_pair do |key, type|
135
+ if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
136
+ transformed_hash["#{key}"] = nil
141
137
  elsif type =~ /\AArray<(.*)>/i
142
138
  # check to ensure the input is an array given that the attribute
143
139
  # is documented as an array but the input is not
144
- if attributes[self.class.attribute_map[key]].is_a?(Array)
145
- self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) })
140
+ if attributes[attribute_map[key]].is_a?(Array)
141
+ transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
146
142
  end
147
- elsif !attributes[self.class.attribute_map[key]].nil?
148
- self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]]))
143
+ elsif !attributes[attribute_map[key]].nil?
144
+ transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
149
145
  end
150
146
  end
151
-
152
- self
147
+ new(transformed_hash)
153
148
  end
154
149
 
155
150
  # Deserializes the data based on type
156
151
  # @param string type Data type
157
152
  # @param string value Value to be deserialized
158
153
  # @return [Object] Deserialized data
159
- def _deserialize(type, value)
154
+ def self._deserialize(type, value)
160
155
  case type.to_sym
161
156
  when :Time
162
157
  Time.parse(value)
@@ -1,15 +1,15 @@
1
1
  =begin
2
2
  #Enterprise Mission Assurance Support Service (eMASS)
3
3
 
4
- #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` endpoint 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:
4
+ #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:
5
5
 
6
- The version of the OpenAPI document: v3.10
6
+ The version of the OpenAPI document: v3.12
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.1.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
13
13
  module EmassClient
14
- VERSION = '3.9.10'
14
+ VERSION = '3.12.0'
15
15
  end
data/lib/emass_client.rb CHANGED
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #Enterprise Mission Assurance Support Service (eMASS)
3
3
 
4
- #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` endpoint 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:
4
+ #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:
5
5
 
6
- The version of the OpenAPI document: v3.10
6
+ The version of the OpenAPI document: v3.12
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 7.0.0-SNAPSHOT
9
+ OpenAPI Generator version: 7.1.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -28,12 +28,16 @@ require 'emass_client/models/cac_get'
28
28
  require 'emass_client/models/cac_response_get'
29
29
  require 'emass_client/models/cac_response_post'
30
30
  require 'emass_client/models/cac_response_post_data_inner'
31
- require 'emass_client/models/cloud_resources_post'
31
+ require 'emass_client/models/cloud_resources_delete'
32
+ require 'emass_client/models/cloud_resources_delete_body_inner'
33
+ require 'emass_client/models/cloud_resources_post_delete'
32
34
  require 'emass_client/models/cloud_resources_response_post'
33
35
  require 'emass_client/models/cmmc_get'
34
36
  require 'emass_client/models/cmmc_response_get'
35
37
  require 'emass_client/models/connectivity_ccsd'
36
- require 'emass_client/models/containers_resources_post'
38
+ require 'emass_client/models/container_resources_delete_body_inner'
39
+ require 'emass_client/models/containers_resources_post_delete'
40
+ require 'emass_client/models/containers_response_delete'
37
41
  require 'emass_client/models/containers_response_post'
38
42
  require 'emass_client/models/controls_get'
39
43
  require 'emass_client/models/controls_put'
@@ -43,6 +47,7 @@ require 'emass_client/models/dashboard_mock_response'
43
47
  require 'emass_client/models/dashboard_mock_response_pagination'
44
48
  require 'emass_client/models/definition_transitions'
45
49
  require 'emass_client/models/instances_transitions'
50
+ require 'emass_client/models/milestone_response_delete'
46
51
  require 'emass_client/models/milestone_response_get'
47
52
  require 'emass_client/models/milestone_response_get_milestone'
48
53
  require 'emass_client/models/milestone_response_post'
@@ -90,7 +95,7 @@ require 'emass_client/models/role_category'
90
95
  require 'emass_client/models/roles'
91
96
  require 'emass_client/models/ssps'
92
97
  require 'emass_client/models/stage'
93
- require 'emass_client/models/static_code_application'
98
+ require 'emass_client/models/static_code_application_post'
94
99
  require 'emass_client/models/static_code_post'
95
100
  require 'emass_client/models/static_code_request_post_body'
96
101
  require 'emass_client/models/static_code_request_post_body_application'
@@ -126,16 +131,35 @@ require 'emass_client/api/cmmc_assessments_api'
126
131
  require 'emass_client/api/cloud_resource_results_api'
127
132
  require 'emass_client/api/container_scan_results_api'
128
133
  require 'emass_client/api/controls_api'
129
- require 'emass_client/api/dashboards_api'
134
+ require 'emass_client/api/enterprise_artifacts_dashboards_api'
135
+ require 'emass_client/api/enterprise_poam_dashboards_api'
136
+ require 'emass_client/api/enterprise_security_controls_dashboards_api'
137
+ require 'emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api'
138
+ require 'emass_client/api/enterprise_sensor_based_software_resources_dashboards_api'
139
+ require 'emass_client/api/enterprise_terms_conditions_dashboards_api'
140
+ require 'emass_client/api/enterprise_vulnerability_dashboards_api'
141
+ require 'emass_client/api/fisma_inventory_summary_dashboards_api'
142
+ require 'emass_client/api/hardware_baseline_dashboards_api'
130
143
  require 'emass_client/api/milestones_api'
131
144
  require 'emass_client/api/pac_api'
132
145
  require 'emass_client/api/poam_api'
146
+ require 'emass_client/api/ports_and_protocols_dashboards_api'
147
+ require 'emass_client/api/privacy_compliance_dashboards_api'
133
148
  require 'emass_client/api/registration_api'
149
+ require 'emass_client/api/software_baseline_dashboards_api'
134
150
  require 'emass_client/api/static_code_scans_api'
151
+ require 'emass_client/api/system_a20_summary_dashboard_api'
152
+ require 'emass_client/api/system_aa_summary_dashboard_api'
153
+ require 'emass_client/api/system_associations_dashboard_api'
154
+ require 'emass_client/api/system_conmon_integration_status_dashboard_api'
155
+ require 'emass_client/api/system_pl109_reporting_summary_dashboard_api'
135
156
  require 'emass_client/api/system_roles_api'
157
+ require 'emass_client/api/system_status_dashboard_api'
136
158
  require 'emass_client/api/systems_api'
137
159
  require 'emass_client/api/test_api'
138
160
  require 'emass_client/api/test_results_api'
161
+ require 'emass_client/api/threat_risks_dashboards_api'
162
+ require 'emass_client/api/users_dashboard_api'
139
163
  require 'emass_client/api/workflow_definitions_api'
140
164
  require 'emass_client/api/workflow_instances_api'
141
165
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: emass_client
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.9.10
4
+ version: 3.12.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - OpenAPI-Generator
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-06-13 00:00:00.000000000 Z
11
+ date: 2023-10-10 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -69,16 +69,35 @@ files:
69
69
  - lib/emass_client/api/cmmc_assessments_api.rb
70
70
  - lib/emass_client/api/container_scan_results_api.rb
71
71
  - lib/emass_client/api/controls_api.rb
72
- - lib/emass_client/api/dashboards_api.rb
72
+ - lib/emass_client/api/enterprise_artifacts_dashboards_api.rb
73
+ - lib/emass_client/api/enterprise_poam_dashboards_api.rb
74
+ - lib/emass_client/api/enterprise_security_controls_dashboards_api.rb
75
+ - lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb
76
+ - lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb
77
+ - lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb
78
+ - lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb
79
+ - lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb
80
+ - lib/emass_client/api/hardware_baseline_dashboards_api.rb
73
81
  - lib/emass_client/api/milestones_api.rb
74
82
  - lib/emass_client/api/pac_api.rb
75
83
  - lib/emass_client/api/poam_api.rb
84
+ - lib/emass_client/api/ports_and_protocols_dashboards_api.rb
85
+ - lib/emass_client/api/privacy_compliance_dashboards_api.rb
76
86
  - lib/emass_client/api/registration_api.rb
87
+ - lib/emass_client/api/software_baseline_dashboards_api.rb
77
88
  - lib/emass_client/api/static_code_scans_api.rb
89
+ - lib/emass_client/api/system_a20_summary_dashboard_api.rb
90
+ - lib/emass_client/api/system_aa_summary_dashboard_api.rb
91
+ - lib/emass_client/api/system_associations_dashboard_api.rb
92
+ - lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb
93
+ - lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb
78
94
  - lib/emass_client/api/system_roles_api.rb
95
+ - lib/emass_client/api/system_status_dashboard_api.rb
79
96
  - lib/emass_client/api/systems_api.rb
80
97
  - lib/emass_client/api/test_api.rb
81
98
  - lib/emass_client/api/test_results_api.rb
99
+ - lib/emass_client/api/threat_risks_dashboards_api.rb
100
+ - lib/emass_client/api/users_dashboard_api.rb
82
101
  - lib/emass_client/api/workflow_definitions_api.rb
83
102
  - lib/emass_client/api/workflow_instances_api.rb
84
103
  - lib/emass_client/api_client.rb
@@ -95,12 +114,16 @@ files:
95
114
  - lib/emass_client/models/cac_response_get.rb
96
115
  - lib/emass_client/models/cac_response_post.rb
97
116
  - lib/emass_client/models/cac_response_post_data_inner.rb
98
- - lib/emass_client/models/cloud_resources_post.rb
117
+ - lib/emass_client/models/cloud_resources_delete.rb
118
+ - lib/emass_client/models/cloud_resources_delete_body_inner.rb
119
+ - lib/emass_client/models/cloud_resources_post_delete.rb
99
120
  - lib/emass_client/models/cloud_resources_response_post.rb
100
121
  - lib/emass_client/models/cmmc_get.rb
101
122
  - lib/emass_client/models/cmmc_response_get.rb
102
123
  - lib/emass_client/models/connectivity_ccsd.rb
103
- - lib/emass_client/models/containers_resources_post.rb
124
+ - lib/emass_client/models/container_resources_delete_body_inner.rb
125
+ - lib/emass_client/models/containers_resources_post_delete.rb
126
+ - lib/emass_client/models/containers_response_delete.rb
104
127
  - lib/emass_client/models/containers_response_post.rb
105
128
  - lib/emass_client/models/controls_get.rb
106
129
  - lib/emass_client/models/controls_put.rb
@@ -110,6 +133,7 @@ files:
110
133
  - lib/emass_client/models/dashboard_mock_response_pagination.rb
111
134
  - lib/emass_client/models/definition_transitions.rb
112
135
  - lib/emass_client/models/instances_transitions.rb
136
+ - lib/emass_client/models/milestone_response_delete.rb
113
137
  - lib/emass_client/models/milestone_response_get.rb
114
138
  - lib/emass_client/models/milestone_response_get_milestone.rb
115
139
  - lib/emass_client/models/milestone_response_post.rb
@@ -157,7 +181,7 @@ files:
157
181
  - lib/emass_client/models/roles.rb
158
182
  - lib/emass_client/models/ssps.rb
159
183
  - lib/emass_client/models/stage.rb
160
- - lib/emass_client/models/static_code_application.rb
184
+ - lib/emass_client/models/static_code_application_post.rb
161
185
  - lib/emass_client/models/static_code_post.rb
162
186
  - lib/emass_client/models/static_code_request_post_body.rb
163
187
  - lib/emass_client/models/static_code_request_post_body_application.rb