From b78fd54dad5bc4acc414ad1440e27a0d06650afd Mon Sep 17 00:00:00 2001 From: "George M. Dias" Date: Tue, 13 Jun 2023 11:26:57 -0400 Subject: [PATCH] API spec v3.10 (#8) --- .github/workflows/generate_docs.yml | 1 + .github/workflows/gh-pages.yml | 1 + .github/workflows/publish-to-test-pypi.yml | 18 +- docs/developers.md | 5 +- eMASSRestOpenApi.yaml | 508 +++++++++++-- .../python/python-generator-config.json | 2 +- .../templates/ruby/ruby-generator-config.json | 2 +- .../typescript-generator-config.json | 2 +- src/python_client/.openapi-generator/FILES | 10 + src/python_client/README.md | 66 +- .../docs/DashboardMockResponse.md | 30 + .../docs/DashboardMockResponsePagination.md | 33 + src/python_client/docs/DashboardsApi.md | 468 ++++++++++-- src/python_client/docs/MockObject.md | 40 + src/python_client/docs/Systems.md | 2 + .../docs/WorkflowInstanceResponseGet.md | 2 +- src/python_client/emass_client/__init__.py | 13 +- .../emass_client/api/artifacts_api.py | 8 +- .../emass_client/api/artifacts_export_api.py | 8 +- src/python_client/emass_client/api/cac_api.py | 8 +- .../api/cloud_resource_results_api.py | 8 +- .../emass_client/api/cmmc_assessments_api.py | 8 +- .../api/container_scan_results_api.py | 8 +- .../emass_client/api/controls_api.py | 8 +- .../emass_client/api/dashboards_api.py | 622 ++++++++++++++-- .../emass_client/api/milestones_api.py | 8 +- src/python_client/emass_client/api/pac_api.py | 8 +- .../emass_client/api/poam_api.py | 8 +- .../emass_client/api/registration_api.py | 8 +- .../emass_client/api/static_code_scans_api.py | 8 +- .../emass_client/api/system_roles_api.py | 8 +- .../emass_client/api/systems_api.py | 8 +- .../emass_client/api/test_api.py | 8 +- .../emass_client/api/test_results_api.py | 8 +- .../api/workflow_definitions_api.py | 8 +- .../api/workflow_instances_api.py | 8 +- src/python_client/emass_client/api_client.py | 10 +- .../emass_client/configuration.py | 12 +- src/python_client/emass_client/exceptions.py | 12 +- .../emass_client/models/__init__.py | 11 +- .../emass_client/models/artifacts_get.py | 8 +- .../artifacts_request_delete_body_inner.py | 8 +- .../models/artifacts_response_del.py | 8 +- .../artifacts_response_del_data_inner.py | 8 +- .../models/artifacts_response_get.py | 8 +- .../models/artifacts_response_put_post.py | 8 +- .../artifacts_response_put_post_data_inner.py | 8 +- .../emass_client/models/cac_get.py | 8 +- .../emass_client/models/cac_response_get.py | 8 +- .../emass_client/models/cac_response_post.py | 8 +- .../models/cac_response_post_data_inner.py | 8 +- .../models/cloud_resources_post.py | 8 +- .../models/cloud_resources_response_post.py | 8 +- .../emass_client/models/cmmc_get.py | 8 +- .../emass_client/models/cmmc_response_get.py | 8 +- .../emass_client/models/connectivity_ccsd.py | 8 +- .../models/containers_resources_post.py | 8 +- .../models/containers_response_post.py | 8 +- .../emass_client/models/controls_get.py | 8 +- .../emass_client/models/controls_put.py | 8 +- .../models/controls_response_get.py | 8 +- .../models/controls_response_put.py | 8 +- .../models/dashboard_mock_response.py | 127 ++++ .../dashboard_mock_response_pagination.py | 117 +++ .../models/definition_transitions.py | 8 +- .../models/instances_transitions.py | 8 +- .../models/milestone_response_get.py | 8 +- .../milestone_response_get_milestone.py | 8 +- .../models/milestone_response_post.py | 8 +- .../models/milestone_response_put.py | 8 +- .../emass_client/models/milestones_get.py | 8 +- .../models/milestones_put_post_delete.py | 8 +- .../milestones_request_delete_body_inner.py | 8 +- .../models/milestones_required_post.py | 8 +- .../models/milestones_required_put.py | 8 +- .../emass_client/models/mock_object.py | 146 ++++ .../emass_client/models/pac_get.py | 8 +- .../emass_client/models/pac_post.py | 8 +- .../emass_client/models/pac_response_get.py | 8 +- .../emass_client/models/pac_response_post.py | 8 +- .../emass_client/models/poam_get.py | 8 +- .../emass_client/models/poam_post_put_del.py | 8 +- .../models/poam_request_delete_body_inner.py | 8 +- .../models/poam_response_delete.py | 8 +- .../models/poam_response_get_poams.py | 8 +- .../models/poam_response_get_systems.py | 8 +- .../emass_client/models/poam_response_post.py | 8 +- .../emass_client/models/poam_response_put.py | 8 +- .../emass_client/models/register.py | 8 +- .../emass_client/models/register_data.py | 8 +- .../models/register_user_request_post_body.py | 8 +- .../emass_client/models/response200.py | 8 +- .../emass_client/models/response201.py | 8 +- .../emass_client/models/response201_meta.py | 8 +- .../emass_client/models/response400.py | 8 +- .../emass_client/models/response400_meta.py | 8 +- .../emass_client/models/response401.py | 8 +- .../emass_client/models/response401_meta.py | 8 +- .../emass_client/models/response403.py | 8 +- .../emass_client/models/response403_meta.py | 8 +- .../emass_client/models/response404.py | 8 +- .../emass_client/models/response405.py | 8 +- .../emass_client/models/response405_meta.py | 8 +- .../emass_client/models/response411.py | 8 +- .../emass_client/models/response411_meta.py | 8 +- .../emass_client/models/response490.py | 8 +- .../emass_client/models/response490_meta.py | 8 +- .../emass_client/models/response500.py | 8 +- .../emass_client/models/response500_meta.py | 8 +- .../emass_client/models/role_category.py | 8 +- .../emass_client/models/roles.py | 8 +- src/python_client/emass_client/models/ssps.py | 8 +- .../emass_client/models/stage.py | 8 +- .../models/static_code_application.py | 8 +- .../emass_client/models/static_code_post.py | 8 +- .../models/static_code_request_post_body.py | 8 +- ...atic_code_request_post_body_application.py | 8 +- .../models/static_code_response_post.py | 8 +- .../models/success200_response.py | 8 +- .../models/success200_response_data_inner.py | 8 +- .../emass_client/models/system_response.py | 8 +- .../models/system_roles_category_response.py | 8 +- .../models/system_roles_response.py | 8 +- .../system_roles_response_data_inner.py | 8 +- .../emass_client/models/systems.py | 24 +- .../emass_client/models/systems_response.py | 8 +- src/python_client/emass_client/models/test.py | 8 +- .../emass_client/models/test_data.py | 8 +- .../emass_client/models/test_results_get.py | 8 +- .../emass_client/models/test_results_post.py | 8 +- .../models/test_results_response_get.py | 8 +- .../models/test_results_response_post.py | 8 +- .../emass_client/models/users.py | 8 +- .../models/workflow_definition_get.py | 8 +- .../workflow_definition_response_get.py | 8 +- .../models/workflow_instance_get.py | 8 +- .../models/workflow_instance_response_get.py | 24 +- .../models/workflow_instances_get.py | 8 +- .../models/workflow_instances_response_get.py | 8 +- ...kflow_instances_response_get_pagination.py | 8 +- src/python_client/emass_client/py.typed | 0 src/python_client/emass_client/rest.py | 13 +- src/python_client/pyproject.toml | 3 +- src/python_client/requirements.txt | 2 +- src/python_client/setup.py | 10 +- src/python_client/test/test_artifacts_api.py | 8 +- .../test/test_artifacts_export_api.py | 8 +- src/python_client/test/test_artifacts_get.py | 8 +- ...est_artifacts_request_delete_body_inner.py | 8 +- .../test/test_artifacts_response_del.py | 8 +- .../test_artifacts_response_del_data_inner.py | 8 +- .../test/test_artifacts_response_get.py | 8 +- .../test/test_artifacts_response_put_post.py | 8 +- ..._artifacts_response_put_post_data_inner.py | 8 +- src/python_client/test/test_cac_api.py | 8 +- src/python_client/test/test_cac_get.py | 8 +- .../test/test_cac_response_get.py | 8 +- .../test/test_cac_response_post.py | 8 +- .../test/test_cac_response_post_data_inner.py | 8 +- .../test/test_cloud_resource_results_api.py | 8 +- .../test/test_cloud_resources_post.py | 8 +- .../test_cloud_resources_response_post.py | 8 +- .../test/test_cmmc_assessments_api.py | 8 +- src/python_client/test/test_cmmc_get.py | 8 +- .../test/test_cmmc_response_get.py | 8 +- .../test/test_connectivity_ccsd.py | 8 +- .../test/test_container_scan_results_api.py | 8 +- .../test/test_containers_resources_post.py | 8 +- .../test/test_containers_response_post.py | 8 +- src/python_client/test/test_controls_api.py | 8 +- src/python_client/test/test_controls_get.py | 8 +- src/python_client/test/test_controls_put.py | 8 +- .../test/test_controls_response_get.py | 8 +- .../test/test_controls_response_put.py | 8 +- .../test/test_dashboard_mock_response.py | 115 +++ ...test_dashboard_mock_response_pagination.py | 96 +++ src/python_client/test/test_dashboards_api.py | 81 ++- .../test/test_definition_transitions.py | 8 +- .../test/test_instances_transitions.py | 8 +- .../test/test_milestone_response_get.py | 8 +- .../test_milestone_response_get_milestone.py | 8 +- .../test/test_milestone_response_post.py | 8 +- .../test/test_milestone_response_put.py | 8 +- src/python_client/test/test_milestones_api.py | 8 +- src/python_client/test/test_milestones_get.py | 8 +- .../test/test_milestones_put_post_delete.py | 8 +- ...st_milestones_request_delete_body_inner.py | 8 +- .../test/test_milestones_required_post.py | 8 +- .../test/test_milestones_required_put.py | 8 +- src/python_client/test/test_mock_object.py | 103 +++ src/python_client/test/test_pac_api.py | 8 +- src/python_client/test/test_pac_get.py | 8 +- src/python_client/test/test_pac_post.py | 8 +- .../test/test_pac_response_get.py | 8 +- .../test/test_pac_response_post.py | 8 +- src/python_client/test/test_poam_api.py | 8 +- src/python_client/test/test_poam_get.py | 8 +- .../test/test_poam_post_put_del.py | 8 +- .../test_poam_request_delete_body_inner.py | 8 +- .../test/test_poam_response_delete.py | 8 +- .../test/test_poam_response_get_poams.py | 8 +- .../test/test_poam_response_get_systems.py | 8 +- .../test/test_poam_response_post.py | 8 +- .../test/test_poam_response_put.py | 8 +- src/python_client/test/test_register.py | 8 +- src/python_client/test/test_register_data.py | 8 +- .../test_register_user_request_post_body.py | 8 +- .../test/test_registration_api.py | 8 +- src/python_client/test/test_response200.py | 8 +- src/python_client/test/test_response201.py | 8 +- .../test/test_response201_meta.py | 8 +- src/python_client/test/test_response400.py | 8 +- .../test/test_response400_meta.py | 8 +- src/python_client/test/test_response401.py | 8 +- .../test/test_response401_meta.py | 8 +- src/python_client/test/test_response403.py | 8 +- .../test/test_response403_meta.py | 8 +- src/python_client/test/test_response404.py | 8 +- src/python_client/test/test_response405.py | 8 +- .../test/test_response405_meta.py | 8 +- src/python_client/test/test_response411.py | 8 +- .../test/test_response411_meta.py | 8 +- src/python_client/test/test_response490.py | 8 +- .../test/test_response490_meta.py | 8 +- src/python_client/test/test_response500.py | 8 +- .../test/test_response500_meta.py | 8 +- src/python_client/test/test_role_category.py | 8 +- src/python_client/test/test_roles.py | 8 +- src/python_client/test/test_ssps.py | 8 +- src/python_client/test/test_stage.py | 8 +- .../test/test_static_code_application.py | 8 +- .../test/test_static_code_post.py | 8 +- .../test_static_code_request_post_body.py | 8 +- ...atic_code_request_post_body_application.py | 8 +- .../test/test_static_code_response_post.py | 8 +- .../test/test_static_code_scans_api.py | 8 +- .../test/test_success200_response.py | 8 +- .../test_success200_response_data_inner.py | 8 +- .../test/test_system_response.py | 12 +- .../test/test_system_roles_api.py | 8 +- .../test_system_roles_category_response.py | 8 +- .../test/test_system_roles_response.py | 8 +- .../test_system_roles_response_data_inner.py | 8 +- src/python_client/test/test_systems.py | 12 +- src/python_client/test/test_systems_api.py | 8 +- .../test/test_systems_response.py | 12 +- src/python_client/test/test_test.py | 8 +- src/python_client/test/test_test_api.py | 8 +- src/python_client/test/test_test_data.py | 8 +- .../test/test_test_results_api.py | 8 +- .../test/test_test_results_get.py | 8 +- .../test/test_test_results_post.py | 8 +- .../test/test_test_results_response_get.py | 8 +- .../test/test_test_results_response_post.py | 8 +- src/python_client/test/test_users.py | 8 +- .../test/test_workflow_definition_get.py | 8 +- .../test_workflow_definition_response_get.py | 8 +- .../test/test_workflow_definitions_api.py | 8 +- .../test/test_workflow_instance_get.py | 8 +- .../test_workflow_instance_response_get.py | 50 +- .../test/test_workflow_instances_api.py | 8 +- .../test/test_workflow_instances_get.py | 8 +- .../test_workflow_instances_response_get.py | 8 +- ...kflow_instances_response_get_pagination.py | 8 +- src/ruby_client/.openapi-generator/FILES | 9 + src/ruby_client/.travis.yml | 2 +- src/ruby_client/README.md | 68 +- src/ruby_client/docs/DashboardMockResponse.md | 22 + .../docs/DashboardMockResponsePagination.md | 28 + src/ruby_client/docs/DashboardsApi.md | 478 +++++++++--- src/ruby_client/docs/MockObject.md | 42 ++ src/ruby_client/docs/Systems.md | 6 +- .../docs/WorkflowInstanceResponseGet.md | 2 +- src/ruby_client/emass_client.gemspec | 2 +- src/ruby_client/lib/emass_client.rb | 5 +- .../lib/emass_client/api/artifacts_api.rb | 2 +- .../emass_client/api/artifacts_export_api.rb | 2 +- .../lib/emass_client/api/cac_api.rb | 2 +- .../api/cloud_resource_results_api.rb | 2 +- .../emass_client/api/cmmc_assessments_api.rb | 2 +- .../api/container_scan_results_api.rb | 2 +- .../lib/emass_client/api/controls_api.rb | 2 +- .../lib/emass_client/api/dashboards_api.rb | 325 +++++++-- .../lib/emass_client/api/milestones_api.rb | 2 +- .../lib/emass_client/api/pac_api.rb | 2 +- .../lib/emass_client/api/poam_api.rb | 2 +- .../lib/emass_client/api/registration_api.rb | 2 +- .../emass_client/api/static_code_scans_api.rb | 2 +- .../lib/emass_client/api/system_roles_api.rb | 2 +- .../lib/emass_client/api/systems_api.rb | 2 +- .../lib/emass_client/api/test_api.rb | 2 +- .../lib/emass_client/api/test_results_api.rb | 2 +- .../api/workflow_definitions_api.rb | 2 +- .../api/workflow_instances_api.rb | 2 +- .../lib/emass_client/api_client.rb | 2 +- src/ruby_client/lib/emass_client/api_error.rb | 2 +- .../lib/emass_client/configuration.rb | 2 +- .../lib/emass_client/models/artifacts_get.rb | 2 +- .../artifacts_request_delete_body_inner.rb | 2 +- .../models/artifacts_response_del.rb | 2 +- .../artifacts_response_del_data_inner.rb | 2 +- .../models/artifacts_response_get.rb | 2 +- .../models/artifacts_response_put_post.rb | 2 +- .../artifacts_response_put_post_data_inner.rb | 2 +- .../lib/emass_client/models/cac_get.rb | 2 +- .../emass_client/models/cac_response_get.rb | 2 +- .../emass_client/models/cac_response_post.rb | 2 +- .../models/cac_response_post_data_inner.rb | 2 +- .../models/cloud_resources_post.rb | 2 +- .../models/cloud_resources_response_post.rb | 2 +- .../lib/emass_client/models/cmmc_get.rb | 2 +- .../emass_client/models/cmmc_response_get.rb | 2 +- .../emass_client/models/connectivity_ccsd.rb | 2 +- .../models/containers_resources_post.rb | 2 +- .../models/containers_response_post.rb | 2 +- .../lib/emass_client/models/controls_get.rb | 2 +- .../lib/emass_client/models/controls_put.rb | 2 +- .../models/controls_response_get.rb | 2 +- .../models/controls_response_put.rb | 2 +- .../models/dashboard_mock_response.rb | 239 ++++++ .../dashboard_mock_response_pagination.rb | 264 +++++++ .../models/definition_transitions.rb | 2 +- .../models/instances_transitions.rb | 2 +- .../models/milestone_response_get.rb | 2 +- .../milestone_response_get_milestone.rb | 2 +- .../models/milestone_response_post.rb | 2 +- .../models/milestone_response_put.rb | 2 +- .../lib/emass_client/models/milestones_get.rb | 2 +- .../models/milestones_put_post_delete.rb | 2 +- .../milestones_request_delete_body_inner.rb | 2 +- .../models/milestones_required_post.rb | 2 +- .../models/milestones_required_put.rb | 2 +- .../lib/emass_client/models/mock_object.rb | 343 +++++++++ .../lib/emass_client/models/pac_get.rb | 2 +- .../lib/emass_client/models/pac_post.rb | 2 +- .../emass_client/models/pac_response_get.rb | 2 +- .../emass_client/models/pac_response_post.rb | 2 +- .../lib/emass_client/models/poam_get.rb | 2 +- .../emass_client/models/poam_post_put_del.rb | 2 +- .../models/poam_request_delete_body_inner.rb | 2 +- .../models/poam_response_delete.rb | 2 +- .../models/poam_response_get_poams.rb | 2 +- .../models/poam_response_get_systems.rb | 2 +- .../emass_client/models/poam_response_post.rb | 2 +- .../emass_client/models/poam_response_put.rb | 2 +- .../lib/emass_client/models/register.rb | 2 +- .../lib/emass_client/models/register_data.rb | 2 +- .../models/register_user_request_post_body.rb | 2 +- .../lib/emass_client/models/response200.rb | 2 +- .../lib/emass_client/models/response201.rb | 2 +- .../emass_client/models/response201_meta.rb | 2 +- .../lib/emass_client/models/response400.rb | 2 +- .../emass_client/models/response400_meta.rb | 2 +- .../lib/emass_client/models/response401.rb | 2 +- .../emass_client/models/response401_meta.rb | 2 +- .../lib/emass_client/models/response403.rb | 2 +- .../emass_client/models/response403_meta.rb | 2 +- .../lib/emass_client/models/response404.rb | 2 +- .../lib/emass_client/models/response405.rb | 2 +- .../emass_client/models/response405_meta.rb | 2 +- .../lib/emass_client/models/response411.rb | 2 +- .../emass_client/models/response411_meta.rb | 2 +- .../lib/emass_client/models/response490.rb | 2 +- .../emass_client/models/response490_meta.rb | 2 +- .../lib/emass_client/models/response500.rb | 2 +- .../emass_client/models/response500_meta.rb | 2 +- .../lib/emass_client/models/role_category.rb | 2 +- .../lib/emass_client/models/roles.rb | 2 +- .../lib/emass_client/models/ssps.rb | 2 +- .../lib/emass_client/models/stage.rb | 2 +- .../models/static_code_application.rb | 2 +- .../emass_client/models/static_code_post.rb | 2 +- .../models/static_code_request_post_body.rb | 2 +- ...atic_code_request_post_body_application.rb | 2 +- .../models/static_code_response_post.rb | 2 +- .../models/success200_response.rb | 2 +- .../models/success200_response_data_inner.rb | 2 +- .../emass_client/models/system_response.rb | 2 +- .../models/system_roles_category_response.rb | 2 +- .../models/system_roles_response.rb | 2 +- .../system_roles_response_data_inner.rb | 2 +- .../lib/emass_client/models/systems.rb | 26 +- .../emass_client/models/systems_response.rb | 2 +- .../lib/emass_client/models/test.rb | 2 +- .../lib/emass_client/models/test_data.rb | 2 +- .../emass_client/models/test_results_get.rb | 2 +- .../emass_client/models/test_results_post.rb | 2 +- .../models/test_results_response_get.rb | 2 +- .../models/test_results_response_post.rb | 2 +- .../lib/emass_client/models/users.rb | 2 +- .../models/workflow_definition_get.rb | 2 +- .../workflow_definition_response_get.rb | 2 +- .../models/workflow_instance_get.rb | 2 +- .../models/workflow_instance_response_get.rb | 8 +- .../models/workflow_instances_get.rb | 2 +- .../models/workflow_instances_response_get.rb | 2 +- ...kflow_instances_response_get_pagination.rb | 2 +- src/ruby_client/lib/emass_client/version.rb | 4 +- .../spec/api/artifacts_api_spec.rb | 2 +- .../spec/api/artifacts_export_api_spec.rb | 2 +- src/ruby_client/spec/api/cac_api_spec.rb | 2 +- .../api/cloud_resource_results_api_spec.rb | 2 +- .../spec/api/cmmc_assessments_api_spec.rb | 2 +- .../api/container_scan_results_api_spec.rb | 2 +- src/ruby_client/spec/api/controls_api_spec.rb | 2 +- .../spec/api/dashboards_api_spec.rb | 99 ++- .../spec/api/milestones_api_spec.rb | 2 +- src/ruby_client/spec/api/pac_api_spec.rb | 2 +- src/ruby_client/spec/api/poam_api_spec.rb | 2 +- .../spec/api/registration_api_spec.rb | 2 +- .../spec/api/static_code_scans_api_spec.rb | 2 +- .../spec/api/system_roles_api_spec.rb | 2 +- src/ruby_client/spec/api/systems_api_spec.rb | 2 +- src/ruby_client/spec/api/test_api_spec.rb | 2 +- .../spec/api/test_results_api_spec.rb | 2 +- .../spec/api/workflow_definitions_api_spec.rb | 2 +- .../spec/api/workflow_instances_api_spec.rb | 2 +- src/ruby_client/spec/api_client_spec.rb | 2 +- src/ruby_client/spec/configuration_spec.rb | 2 +- .../spec/models/artifacts_get_spec.rb | 2 +- ...rtifacts_request_delete_body_inner_spec.rb | 2 +- .../artifacts_response_del_data_inner_spec.rb | 2 +- .../models/artifacts_response_del_spec.rb | 2 +- .../models/artifacts_response_get_spec.rb | 2 +- ...facts_response_put_post_data_inner_spec.rb | 2 +- .../artifacts_response_put_post_spec.rb | 2 +- src/ruby_client/spec/models/cac_get_spec.rb | 2 +- .../spec/models/cac_response_get_spec.rb | 2 +- .../cac_response_post_data_inner_spec.rb | 2 +- .../spec/models/cac_response_post_spec.rb | 2 +- .../spec/models/cloud_resources_post_spec.rb | 2 +- .../cloud_resources_response_post_spec.rb | 2 +- src/ruby_client/spec/models/cmmc_get_spec.rb | 2 +- .../spec/models/cmmc_response_get_spec.rb | 2 +- .../spec/models/connectivity_ccsd_spec.rb | 2 +- .../models/containers_resources_post_spec.rb | 2 +- .../models/containers_response_post_spec.rb | 2 +- .../spec/models/controls_get_spec.rb | 2 +- .../spec/models/controls_put_spec.rb | 2 +- .../spec/models/controls_response_get_spec.rb | 2 +- .../spec/models/controls_response_put_spec.rb | 2 +- ...dashboard_mock_response_pagination_spec.rb | 64 ++ .../models/dashboard_mock_response_spec.rb | 46 ++ .../models/definition_transitions_spec.rb | 2 +- .../spec/models/instances_transitions_spec.rb | 2 +- .../milestone_response_get_milestone_spec.rb | 2 +- .../models/milestone_response_get_spec.rb | 2 +- .../models/milestone_response_post_spec.rb | 2 +- .../models/milestone_response_put_spec.rb | 2 +- .../spec/models/milestones_get_spec.rb | 2 +- .../models/milestones_put_post_delete_spec.rb | 2 +- ...lestones_request_delete_body_inner_spec.rb | 2 +- .../models/milestones_required_post_spec.rb | 2 +- .../models/milestones_required_put_spec.rb | 2 +- .../spec/models/mock_object_spec.rb | 106 +++ src/ruby_client/spec/models/pac_get_spec.rb | 2 +- src/ruby_client/spec/models/pac_post_spec.rb | 2 +- .../spec/models/pac_response_get_spec.rb | 2 +- .../spec/models/pac_response_post_spec.rb | 2 +- src/ruby_client/spec/models/poam_get_spec.rb | 2 +- .../spec/models/poam_post_put_del_spec.rb | 2 +- .../poam_request_delete_body_inner_spec.rb | 2 +- .../spec/models/poam_response_delete_spec.rb | 2 +- .../models/poam_response_get_poams_spec.rb | 2 +- .../models/poam_response_get_systems_spec.rb | 2 +- .../spec/models/poam_response_post_spec.rb | 2 +- .../spec/models/poam_response_put_spec.rb | 2 +- .../spec/models/register_data_spec.rb | 2 +- src/ruby_client/spec/models/register_spec.rb | 2 +- .../register_user_request_post_body_spec.rb | 2 +- .../spec/models/response200_spec.rb | 2 +- .../spec/models/response201_meta_spec.rb | 2 +- .../spec/models/response201_spec.rb | 2 +- .../spec/models/response400_meta_spec.rb | 2 +- .../spec/models/response400_spec.rb | 2 +- .../spec/models/response401_meta_spec.rb | 2 +- .../spec/models/response401_spec.rb | 2 +- .../spec/models/response403_meta_spec.rb | 2 +- .../spec/models/response403_spec.rb | 2 +- .../spec/models/response404_spec.rb | 2 +- .../spec/models/response405_meta_spec.rb | 2 +- .../spec/models/response405_spec.rb | 2 +- .../spec/models/response411_meta_spec.rb | 2 +- .../spec/models/response411_spec.rb | 2 +- .../spec/models/response490_meta_spec.rb | 2 +- .../spec/models/response490_spec.rb | 2 +- .../spec/models/response500_meta_spec.rb | 2 +- .../spec/models/response500_spec.rb | 2 +- .../spec/models/role_category_spec.rb | 2 +- src/ruby_client/spec/models/roles_spec.rb | 2 +- src/ruby_client/spec/models/ssps_spec.rb | 2 +- src/ruby_client/spec/models/stage_spec.rb | 2 +- .../models/static_code_application_spec.rb | 2 +- .../spec/models/static_code_post_spec.rb | 2 +- ...code_request_post_body_application_spec.rb | 2 +- .../static_code_request_post_body_spec.rb | 2 +- .../models/static_code_response_post_spec.rb | 2 +- .../success200_response_data_inner_spec.rb | 2 +- .../spec/models/success200_response_spec.rb | 2 +- .../spec/models/system_response_spec.rb | 2 +- .../system_roles_category_response_spec.rb | 2 +- .../system_roles_response_data_inner_spec.rb | 2 +- .../spec/models/system_roles_response_spec.rb | 2 +- .../spec/models/systems_response_spec.rb | 2 +- src/ruby_client/spec/models/systems_spec.rb | 14 +- src/ruby_client/spec/models/test_data_spec.rb | 2 +- .../spec/models/test_results_get_spec.rb | 2 +- .../spec/models/test_results_post_spec.rb | 2 +- .../models/test_results_response_get_spec.rb | 2 +- .../models/test_results_response_post_spec.rb | 2 +- src/ruby_client/spec/models/test_spec.rb | 2 +- src/ruby_client/spec/models/users_spec.rb | 2 +- .../models/workflow_definition_get_spec.rb | 2 +- .../workflow_definition_response_get_spec.rb | 2 +- .../spec/models/workflow_instance_get_spec.rb | 2 +- .../workflow_instance_response_get_spec.rb | 2 +- .../models/workflow_instances_get_spec.rb | 2 +- ..._instances_response_get_pagination_spec.rb | 2 +- .../workflow_instances_response_get_spec.rb | 2 +- src/ruby_client/spec/spec_helper.rb | 2 +- src/typescript_client/README.md | 10 +- src/typescript_client/api.ts | 688 +++++++++++++++--- src/typescript_client/base.ts | 2 +- src/typescript_client/common.ts | 2 +- src/typescript_client/configuration.ts | 2 +- src/typescript_client/index.ts | 2 +- src/typescript_client/package.json | 2 +- 527 files changed, 6135 insertions(+), 1850 deletions(-) create mode 100644 src/python_client/docs/DashboardMockResponse.md create mode 100644 src/python_client/docs/DashboardMockResponsePagination.md create mode 100644 src/python_client/docs/MockObject.md create mode 100644 src/python_client/emass_client/models/dashboard_mock_response.py create mode 100644 src/python_client/emass_client/models/dashboard_mock_response_pagination.py create mode 100644 src/python_client/emass_client/models/mock_object.py create mode 100644 src/python_client/emass_client/py.typed create mode 100644 src/python_client/test/test_dashboard_mock_response.py create mode 100644 src/python_client/test/test_dashboard_mock_response_pagination.py create mode 100644 src/python_client/test/test_mock_object.py create mode 100644 src/ruby_client/docs/DashboardMockResponse.md create mode 100644 src/ruby_client/docs/DashboardMockResponsePagination.md create mode 100644 src/ruby_client/docs/MockObject.md create mode 100644 src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb create mode 100644 src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb create mode 100644 src/ruby_client/lib/emass_client/models/mock_object.rb create mode 100644 src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb create mode 100644 src/ruby_client/spec/models/dashboard_mock_response_spec.rb create mode 100644 src/ruby_client/spec/models/mock_object_spec.rb diff --git a/.github/workflows/generate_docs.yml b/.github/workflows/generate_docs.yml index a54d5466..a7c9c541 100644 --- a/.github/workflows/generate_docs.yml +++ b/.github/workflows/generate_docs.yml @@ -1,6 +1,7 @@ name: Generate eMASS Documentation # Run on each push to main +# For testing use the PR name for 'branches:' - once done testing revert the 'branches:' name to main on: push: branches: [ main ] diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml index 5eb61f4c..03b848dc 100644 --- a/.github/workflows/gh-pages.yml +++ b/.github/workflows/gh-pages.yml @@ -1,3 +1,4 @@ +# For testing use the PR name for 'branches:' - once done testing revert the 'branches:' name to main name: Deploy to GitHub Pages on: push: diff --git a/.github/workflows/publish-to-test-pypi.yml b/.github/workflows/publish-to-test-pypi.yml index 10d97e57..ac240aae 100644 --- a/.github/workflows/publish-to-test-pypi.yml +++ b/.github/workflows/publish-to-test-pypi.yml @@ -1,19 +1,27 @@ # publish a python package to the test pipy registry - await until the generate clients finishes name: Publish Python 🐍 distributions 📦 to TestPyPI -# Push to TestPyPI unconditionally (need to rev version or del/yank same ver) -# Used for testing the python package - to test comment the +#----------------------------------------------------------------------------------- +# Push to TestPyPI unconditionally (need to rev version, del/yank ver will not work) +# +# For testing use: +# on: push +# (push to the TestPyPi registry on every push during development) +# +# Once test is completed use: # on: # workflow_run: -# workflows: ['generate-eMASS-clients'] +# workflows: [Generate OpenAPI Clients] -> old ['generate-eMASS-clients'] # types: # - completed -# and simply use on: push +#----------------------------------------------------------------------------------- + on: workflow_run: - workflows: ['generate-eMASS-clients'] + workflows: [Generate OpenAPI Clients] types: - completed +# on: push jobs: build-n-publish: diff --git a/docs/developers.md b/docs/developers.md index c11a7bb3..f3108172 100644 --- a/docs/developers.md +++ b/docs/developers.md @@ -65,7 +65,7 @@ curl -X GET "http://localhost:4010/api/systems?policy=rmf" -H "accept: applicat ## Building an eMASS Client SDK The API clients are generated utilizing the [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) CLI. -**Note:** Currently there are two (2) client SDKs (ruby, and typscript-axios) that are automatically generated utilizing GitHub action implemented within this repository. They are generated when a push to the main branch occurs and the API specification file has been modified. +**Note:** Currently there are three (3) client SDKs (ruby, typscript-axios, and python) that are automatically generated utilizing GitHub action implemented within this repository. They are generated when a push to the main branch occurs and the API specification file has been modified. ### Generate an eMASS Client Follow these steps to generate an eMASS client for additional supported language provided by the [OpenAPI Generator](https://github.com/OpenAPITools/openapi-generator) CLI: @@ -122,6 +122,9 @@ Follow these steps to generate an eMASS client for additional supported language ``` openapi-generators/openapitools-generator-action@v1 ``` + +An OpenAPI Generator CLI Docker Image solution is available and documented [here](https://github.com/OpenAPITools/openapi-generator#16---docker) as a Public Pre-built Docker image. + --- NOTICE diff --git a/eMASSRestOpenApi.yaml b/eMASSRestOpenApi.yaml index 806878f6..8a903e8c 100644 --- a/eMASSRestOpenApi.yaml +++ b/eMASSRestOpenApi.yaml @@ -58,7 +58,7 @@ info: name: eMASS Tier III support url: 'https://www.dcsa.mil/is/emass/' email: disa.meade.id.mbx.emass-tier-iii-support@mail.mil - version: 'v3.9' + version: 'v3.10' externalDocs: description: eMASS New User Registration (requires CAC authentication) @@ -100,9 +100,10 @@ tags: - If a system is dual-policy enabled, the returned system role information will default to the RMF policy information unless otherwise specified. - name: Controls - description: "The Controls endpoints provide the ability to view, add, and update + description: > + The Controls endpoints provide the ability to view, add, and update Security Control information to a system for both the Implementation Plan and - Risk Assessment." + Risk Assessment. - name: Test Results description: > The Test Results endpoints provide the ability to view and add test results for a @@ -2648,14 +2649,18 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------# + # D A S H B O A R D S # + #---------------------------------------------------------------------------# + #---------------------------------------------------------------------------- - # Dashboards + # System Status Dashboards #---------------------------------------------------------------------------- /api/dashboards/system-status-details: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Status Details" description: |- Get systems status detail dashboard information. operationId: getSystemStatusDetails @@ -2714,11 +2719,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Enterprise Security Controls Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-control-compliance-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Control Compliance Summary" description: |- Get systems control compliance summary dashboard information. operationId: getSystemControlComplianceSummary @@ -2781,7 +2789,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Control Compliance Details" description: |- Get systems security control details dashboard information. operationId: getSystemSecurityControlDetails @@ -2844,7 +2852,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Assessment Procedures Details" description: |- Get systems assessement procdures details dashboard information. operationId: getSystemAssessmentProceduresDetails @@ -2903,11 +2911,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Enterprise POA&M Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-poam-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System POA&M Summary" description: |- Get systems POA&Ms summary dashboard information. operationId: getSystemPoamSummary @@ -2970,7 +2981,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System POA&M Details" description: |- Get system POA&Ms details dashboard information. operationId: getSystemPoamDetails @@ -3029,11 +3040,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Enterprise Artifacts Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-artifacts-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Artifacts Summary" description: |- Get system Artifacts summary information. operationId: getSystemArtifactsSummary @@ -3096,7 +3110,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Artifacts Details" description: |- Get system Artifacts details information. operationId: getSystemArtifactsDetails @@ -3155,11 +3169,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Hardware Baseline Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-hardware-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Hardware Summary" description: |- Get system hardware summary dashboard information. operationId: getSystemHardwareSummary @@ -3222,7 +3239,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Hardware Details" description: |- Get system hardware details dashboard information. operationId: getSystemHardwareDetails @@ -3281,11 +3298,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Enterprise Sensor-based Hardware Resources Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-sensor-hardware-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Sensor Hardware Summary" description: |- Get system sensor hardware summary dashboard information. operationId: getSystemSensorHardwareSummary @@ -3348,7 +3368,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Sensor Hardware Details" description: |- Get system sensor hardware details dashboard information. operationId: getSystemSensorHardwareDetails @@ -3406,12 +3426,144 @@ paths: application/json: schema: "$ref": "#/components/schemas/Response500" + + #---------------------------------------------------------------------------- + # Software Baseline Dashboards + #---------------------------------------------------------------------------- + /api/dashboards/system-software-summary: + get: + tags: + - Dashboards + summary: "System Software Summary" + description: |- + Get system software summary dashboard information. + operationId: getSystemSoftwareSummary + parameters: + - $ref: '#/components/parameters/orgId' + - $ref: '#/components/parameters/dashboardExcludeInherited' + - $ref: '#/components/parameters/dashboardPageIndex' + - $ref: '#/components/parameters/dashboardPageSize' + responses: + '200': + description: "Successful response" + content: + application/json: + schema: + type: object + '400': + description: "Bad Request" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response400" + '401': + description: "Unauthorized" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response401" + '403': + description: "Forbidden" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response403" + '404': + description: "Not Found" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response404" + '405': + description: "Method Not Allowed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response405" + '490': + description: "API Rule Failed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response490" + '500': + description: "Internal Server Error" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response500" + /api/dashboards/system-software-details: + get: + tags: + - Dashboards + summary: "System Software Details" + description: |- + Get system software details dashboard information. + operationId: getSystemSoftwareDetails + parameters: + - $ref: '#/components/parameters/orgId' + - $ref: '#/components/parameters/dashboardExcludeInherited' + - $ref: '#/components/parameters/dashboardPageIndex' + - $ref: '#/components/parameters/dashboardPageSize' + responses: + '200': + description: "Successful response" + content: + application/json: + schema: + type: object + '400': + description: "Bad Request" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response400" + '401': + description: "Unauthorized" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response401" + '403': + description: "Forbidden" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response403" + '404': + description: "Not Found" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response404" + '405': + description: "Method Not Allowed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response405" + '490': + description: "API Rule Failed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response490" + '500': + description: "Internal Server Error" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response500" + + #---------------------------------------------------------------------------- + # Ports and Protocols Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-ports-protocols-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Ports/Protocols Summary" description: |- Get system ports and protocols summary dashboard information. operationId: getSystemPortsProtocolsSummary @@ -3474,7 +3626,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Ports/Protocols Details" description: |- Get system ports and protocols details dashboard information. operationId: getSystemPortsProtocolsDetails @@ -3533,11 +3685,80 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # System CONMON Integration Status Dashboards + #---------------------------------------------------------------------------- + /api/dashboards/system-conmon-integration-status-summary: + get: + tags: + - Dashboards + summary: "System CONMON Integration Status" + description: |- + Get system CONMON integration status dashboard information. + operationId: getSystemCommonIntegrationStatusSummary + parameters: + - $ref: '#/components/parameters/orgId' + - $ref: '#/components/parameters/dashboardExcludeInherited' + - $ref: '#/components/parameters/dashboardPageIndex' + - $ref: '#/components/parameters/dashboardPageSize' + responses: + '200': + description: "Successful response" + content: + application/json: + schema: + type: object + '400': + description: "Bad Request" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response400" + '401': + description: "Unauthorized" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response401" + '403': + description: "Forbidden" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response403" + '404': + description: "Not Found" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response404" + '405': + description: "Method Not Allowed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response405" + '490': + description: "API Rule Failed" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response490" + '500': + description: "Internal Server Error" + content: + application/json: + schema: + "$ref": "#/components/schemas/Response500" + + #---------------------------------------------------------------------------- + # System Associations Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-associations-details: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Associations Details" description: |- Get system associations details dashboard information. operationId: getSystemAssociationsDetails @@ -3596,11 +3817,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Users Dashboards + #---------------------------------------------------------------------------- /api/dashboards/user-system-assignments-details: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "User System Assignments Details" description: |- Get user system assignments details dashboard information. operationId: getUserSystemAssignmentsDetails @@ -3659,11 +3883,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Privacy Compliance Dashboards + #---------------------------------------------------------------------------- /api/dashboards/system-privacy-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "System Privacy Summary" description: |- Get user system privacy summary dashboard information. operationId: getSystemPrivacySummary @@ -3726,7 +3953,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA OMB FISMA SAOP Summary" description: |- Get VA OMB-FISMA SAOP summary dashboard information. operationId: getVaOmbFsmaSaopSummary @@ -3785,11 +4012,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # System A&A Summary Dashboards + #---------------------------------------------------------------------------- /api/dashboards/va-system-aa-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System A&A Summary" description: |- Get VA system A&A summary dashboard information. operationId: getVaSystemAaSummary @@ -3848,11 +4078,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # System A2.0 Summary Dashboards + #---------------------------------------------------------------------------- /api/dashboards/va-system-a2-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System A2.0 Summary" description: |- Get VA system A2.0 summary dashboard information. operationId: getVaSystemA2Summary @@ -3911,11 +4144,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # System P.L. 109 Reporting Summary Dashboards + #---------------------------------------------------------------------------- /api/dashboards/va-system-pl-109-reporting-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System P.L. 109 Reporting Summary" description: |- Get VA system P.L. 109 reporting summary dashboard information. operationId: getVaSystemPl109ReportingSummary @@ -3974,11 +4210,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # FISMA Inventory Summary Dashboards + #---------------------------------------------------------------------------- /api/dashboards/va-system-fisma-inventory-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System FISMA Inventory Summary" description: |- Get VA system FISMA inventory summary dashboard information. operationId: getVaSystemFismaInvetorySummary @@ -4041,7 +4280,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System FISMA Inventory Crypto Summary" description: |- Get VA system FISMA inventory crypto summary dashboard information. operationId: getVaSystemFismaInvetoryCryptoSummary @@ -4100,11 +4339,14 @@ paths: schema: "$ref": "#/components/schemas/Response500" + #---------------------------------------------------------------------------- + # Threat Risks Dashboards + #---------------------------------------------------------------------------- /api/dashboards/va-system-threat-risks-summary: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System Threat Risks Summary" description: |- Get VA system threat risk summary dashboard information. operationId: getVaSystemThreatRiskSummary @@ -4167,7 +4409,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System Threat Sources Details" description: |- Get VA system threat source details dashboard information. operationId: getVaSystemThreatSourceDetails @@ -4230,7 +4472,7 @@ paths: get: tags: - Dashboards - summary: "Get dashboard information" + summary: "VA System Threat Architecture Details" description: |- Get VA system threat architecture details dashboard information. operationId: getVaSystemThreatArchitectureDetails @@ -5266,7 +5508,7 @@ components: isBaseline: type: boolean description: "[Optional] True/false flag for providing results as baseline. If true, all existing compliance results for the resourceId will be replaced by results in the current call" - example: "true" + example: true tags: type: object description: "[Optional] Informational tags associated to results for other metadata" @@ -5294,7 +5536,7 @@ components: isCompliant: type: boolean description: "[Required] Compliance status of the policy for the identified cloud resource" - example: "false" + example: false control: type: string description: "[Optional] Comma separated correlation to Security Control (e.g. exact NIST Control acronym)" @@ -5369,7 +5611,7 @@ components: isBaseline: type: boolean description: "[Optional] True/false flag for providing results as baseline. If true, all existing compliance results for the provided benchmark within the container will be replaced by results in the current call" - example: "false" + example: false results: type: array items: @@ -5445,14 +5687,14 @@ components: rawSeverity: type: string description: "[Optional] Scan vulnerability ratting" - example: "Moderate" enum: [Low, Medium, Moderate, High, Critical] + example: "Moderate" codeCheckName: type: string description: "[Required] Name of the software vulnerability or weakness." - example: "Hidden Field" x-faker: - random.arrayElement: [['Hidden Field', 'Redundant Check', 'Invalid Field', 'Vulnerable Field']] + random.arrayElement: [['Hidden Field', 'Redundant Check', 'Invalid Field', 'Vulnerable Field']] + example: "Hidden Field" count: type: integer format: int64 @@ -5957,9 +6199,7 @@ components: meta: "$ref": "#/components/schemas/Response200" data: - type: array - items: - $ref: '#/components/schemas/WorkflowInstanceGet' + $ref: '#/components/schemas/WorkflowInstanceGet' Success200Response: title: "Default success response schema" type: object @@ -5981,7 +6221,40 @@ components: $ref: '#/components/schemas/Errors' Empty200Response: type: object - + DashboardMockResponse: + title: "Dashboards GET mock response" + type: object + additionalProperties: false + properties: + meta: + "$ref": "#/components/schemas/Response200" + data: + type: array + items: + $ref: "#/components/schemas/MockObject" + pagination: + type: object + properties: + totalCount: + type: integer + example: 2 + totalPages: + type: integer + example: 1 + pageIndex: + type: integer + example: 2 + pageSize: + type: integer + example: 20000 + prevPageUrl: + type: string + x-faker: internet.url + example: "https://myfakeurl.reponse.page.com?PreviousPage" + nextPageUrl: + type: string + x-faker: internet.url + example: "https://myfakeurl.reponse.page.com?NextPage" #---------------------------------------------------------------------------- # Supporting 200 Responses - Endpoint response - returned values #---------------------------------------------------------------------------- @@ -6065,8 +6338,8 @@ components: type: string nullable: true description: "[Read-Only] Registration types parameters (assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider.)" - example: "Assess and Authorize" enum: ["Assess and Authorize", "Assess Only", "Guest", "Regular", "Functional", "Cloud Service Provider", "Common Control Provider"] + example: "Assess and Authorize" name: type: string nullable: true @@ -6077,9 +6350,9 @@ components: type: string nullable: true description: "[Read-only] Acronym of the system record." - example: "PM-6" x-faker: - random.arrayElement: [["AC-1", "AC-2","S-1","S-23","SI-16","SI-56","UA-16","SI-4(11)"]] + random.arrayElement: [["AC-1", "AC-2","S-1","S-23","SI-16","SI-56","UA-16","SI-4(11)"]] + example: "PM-6" description: type: string nullable: true @@ -6114,8 +6387,8 @@ components: type: string nullable: true description: "[Read-only] Type of the system record. RMF values include the following options (IS Major Application, IS Enclave, Platform IT System). DIACAP values include the following options (Platform IT Interconnection, AIS Application, Outsourced IT-Based Process (DoD-controlled), Enclave, Outsourced IT-Based Process (service provider shared))" - example: "IS Major Application" enum: ["IS Major Application", "IS Enclave", "Platform IT", "Platform IT System", "Platform IT Interconnection", "AIS Application", "Outsourced IT-Based Process (DoD-controlled)", "Enclave", "Outsourced IT-Based Process (service provider shared)"] + example: "IS Major Application" isNSS: type: boolean nullable: true @@ -6166,6 +6439,7 @@ components: "Interim Authorization to Test (IATT)","Denied Authorization to Operate (DATO)","Not Yet Authorized", "Decommissioned","Authorization to Operate (ATO)","Interim Authorization to Operate (IATO)", "Interim Authorization to Test (IATT)","Denied Authorization to Operate (DATO)","Unaccredited","Decommissioned"]] + example: "Not Yet Authorized" authorizationDate: type: integer nullable: true @@ -6182,9 +6456,9 @@ components: type: integer nullable: true description: "[Read-only] Length of system's Authorization. Calculated based off of Authorization Date & Authorization Termination Date." - example: 365 minimum: 28 maximum: 1825 + example: 365 termsForAuth: type: string nullable: true @@ -6195,8 +6469,8 @@ components: type: string nullable: true description: "[Read-only] Status of the approval of the system's RMF Security Plan. Values include the following options (Approved, Denied, Not Yet Approved)." - example: "Approved" enum: ["Approved", "Not Yet Approved", "Denied"] + example: "Approved" securityPlanApprovalDate: type: integer nullable: true @@ -6230,48 +6504,48 @@ components: type: string nullable: true description: "[Read-only] Primary functional area of the system record." - example: "Health/Medical" x-faker: random.arrayElement: [["Allies", "CBRNE", "Civilian Personnel & Readiness", "Command and Control", "Communications", "Communications Security (COMSEC)", "Economic", "Environmental Security", "Facilities", "Finance", "Health/Medical", "Human Resources", "Information Management", "Inspector General", "Intelligence", "Logistics", "Military Personnel and Readiness", "Nuclear", "Nuclear, Chemical, and Biological", "Operations", "Personnel and Readiness", "Procurement/Acquisition", "Reserve Components", "Scientific and Engineering", "Space and Weather", "Test and Evaluation", "Trainers", "Weapons", "Legal", "Transportation", "Not Applicable (N/A)", "Integration and Testing"]] + example: "Health/Medical" secondaryFunctionalArea: type: string nullable: true description: "[Read-only] Secondary functional area of the system record." - example: "Logistics" x-faker: random.arrayElement: [["Allies", "CBRNE", "Civilian Personnel & Readiness", "Command and Control", "Communications", "Communications Security (COMSEC)", "Economic", "Environmental Security", "Facilities", "Finance", "Health/Medical", "Human Resources", "Information Management", "Inspector General", "Intelligence", "Logistics", "Military Personnel and Readiness", "Nuclear", "Nuclear, Chemical, and Biological", "Operations", "Personnel and Readiness", "Procurement/Acquisition", "Reserve Components", "Scientific and Engineering", "Space and Weather", "Test and Evaluation", "Trainers", "Weapons", "Legal", "Transportation", "Not Applicable (N/A)", "Integration and Testing"]] + example: "Logistics" primaryControlSet: type: string nullable: true description: "[Read-only] Primary Control Set of the system record. RMF values include the following options (NIST SP 800-53 Revision 4), DIACAP values include the following options (DoDI 8500.2)" - example: "NIST SP 800-53 Revision 4" enum: ["NIST SP 800-53 Revision 4", "DoDI 8500.2"] + example: "NIST SP 800-53 Revision 4" confidentiality: type: string nullable: true description: "[Read-only] Confidentiality of the system record. RMF values include the following options (High, Moderate, Low)" - example: "Low" enum: ["High", "Moderate", "Low"] + example: "Low" integrity: type: string nullable: true description: "[Read-only] Integrity of the system record. RMF values include the following options (High, Moderate, Low)" - example: "Moderate" enum: ["High", "Moderate", "Low"] + example: "Moderate" availability: type: string nullable: true description: "[Read-only] Availability of the system record. RMF values include the following options (High, Moderate, Low)" - example: "High" enum: ["High", "Moderate", "Low"] + example: "High" appliedOverlays: type: string nullable: true @@ -6282,11 +6556,11 @@ components: type: string nullable: true description: "[Read-only] RMF Activity of the system record." - example: "Maintain ATO and conduct reviews" x-faker: random.arrayElement: [["Initiate and plan C&A", "Initiate and plan cybersecurity Assessment Authorization", "Implement and validate assigned security controls", "Make assessment determination and authorization decision", "Maintain ATO and conduct reviews", "Decommission"]] + example: "Maintain ATO and conduct reviews" crossDomainTicket: type: string nullable: true @@ -6303,14 +6577,14 @@ components: type: string nullable: true description: "[Read-Only] MAC level of the system record." - example: "II" enum: [ "I", "II", "III"] + example: "II" dodConfidentiality: type: string nullable: true description: "[Read-Only] DoD Confidentiality level of the system record." - example: "Public" enum: ["Public", "Sensitive", "Classified"] + example: "Public" contingencyPlanTested: type: boolean nullable: true @@ -6349,8 +6623,8 @@ components: type: string nullable: true description: "[Optional] Values include the following options (Very Low, Low, Moderate,High,Very High)" - example: "Low" enum: ["Low", "Moderate", "High"] + example: "Low" hasCUI: type: boolean nullable: true @@ -6391,8 +6665,8 @@ components: type: string nullable: true description: "[Read-only] Status of the PIA, availability values include the following options (Not Started, In Progress, Completed)" - example: "Not Started" enum: ["Not Started", "In Progress", "Completed"] + example: "Not Started" piaDate: type: integer nullable: true @@ -6402,43 +6676,43 @@ components: type: string nullable: true description: "[Read-only] User-defined field to augment Ad Hoc Reporting." - example: "Test User-defined Field 1" x-faker: - random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + example: "Test User-defined Field 1" userDefinedField2: type: string nullable: true description: "[Read-only] User-defined field to augment Ad Hoc Reporting." - example: "Test User-defined Field 2" x-faker: - random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + example: "Test User-defined Field 2" userDefinedField3: type: string nullable: true description: "[Read-only] User-defined field to augment Ad Hoc Reporting." - example: "Test User-defined Field 3" x-faker: random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + example: "Test User-defined Field 3" userDefinedField4: type: string nullable: true description: "[Read-only] User-defined field to augment Ad Hoc Reporting." - example: "Test User-defined Field 4" x-faker: - random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + example: "Test User-defined Field 4" userDefinedField5: type: string nullable: true description: "[Read-only] User-defined field to augment Ad Hoc Reporting." - example: "Test User-defined Field 5" x-faker: - random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + random.arrayElement: [["Test User-defined Field 1","Test User-defined Field 2","Test User-defined Field 3","Test User-defined Field 4","Test User-defined Field 4"]] + example: "Test User-defined Field 5" currentRmfLifecycleStep: type: string nullable: true description: "[Read-only] Displays the system's current step within the RMF Lifecycle." - example: "4 - Assess" enum: ["1 - Categorize", "2 - Select", "3 - Implement", "4 - Assess", "5 - Authorize", "6 - Monitor"] + example: "4 - Assess" otherInformation: type: string nullable: true @@ -6455,20 +6729,20 @@ components: type: string nullable: true description: "[Read-Only] The overall classification level of information that the System is approved to collect, process, store, and/or distribute." - example: "Unclassified" x-faker: random.arrayElement: [["Public Trust", "For Official Use Only (FOUO)", "Controlled Unclassified Information (CUI)", "Unclassified", "Restricted Data/Formerly Restricted Data", "Sensitive Compartmented Information", - "Special Access Program", "Secret", "Top Secret", "Confidential"]] + "Special Access Program", "Secret", "Top Secret", "Confidential"]] + example: "Unclassified" overallClassification: type: string nullable: true description: "[Read-Only] Same field as highestSystemDataClassification, but displays as overallClassification for NISP only." - example: "Unclassified" x-faker: random.arrayElement: [["Public Trust", "For Official Use Only (FOUO)", "Controlled Unclassified Information (CUI)", "Unclassified", "Restricted Data/Formerly Restricted Data", "Sensitive Compartmented Information", - "Special Access Program", "Secret", "Top Secret", "Confidential"]] + "Special Access Program", "Secret", "Top Secret", "Confidential"]] + example: "Unclassified" isHVA: type: boolean nullable: true @@ -6514,8 +6788,8 @@ components: type: string nullable: true description: "[Read-Only] Values include the following: (Hybrid, Private, Public)" - example: "Public" enum: ["Hybrid", "Private", "Public"] + example: "Public" atcStatus: type: string nullable: true @@ -6523,8 +6797,8 @@ components: [Read-Only] The Authority to Connect decision. Values include the following: (Authority to Connect (ATC), Denial of Authority to Connect (DATC), Not Yet Connected, Decommissioned) - example: "Decommissioned" enum: ["Authority to Connect (ATC)", "Denial of Authority to Connect (DATC)", "Not Yet Connected","Decommissioned"] + example: "Decommissioned" isSaaS: type: boolean nullable: true @@ -6594,6 +6868,20 @@ components: description: "[Read-Only] Is this IS reportable per Federal Information Security Management Act (FISMA) established requirements? VA only" x-faker: random.boolean example: false + groupTagging: + type: string + nullable: true + description: "[Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only." + x-faker: + random.arrayElement: [["Group Tag 1", "Group Tag 2", "Group Tag 3", "Group Tag 4", "Group Tag 5"]] + example: "Group Tag 1" + groupTagDescriptions: + type: string + nullable: true + description: "[Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only." + x-faker: + random.arrayElement: [["Group Tag 1 explanation", "Group Tag 2 explanation", "Group Tag 3 explanation", "Group Tag 4 explanation", "Group Tag 5 explanation"]] + example: "Group Tag 1 explanation" package: type: array nullable: true @@ -7976,7 +8264,78 @@ components: description: "[Read-Only] The beginning stage that is active before performing a transition." x-faker: random.word example: "Not Started" - + MockObject: + title: Object mock data + type: object + additionalProperties: false + properties: + pocOrganization: + type: string + description: "[Required] Organization/Office represented. 100 Characters." + x-faker: company.companyName + example: "Army" + resources: + type: string + description: "[Required] List of resources used. 250 Characters." + x-faker: random.words + example: "Resource text." + owningOrganization: + type: string + nullable: true + description: "[Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy." + x-faker: company.companyName + example: "Defense Information Systems Agency" + secondaryOrganization: + type: string + nullable: true + description: "[Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level." + x-faker: company.companyName + example: "ID31" + pocFirstName: + type: string + description: "[Conditional] First name of POC. 100 Characters." + x-faker: name.firstName + example: "John" + pocLastName: + type: string + description: "[Conditional] Last name of POC. 100 Characters." + x-faker: name.lastName + example: "Smith" + pocEmail: + type: string + description: "[Conditional] Email address of POC. 100 Characters." + x-faker: internet.email + example: "smith@ah.com" + pocPhoneNumber: + type: string + description: "[Conditional] Phone number of POC (area code) ***-**** format. 100 Characters." + x-faker: phone.phoneNumber.email + example: "555-555-5555" + severity: + type: string + description: "[Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High)" + example: "Low" + scheduledCompletionDate: + type: integer + format: int64 + nullable: true + description: "[Conditional] Required for ongoing and completed POA&M items. Unix time format." + example: 1599644800 + completionDate: + type: integer + format: int64 + description: "[Conditional] Field is required for completed POA&M items. Unix time format." + example: 1505916276 + comments: + type: string + description: "[Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters" + x-faker: random.words + example: "Comments text." + isActive: + type: boolean + description: "[Conditional] Optionally used in PUT to delete milestones when updating a POA&M." + x-faker: random.boolean + example: true #---------------------------------------------------------------------------- # HTTP response status code values #---------------------------------------------------------------------------- @@ -8153,6 +8512,7 @@ components: example: "key:value" x-faker: random.arrayElement: [["key: Error message 1","key: Error message 2","key: Error message 3","key: Error message 4","key: Error message 5"]] + #---------------------------------------------------------------------------- # Security schemes - Define the key name and location #---------------------------------------------------------------------------- diff --git a/src/openapi/templates/python/python-generator-config.json b/src/openapi/templates/python/python-generator-config.json index 50827917..5135c601 100644 --- a/src/openapi/templates/python/python-generator-config.json +++ b/src/openapi/templates/python/python-generator-config.json @@ -1,6 +1,6 @@ { "packageName": "emass_client", - "packageVersion": "3.9.1", + "packageVersion": "3.10.0", "projectName": "emass_client_api", "packageUrl": "https://github.com/mitre/emass_client", "licenseInfo": "Apache-2.0" diff --git a/src/openapi/templates/ruby/ruby-generator-config.json b/src/openapi/templates/ruby/ruby-generator-config.json index d04fa743..14e541f0 100644 --- a/src/openapi/templates/ruby/ruby-generator-config.json +++ b/src/openapi/templates/ruby/ruby-generator-config.json @@ -1,6 +1,6 @@ { "gemName": "emass_client", - "gemVersion": "3.9.1", + "gemVersion": "3.10.0", "gemLicense": "Apache-2.0", "enumUnknownDefaultCase": true } \ No newline at end of file diff --git a/src/openapi/templates/typescript/typescript-generator-config.json b/src/openapi/templates/typescript/typescript-generator-config.json index 1b6bffce..7bf2e027 100644 --- a/src/openapi/templates/typescript/typescript-generator-config.json +++ b/src/openapi/templates/typescript/typescript-generator-config.json @@ -1,6 +1,6 @@ { "npmName": "@mitre/emass_client", - "npmVersion": "3.9.1", + "npmVersion": "3.10.0", "npmLicense": "Apache-2.0", "enumUnknownDefaultCase": true } \ No newline at end of file diff --git a/src/python_client/.openapi-generator/FILES b/src/python_client/.openapi-generator/FILES index 9cd0d542..d0d21cf1 100644 --- a/src/python_client/.openapi-generator/FILES +++ b/src/python_client/.openapi-generator/FILES @@ -33,6 +33,8 @@ docs/ControlsGet.md docs/ControlsPut.md docs/ControlsResponseGet.md docs/ControlsResponsePut.md +docs/DashboardMockResponse.md +docs/DashboardMockResponsePagination.md docs/DashboardsApi.md docs/DefinitionTransitions.md docs/InstancesTransitions.md @@ -46,6 +48,7 @@ docs/MilestonesPutPostDelete.md docs/MilestonesRequestDeleteBodyInner.md docs/MilestonesRequiredPost.md docs/MilestonesRequiredPut.md +docs/MockObject.md docs/PACApi.md docs/POAMApi.md docs/PacGet.md @@ -168,6 +171,8 @@ emass_client/models/controls_get.py emass_client/models/controls_put.py emass_client/models/controls_response_get.py emass_client/models/controls_response_put.py +emass_client/models/dashboard_mock_response.py +emass_client/models/dashboard_mock_response_pagination.py emass_client/models/definition_transitions.py emass_client/models/instances_transitions.py emass_client/models/milestone_response_get.py @@ -179,6 +184,7 @@ emass_client/models/milestones_put_post_delete.py emass_client/models/milestones_request_delete_body_inner.py emass_client/models/milestones_required_post.py emass_client/models/milestones_required_put.py +emass_client/models/mock_object.py emass_client/models/pac_get.py emass_client/models/pac_post.py emass_client/models/pac_response_get.py @@ -243,6 +249,7 @@ emass_client/models/workflow_instance_response_get.py emass_client/models/workflow_instances_get.py emass_client/models/workflow_instances_response_get.py emass_client/models/workflow_instances_response_get_pagination.py +emass_client/py.typed emass_client/rest.py git_push.sh pyproject.toml @@ -280,6 +287,8 @@ test/test_controls_get.py test/test_controls_put.py test/test_controls_response_get.py test/test_controls_response_put.py +test/test_dashboard_mock_response.py +test/test_dashboard_mock_response_pagination.py test/test_dashboards_api.py test/test_definition_transitions.py test/test_instances_transitions.py @@ -293,6 +302,7 @@ test/test_milestones_put_post_delete.py test/test_milestones_request_delete_body_inner.py test/test_milestones_required_post.py test/test_milestones_required_put.py +test/test_mock_object.py test/test_pac_api.py test/test_pac_get.py test/test_pac_post.py diff --git a/src/python_client/README.md b/src/python_client/README.md index 441ae797..865ea5d3 100644 --- a/src/python_client/README.md +++ b/src/python_client/README.md @@ -1,4 +1,4 @@ -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -6,9 +6,9 @@ Representational State Transfer (REST) Application Programming Interface (API) s This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -127,32 +127,35 @@ Class | Method | HTTP request | Description *ContainerScanResultsApi* | [**add_container_sans_by_system_id**](docs/ContainerScanResultsApi.md#add_container_sans_by_system_id) | **POST** /api/systems/{systemId}/container-scan-results | Add one or many containers and their scan results *ControlsApi* | [**get_system_controls**](docs/ControlsApi.md#get_system_controls) | **GET** /api/systems/{systemId}/controls | Get control information in a system for one or many controls *ControlsApi* | [**update_control_by_system_id**](docs/ControlsApi.md#update_control_by_system_id) | **PUT** /api/systems/{systemId}/controls | Update control information in a system for one or many controls -*DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | Get dashboard information -*DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | Get dashboard information -*DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information -*DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information -*DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information -*DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information -*DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information -*DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information -*DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information -*DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | Get dashboard information -*DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | Get dashboard information -*DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information -*DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information -*DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | Get dashboard information -*DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | Get dashboard information -*DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information -*DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information -*DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | Get dashboard information -*DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | Get dashboard information -*DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | Get dashboard information +*DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | System Artifacts Details +*DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | System Artifacts Summary +*DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | System Assessment Procedures Details +*DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | System Associations Details +*DashboardsApi* | [**get_system_common_integration_status_summary**](docs/DashboardsApi.md#get_system_common_integration_status_summary) | **GET** /api/dashboards/system-conmon-integration-status-summary | System CONMON Integration Status +*DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | System Control Compliance Summary +*DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | System Hardware Details +*DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | System Hardware Summary +*DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | System POA&M Details +*DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | System POA&M Summary +*DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | System Ports/Protocols Details +*DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | System Ports/Protocols Summary +*DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | System Privacy Summary +*DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | System Control Compliance Details +*DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | System Sensor Hardware Details +*DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | System Sensor Hardware Summary +*DashboardsApi* | [**get_system_software_details**](docs/DashboardsApi.md#get_system_software_details) | **GET** /api/dashboards/system-software-details | System Software Details +*DashboardsApi* | [**get_system_software_summary**](docs/DashboardsApi.md#get_system_software_summary) | **GET** /api/dashboards/system-software-summary | System Software Summary +*DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | System Status Details +*DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | User System Assignments Details +*DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | VA OMB FISMA SAOP Summary +*DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | VA System A2.0 Summary +*DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | VA System A&A Summary +*DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | VA System FISMA Inventory Crypto Summary +*DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | VA System FISMA Inventory Summary +*DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | VA System P.L. 109 Reporting Summary +*DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | VA System Threat Architecture Details +*DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | VA System Threat Risks Summary +*DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | VA System Threat Sources Details *MilestonesApi* | [**add_milestone_by_system_id_and_poam_id**](docs/MilestonesApi.md#add_milestone_by_system_id_and_poam_id) | **POST** /api/systems/{systemId}/poams/{poamId}/milestones | Add milestones to one or many POA&M items in a system *MilestonesApi* | [**delete_milestone**](docs/MilestonesApi.md#delete_milestone) | **DELETE** /api/systems/{systemId}/poams/{poamId}/milestones | Remove milestones in a system for one or many POA&M items *MilestonesApi* | [**get_system_milestones_by_poam_id**](docs/MilestonesApi.md#get_system_milestones_by_poam_id) | **GET** /api/systems/{systemId}/poams/{poamId}/milestones | Get milestones in one or many POA&M items in a system @@ -203,6 +206,8 @@ Class | Method | HTTP request | Description - [ControlsPut](docs/ControlsPut.md) - [ControlsResponseGet](docs/ControlsResponseGet.md) - [ControlsResponsePut](docs/ControlsResponsePut.md) + - [DashboardMockResponse](docs/DashboardMockResponse.md) + - [DashboardMockResponsePagination](docs/DashboardMockResponsePagination.md) - [DefinitionTransitions](docs/DefinitionTransitions.md) - [InstancesTransitions](docs/InstancesTransitions.md) - [MilestoneResponseGet](docs/MilestoneResponseGet.md) @@ -214,6 +219,7 @@ Class | Method | HTTP request | Description - [MilestonesRequestDeleteBodyInner](docs/MilestonesRequestDeleteBodyInner.md) - [MilestonesRequiredPost](docs/MilestonesRequiredPost.md) - [MilestonesRequiredPut](docs/MilestonesRequiredPut.md) + - [MockObject](docs/MockObject.md) - [PacGet](docs/PacGet.md) - [PacPost](docs/PacPost.md) - [PacResponseGet](docs/PacResponseGet.md) diff --git a/src/python_client/docs/DashboardMockResponse.md b/src/python_client/docs/DashboardMockResponse.md new file mode 100644 index 00000000..9e9e3267 --- /dev/null +++ b/src/python_client/docs/DashboardMockResponse.md @@ -0,0 +1,30 @@ +# DashboardMockResponse + + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**meta** | [**Response200**](Response200.md) | | [optional] +**data** | [**List[MockObject]**](MockObject.md) | | [optional] +**pagination** | [**DashboardMockResponsePagination**](DashboardMockResponsePagination.md) | | [optional] + +## Example + +```python +from emass_client.models.dashboard_mock_response import DashboardMockResponse + +# TODO update the JSON string below +json = "{}" +# create an instance of DashboardMockResponse from a JSON string +dashboard_mock_response_instance = DashboardMockResponse.from_json(json) +# print the JSON string representation of the object +print DashboardMockResponse.to_json() + +# convert the object into a dict +dashboard_mock_response_dict = dashboard_mock_response_instance.to_dict() +# create an instance of DashboardMockResponse from a dict +dashboard_mock_response_form_dict = dashboard_mock_response.from_dict(dashboard_mock_response_dict) +``` +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/src/python_client/docs/DashboardMockResponsePagination.md b/src/python_client/docs/DashboardMockResponsePagination.md new file mode 100644 index 00000000..fd51b0b9 --- /dev/null +++ b/src/python_client/docs/DashboardMockResponsePagination.md @@ -0,0 +1,33 @@ +# DashboardMockResponsePagination + + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**total_count** | **int** | | [optional] +**total_pages** | **int** | | [optional] +**page_index** | **int** | | [optional] +**page_size** | **int** | | [optional] +**prev_page_url** | **str** | | [optional] +**next_page_url** | **str** | | [optional] + +## Example + +```python +from emass_client.models.dashboard_mock_response_pagination import DashboardMockResponsePagination + +# TODO update the JSON string below +json = "{}" +# create an instance of DashboardMockResponsePagination from a JSON string +dashboard_mock_response_pagination_instance = DashboardMockResponsePagination.from_json(json) +# print the JSON string representation of the object +print DashboardMockResponsePagination.to_json() + +# convert the object into a dict +dashboard_mock_response_pagination_dict = dashboard_mock_response_pagination_instance.to_dict() +# create an instance of DashboardMockResponsePagination from a dict +dashboard_mock_response_pagination_form_dict = dashboard_mock_response_pagination.from_dict(dashboard_mock_response_pagination_dict) +``` +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/src/python_client/docs/DashboardsApi.md b/src/python_client/docs/DashboardsApi.md index b59a2e82..ae43f0c9 100644 --- a/src/python_client/docs/DashboardsApi.md +++ b/src/python_client/docs/DashboardsApi.md @@ -4,38 +4,41 @@ All URIs are relative to *http://localhost:4010* Method | HTTP request | Description ------------- | ------------- | ------------- -[**get_system_artifacts_details**](DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | Get dashboard information -[**get_system_artifacts_summary**](DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | Get dashboard information -[**get_system_assessment_procedures_details**](DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information -[**get_system_associations_details**](DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information -[**get_system_control_compliance_summary**](DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information -[**get_system_hardware_details**](DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information -[**get_system_hardware_summary**](DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information -[**get_system_poam_details**](DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information -[**get_system_poam_summary**](DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information -[**get_system_ports_protocols_details**](DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | Get dashboard information -[**get_system_ports_protocols_summary**](DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | Get dashboard information -[**get_system_privacy_summary**](DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information -[**get_system_security_control_details**](DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information -[**get_system_sensor_hardware_details**](DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | Get dashboard information -[**get_system_sensor_hardware_summary**](DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | Get dashboard information -[**get_system_status_details**](DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information -[**get_user_system_assignments_details**](DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information -[**get_va_omb_fsma_saop_summary**](DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information -[**get_va_system_a2_summary**](DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information -[**get_va_system_aa_summary**](DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information -[**get_va_system_fisma_invetory_crypto_summary**](DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | Get dashboard information -[**get_va_system_fisma_invetory_summary**](DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information -[**get_va_system_pl109_reporting_summary**](DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information -[**get_va_system_threat_architecture_details**](DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | Get dashboard information -[**get_va_system_threat_risk_summary**](DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | Get dashboard information -[**get_va_system_threat_source_details**](DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | Get dashboard information +[**get_system_artifacts_details**](DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | System Artifacts Details +[**get_system_artifacts_summary**](DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | System Artifacts Summary +[**get_system_assessment_procedures_details**](DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | System Assessment Procedures Details +[**get_system_associations_details**](DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | System Associations Details +[**get_system_common_integration_status_summary**](DashboardsApi.md#get_system_common_integration_status_summary) | **GET** /api/dashboards/system-conmon-integration-status-summary | System CONMON Integration Status +[**get_system_control_compliance_summary**](DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | System Control Compliance Summary +[**get_system_hardware_details**](DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | System Hardware Details +[**get_system_hardware_summary**](DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | System Hardware Summary +[**get_system_poam_details**](DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | System POA&M Details +[**get_system_poam_summary**](DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | System POA&M Summary +[**get_system_ports_protocols_details**](DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | System Ports/Protocols Details +[**get_system_ports_protocols_summary**](DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | System Ports/Protocols Summary +[**get_system_privacy_summary**](DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | System Privacy Summary +[**get_system_security_control_details**](DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | System Control Compliance Details +[**get_system_sensor_hardware_details**](DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | System Sensor Hardware Details +[**get_system_sensor_hardware_summary**](DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | System Sensor Hardware Summary +[**get_system_software_details**](DashboardsApi.md#get_system_software_details) | **GET** /api/dashboards/system-software-details | System Software Details +[**get_system_software_summary**](DashboardsApi.md#get_system_software_summary) | **GET** /api/dashboards/system-software-summary | System Software Summary +[**get_system_status_details**](DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | System Status Details +[**get_user_system_assignments_details**](DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | User System Assignments Details +[**get_va_omb_fsma_saop_summary**](DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | VA OMB FISMA SAOP Summary +[**get_va_system_a2_summary**](DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | VA System A2.0 Summary +[**get_va_system_aa_summary**](DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | VA System A&A Summary +[**get_va_system_fisma_invetory_crypto_summary**](DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | VA System FISMA Inventory Crypto Summary +[**get_va_system_fisma_invetory_summary**](DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | VA System FISMA Inventory Summary +[**get_va_system_pl109_reporting_summary**](DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | VA System P.L. 109 Reporting Summary +[**get_va_system_threat_architecture_details**](DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | VA System Threat Architecture Details +[**get_va_system_threat_risk_summary**](DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | VA System Threat Risks Summary +[**get_va_system_threat_source_details**](DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | VA System Threat Sources Details # **get_system_artifacts_details** > object get_system_artifacts_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Artifacts Details Get system Artifacts details information. @@ -90,7 +93,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Artifacts Details api_response = api_instance.get_system_artifacts_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_artifacts_details:\n") pprint(api_response) @@ -138,7 +141,7 @@ Name | Type | Description | Notes # **get_system_artifacts_summary** > object get_system_artifacts_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Artifacts Summary Get system Artifacts summary information. @@ -193,7 +196,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Artifacts Summary api_response = api_instance.get_system_artifacts_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_artifacts_summary:\n") pprint(api_response) @@ -241,7 +244,7 @@ Name | Type | Description | Notes # **get_system_assessment_procedures_details** > object get_system_assessment_procedures_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Assessment Procedures Details Get systems assessement procdures details dashboard information. @@ -296,7 +299,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Assessment Procedures Details api_response = api_instance.get_system_assessment_procedures_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_assessment_procedures_details:\n") pprint(api_response) @@ -344,7 +347,7 @@ Name | Type | Description | Notes # **get_system_associations_details** > object get_system_associations_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Associations Details Get system associations details dashboard information. @@ -399,7 +402,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Associations Details api_response = api_instance.get_system_associations_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_associations_details:\n") pprint(api_response) @@ -408,6 +411,109 @@ with emass_client.ApiClient(configuration) as api_client: ``` +### Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **org_id** | **int**| **Organization Id**: The unique organization identifier. | + **excludeinherited** | **bool**| **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional] [default to False] + **page_index** | **int**| **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional] [default to 0] + **page_size** | **int**| **Page Size**: If no value is specified, the default returns 20000 per page. | [optional] [default to 20000] + +### Return type + +**object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json + +### HTTP response details +| Status code | Description | Response headers | +|-------------|-------------|------------------| +**200** | Successful response | - | +**400** | Bad Request | - | +**401** | Unauthorized | - | +**403** | Forbidden | - | +**404** | Not Found | - | +**405** | Method Not Allowed | - | +**490** | API Rule Failed | - | +**500** | Internal Server Error | - | + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **get_system_common_integration_status_summary** +> object get_system_common_integration_status_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + +System CONMON Integration Status + +Get system CONMON integration status dashboard information. + +### Example + +* Api Key Authentication (apiKey): +* Api Key Authentication (mockType): +* Api Key Authentication (userId): +```python +import time +import os +import emass_client +from emass_client.rest import ApiException +from pprint import pprint + +# Defining the host is optional and defaults to http://localhost:4010 +# See configuration.py for a list of all supported configuration parameters. +configuration = emass_client.Configuration( + host = "http://localhost:4010" +) + +# The client must configure the authentication and authorization parameters +# in accordance with the API server security policy. +# Examples for each auth method are provided below, use the example that +# satisfies your auth use case. + +# Configure API key authorization: apiKey +configuration.api_key['apiKey'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['apiKey'] = 'Bearer' + +# Configure API key authorization: mockType +configuration.api_key['mockType'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['mockType'] = 'Bearer' + +# Configure API key authorization: userId +configuration.api_key['userId'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['userId'] = 'Bearer' + +# Enter a context with an instance of the API client +with emass_client.ApiClient(configuration) as api_client: + # Create an instance of the API class + api_instance = emass_client.DashboardsApi(api_client) + org_id = 1 # int | **Organization Id**: The unique organization identifier. + excludeinherited = False # bool | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (optional) (default to False) + page_index = 0 # int | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (optional) (default to 0) + page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) + + try: + # System CONMON Integration Status + api_response = api_instance.get_system_common_integration_status_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + print("The response of DashboardsApi->get_system_common_integration_status_summary:\n") + pprint(api_response) + except Exception as e: + print("Exception when calling DashboardsApi->get_system_common_integration_status_summary: %s\n" % e) +``` + + ### Parameters Name | Type | Description | Notes @@ -447,7 +553,7 @@ Name | Type | Description | Notes # **get_system_control_compliance_summary** > object get_system_control_compliance_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Control Compliance Summary Get systems control compliance summary dashboard information. @@ -502,7 +608,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Control Compliance Summary api_response = api_instance.get_system_control_compliance_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_control_compliance_summary:\n") pprint(api_response) @@ -550,7 +656,7 @@ Name | Type | Description | Notes # **get_system_hardware_details** > object get_system_hardware_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Hardware Details Get system hardware details dashboard information. @@ -605,7 +711,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Hardware Details api_response = api_instance.get_system_hardware_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_hardware_details:\n") pprint(api_response) @@ -653,7 +759,7 @@ Name | Type | Description | Notes # **get_system_hardware_summary** > object get_system_hardware_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Hardware Summary Get system hardware summary dashboard information. @@ -708,7 +814,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Hardware Summary api_response = api_instance.get_system_hardware_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_hardware_summary:\n") pprint(api_response) @@ -756,7 +862,7 @@ Name | Type | Description | Notes # **get_system_poam_details** > object get_system_poam_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System POA&M Details Get system POA&Ms details dashboard information. @@ -811,7 +917,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System POA&M Details api_response = api_instance.get_system_poam_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_poam_details:\n") pprint(api_response) @@ -859,7 +965,7 @@ Name | Type | Description | Notes # **get_system_poam_summary** > object get_system_poam_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System POA&M Summary Get systems POA&Ms summary dashboard information. @@ -914,7 +1020,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System POA&M Summary api_response = api_instance.get_system_poam_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_poam_summary:\n") pprint(api_response) @@ -962,7 +1068,7 @@ Name | Type | Description | Notes # **get_system_ports_protocols_details** > object get_system_ports_protocols_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Ports/Protocols Details Get system ports and protocols details dashboard information. @@ -1017,7 +1123,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Ports/Protocols Details api_response = api_instance.get_system_ports_protocols_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_ports_protocols_details:\n") pprint(api_response) @@ -1065,7 +1171,7 @@ Name | Type | Description | Notes # **get_system_ports_protocols_summary** > object get_system_ports_protocols_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Ports/Protocols Summary Get system ports and protocols summary dashboard information. @@ -1120,7 +1226,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Ports/Protocols Summary api_response = api_instance.get_system_ports_protocols_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_ports_protocols_summary:\n") pprint(api_response) @@ -1168,7 +1274,7 @@ Name | Type | Description | Notes # **get_system_privacy_summary** > object get_system_privacy_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Privacy Summary Get user system privacy summary dashboard information. @@ -1223,7 +1329,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Privacy Summary api_response = api_instance.get_system_privacy_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_privacy_summary:\n") pprint(api_response) @@ -1271,7 +1377,7 @@ Name | Type | Description | Notes # **get_system_security_control_details** > object get_system_security_control_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Control Compliance Details Get systems security control details dashboard information. @@ -1326,7 +1432,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Control Compliance Details api_response = api_instance.get_system_security_control_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_security_control_details:\n") pprint(api_response) @@ -1374,7 +1480,7 @@ Name | Type | Description | Notes # **get_system_sensor_hardware_details** > object get_system_sensor_hardware_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Sensor Hardware Details Get system sensor hardware details dashboard information. @@ -1429,7 +1535,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Sensor Hardware Details api_response = api_instance.get_system_sensor_hardware_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_sensor_hardware_details:\n") pprint(api_response) @@ -1477,7 +1583,7 @@ Name | Type | Description | Notes # **get_system_sensor_hardware_summary** > object get_system_sensor_hardware_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Sensor Hardware Summary Get system sensor hardware summary dashboard information. @@ -1532,7 +1638,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Sensor Hardware Summary api_response = api_instance.get_system_sensor_hardware_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_sensor_hardware_summary:\n") pprint(api_response) @@ -1541,6 +1647,212 @@ with emass_client.ApiClient(configuration) as api_client: ``` +### Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **org_id** | **int**| **Organization Id**: The unique organization identifier. | + **excludeinherited** | **bool**| **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional] [default to False] + **page_index** | **int**| **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional] [default to 0] + **page_size** | **int**| **Page Size**: If no value is specified, the default returns 20000 per page. | [optional] [default to 20000] + +### Return type + +**object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json + +### HTTP response details +| Status code | Description | Response headers | +|-------------|-------------|------------------| +**200** | Successful response | - | +**400** | Bad Request | - | +**401** | Unauthorized | - | +**403** | Forbidden | - | +**404** | Not Found | - | +**405** | Method Not Allowed | - | +**490** | API Rule Failed | - | +**500** | Internal Server Error | - | + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **get_system_software_details** +> object get_system_software_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + +System Software Details + +Get system software details dashboard information. + +### Example + +* Api Key Authentication (apiKey): +* Api Key Authentication (mockType): +* Api Key Authentication (userId): +```python +import time +import os +import emass_client +from emass_client.rest import ApiException +from pprint import pprint + +# Defining the host is optional and defaults to http://localhost:4010 +# See configuration.py for a list of all supported configuration parameters. +configuration = emass_client.Configuration( + host = "http://localhost:4010" +) + +# The client must configure the authentication and authorization parameters +# in accordance with the API server security policy. +# Examples for each auth method are provided below, use the example that +# satisfies your auth use case. + +# Configure API key authorization: apiKey +configuration.api_key['apiKey'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['apiKey'] = 'Bearer' + +# Configure API key authorization: mockType +configuration.api_key['mockType'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['mockType'] = 'Bearer' + +# Configure API key authorization: userId +configuration.api_key['userId'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['userId'] = 'Bearer' + +# Enter a context with an instance of the API client +with emass_client.ApiClient(configuration) as api_client: + # Create an instance of the API class + api_instance = emass_client.DashboardsApi(api_client) + org_id = 1 # int | **Organization Id**: The unique organization identifier. + excludeinherited = False # bool | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (optional) (default to False) + page_index = 0 # int | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (optional) (default to 0) + page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) + + try: + # System Software Details + api_response = api_instance.get_system_software_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + print("The response of DashboardsApi->get_system_software_details:\n") + pprint(api_response) + except Exception as e: + print("Exception when calling DashboardsApi->get_system_software_details: %s\n" % e) +``` + + +### Parameters + +Name | Type | Description | Notes +------------- | ------------- | ------------- | ------------- + **org_id** | **int**| **Organization Id**: The unique organization identifier. | + **excludeinherited** | **bool**| **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional] [default to False] + **page_index** | **int**| **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional] [default to 0] + **page_size** | **int**| **Page Size**: If no value is specified, the default returns 20000 per page. | [optional] [default to 20000] + +### Return type + +**object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + + - **Content-Type**: Not defined + - **Accept**: application/json + +### HTTP response details +| Status code | Description | Response headers | +|-------------|-------------|------------------| +**200** | Successful response | - | +**400** | Bad Request | - | +**401** | Unauthorized | - | +**403** | Forbidden | - | +**404** | Not Found | - | +**405** | Method Not Allowed | - | +**490** | API Rule Failed | - | +**500** | Internal Server Error | - | + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + +# **get_system_software_summary** +> object get_system_software_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + +System Software Summary + +Get system software summary dashboard information. + +### Example + +* Api Key Authentication (apiKey): +* Api Key Authentication (mockType): +* Api Key Authentication (userId): +```python +import time +import os +import emass_client +from emass_client.rest import ApiException +from pprint import pprint + +# Defining the host is optional and defaults to http://localhost:4010 +# See configuration.py for a list of all supported configuration parameters. +configuration = emass_client.Configuration( + host = "http://localhost:4010" +) + +# The client must configure the authentication and authorization parameters +# in accordance with the API server security policy. +# Examples for each auth method are provided below, use the example that +# satisfies your auth use case. + +# Configure API key authorization: apiKey +configuration.api_key['apiKey'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['apiKey'] = 'Bearer' + +# Configure API key authorization: mockType +configuration.api_key['mockType'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['mockType'] = 'Bearer' + +# Configure API key authorization: userId +configuration.api_key['userId'] = os.environ["API_KEY"] + +# Uncomment below to setup prefix (e.g. Bearer) for API key, if needed +# configuration.api_key_prefix['userId'] = 'Bearer' + +# Enter a context with an instance of the API client +with emass_client.ApiClient(configuration) as api_client: + # Create an instance of the API class + api_instance = emass_client.DashboardsApi(api_client) + org_id = 1 # int | **Organization Id**: The unique organization identifier. + excludeinherited = False # bool | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (optional) (default to False) + page_index = 0 # int | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (optional) (default to 0) + page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) + + try: + # System Software Summary + api_response = api_instance.get_system_software_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) + print("The response of DashboardsApi->get_system_software_summary:\n") + pprint(api_response) + except Exception as e: + print("Exception when calling DashboardsApi->get_system_software_summary: %s\n" % e) +``` + + ### Parameters Name | Type | Description | Notes @@ -1580,7 +1892,7 @@ Name | Type | Description | Notes # **get_system_status_details** > object get_system_status_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +System Status Details Get systems status detail dashboard information. @@ -1635,7 +1947,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # System Status Details api_response = api_instance.get_system_status_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_system_status_details:\n") pprint(api_response) @@ -1683,7 +1995,7 @@ Name | Type | Description | Notes # **get_user_system_assignments_details** > object get_user_system_assignments_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +User System Assignments Details Get user system assignments details dashboard information. @@ -1738,7 +2050,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # User System Assignments Details api_response = api_instance.get_user_system_assignments_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_user_system_assignments_details:\n") pprint(api_response) @@ -1786,7 +2098,7 @@ Name | Type | Description | Notes # **get_va_omb_fsma_saop_summary** > object get_va_omb_fsma_saop_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA OMB FISMA SAOP Summary Get VA OMB-FISMA SAOP summary dashboard information. @@ -1841,7 +2153,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA OMB FISMA SAOP Summary api_response = api_instance.get_va_omb_fsma_saop_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_omb_fsma_saop_summary:\n") pprint(api_response) @@ -1889,7 +2201,7 @@ Name | Type | Description | Notes # **get_va_system_a2_summary** > object get_va_system_a2_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System A2.0 Summary Get VA system A2.0 summary dashboard information. @@ -1944,7 +2256,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System A2.0 Summary api_response = api_instance.get_va_system_a2_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_a2_summary:\n") pprint(api_response) @@ -1992,7 +2304,7 @@ Name | Type | Description | Notes # **get_va_system_aa_summary** > object get_va_system_aa_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System A&A Summary Get VA system A&A summary dashboard information. @@ -2047,7 +2359,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System A&A Summary api_response = api_instance.get_va_system_aa_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_aa_summary:\n") pprint(api_response) @@ -2095,7 +2407,7 @@ Name | Type | Description | Notes # **get_va_system_fisma_invetory_crypto_summary** > object get_va_system_fisma_invetory_crypto_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System FISMA Inventory Crypto Summary Get VA system FISMA inventory crypto summary dashboard information. @@ -2150,7 +2462,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System FISMA Inventory Crypto Summary api_response = api_instance.get_va_system_fisma_invetory_crypto_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_fisma_invetory_crypto_summary:\n") pprint(api_response) @@ -2198,7 +2510,7 @@ Name | Type | Description | Notes # **get_va_system_fisma_invetory_summary** > object get_va_system_fisma_invetory_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System FISMA Inventory Summary Get VA system FISMA inventory summary dashboard information. @@ -2253,7 +2565,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System FISMA Inventory Summary api_response = api_instance.get_va_system_fisma_invetory_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_fisma_invetory_summary:\n") pprint(api_response) @@ -2301,7 +2613,7 @@ Name | Type | Description | Notes # **get_va_system_pl109_reporting_summary** > object get_va_system_pl109_reporting_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System P.L. 109 Reporting Summary Get VA system P.L. 109 reporting summary dashboard information. @@ -2356,7 +2668,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System P.L. 109 Reporting Summary api_response = api_instance.get_va_system_pl109_reporting_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_pl109_reporting_summary:\n") pprint(api_response) @@ -2404,7 +2716,7 @@ Name | Type | Description | Notes # **get_va_system_threat_architecture_details** > object get_va_system_threat_architecture_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System Threat Architecture Details Get VA system threat architecture details dashboard information. @@ -2459,7 +2771,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System Threat Architecture Details api_response = api_instance.get_va_system_threat_architecture_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_threat_architecture_details:\n") pprint(api_response) @@ -2507,7 +2819,7 @@ Name | Type | Description | Notes # **get_va_system_threat_risk_summary** > object get_va_system_threat_risk_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System Threat Risks Summary Get VA system threat risk summary dashboard information. @@ -2562,7 +2874,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System Threat Risks Summary api_response = api_instance.get_va_system_threat_risk_summary(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_threat_risk_summary:\n") pprint(api_response) @@ -2610,7 +2922,7 @@ Name | Type | Description | Notes # **get_va_system_threat_source_details** > object get_va_system_threat_source_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) -Get dashboard information +VA System Threat Sources Details Get VA system threat source details dashboard information. @@ -2665,7 +2977,7 @@ with emass_client.ApiClient(configuration) as api_client: page_size = 20000 # int | **Page Size**: If no value is specified, the default returns 20000 per page. (optional) (default to 20000) try: - # Get dashboard information + # VA System Threat Sources Details api_response = api_instance.get_va_system_threat_source_details(org_id, excludeinherited=excludeinherited, page_index=page_index, page_size=page_size) print("The response of DashboardsApi->get_va_system_threat_source_details:\n") pprint(api_response) diff --git a/src/python_client/docs/MockObject.md b/src/python_client/docs/MockObject.md new file mode 100644 index 00000000..0d3afddb --- /dev/null +++ b/src/python_client/docs/MockObject.md @@ -0,0 +1,40 @@ +# MockObject + + +## Properties +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**poc_organization** | **str** | [Required] Organization/Office represented. 100 Characters. | [optional] +**resources** | **str** | [Required] List of resources used. 250 Characters. | [optional] +**owning_organization** | **str** | [Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy. | [optional] +**secondary_organization** | **str** | [Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level. | [optional] +**poc_first_name** | **str** | [Conditional] First name of POC. 100 Characters. | [optional] +**poc_last_name** | **str** | [Conditional] Last name of POC. 100 Characters. | [optional] +**poc_email** | **str** | [Conditional] Email address of POC. 100 Characters. | [optional] +**poc_phone_number** | **str** | [Conditional] Phone number of POC (area code) ***-**** format. 100 Characters. | [optional] +**severity** | **str** | [Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High) | [optional] +**scheduled_completion_date** | **int** | [Conditional] Required for ongoing and completed POA&M items. Unix time format. | [optional] +**completion_date** | **int** | [Conditional] Field is required for completed POA&M items. Unix time format. | [optional] +**comments** | **str** | [Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters | [optional] +**is_active** | **bool** | [Conditional] Optionally used in PUT to delete milestones when updating a POA&M. | [optional] + +## Example + +```python +from emass_client.models.mock_object import MockObject + +# TODO update the JSON string below +json = "{}" +# create an instance of MockObject from a JSON string +mock_object_instance = MockObject.from_json(json) +# print the JSON string representation of the object +print MockObject.to_json() + +# convert the object into a dict +mock_object_dict = mock_object_instance.to_dict() +# create an instance of MockObject from a dict +mock_object_form_dict = mock_object.from_dict(mock_object_dict) +``` +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/src/python_client/docs/Systems.md b/src/python_client/docs/Systems.md index f4a69251..8da0e856 100644 --- a/src/python_client/docs/Systems.md +++ b/src/python_client/docs/Systems.md @@ -98,6 +98,8 @@ Name | Type | Description | Notes **atc_termination_date** | **int** | [Read-Only] The Connectivity Authorization Termination Date. | [optional] **system_development_life_cycle** | **str** | [Read-Only] Indicate the date by which the System needs to be deployed to a production environment. VA only. | [optional] **is_fisma_reportable** | **bool** | [Read-Only] Is this IS reportable per Federal Information Security Management Act (FISMA) established requirements? VA only | [optional] +**group_tagging** | **str** | [Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only. | [optional] +**group_tag_descriptions** | **str** | [Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only. | [optional] **package** | [**List[PacGet]**](PacGet.md) | | [optional] **connectivity_ccsd** | [**List[ConnectivityCcsd]**](ConnectivityCcsd.md) | | [optional] diff --git a/src/python_client/docs/WorkflowInstanceResponseGet.md b/src/python_client/docs/WorkflowInstanceResponseGet.md index 969db072..5c967f76 100644 --- a/src/python_client/docs/WorkflowInstanceResponseGet.md +++ b/src/python_client/docs/WorkflowInstanceResponseGet.md @@ -5,7 +5,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **meta** | [**Response200**](Response200.md) | | [optional] -**data** | [**List[WorkflowInstanceGet]**](WorkflowInstanceGet.md) | | [optional] +**data** | [**WorkflowInstanceGet**](WorkflowInstanceGet.md) | | [optional] ## Example diff --git a/src/python_client/emass_client/__init__.py b/src/python_client/emass_client/__init__.py index 10d8b4c9..6071458a 100644 --- a/src/python_client/emass_client/__init__.py +++ b/src/python_client/emass_client/__init__.py @@ -2,7 +2,7 @@ # flake8: noqa -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -10,9 +10,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -51,7 +51,7 @@ Execute `pytest` to run the tests. -__version__ = "3.9.1" +__version__ = "3.10.0" # import apis into sdk package from emass_client.api.artifacts_api import ArtifactsApi @@ -108,6 +108,8 @@ from emass_client.models.controls_put import ControlsPut from emass_client.models.controls_response_get import ControlsResponseGet from emass_client.models.controls_response_put import ControlsResponsePut +from emass_client.models.dashboard_mock_response import DashboardMockResponse +from emass_client.models.dashboard_mock_response_pagination import DashboardMockResponsePagination from emass_client.models.definition_transitions import DefinitionTransitions from emass_client.models.instances_transitions import InstancesTransitions from emass_client.models.milestone_response_get import MilestoneResponseGet @@ -119,6 +121,7 @@ from emass_client.models.milestones_request_delete_body_inner import MilestonesRequestDeleteBodyInner from emass_client.models.milestones_required_post import MilestonesRequiredPost from emass_client.models.milestones_required_put import MilestonesRequiredPut +from emass_client.models.mock_object import MockObject from emass_client.models.pac_get import PacGet from emass_client.models.pac_post import PacPost from emass_client.models.pac_response_get import PacResponseGet diff --git a/src/python_client/emass_client/api/artifacts_api.py b/src/python_client/emass_client/api/artifacts_api.py index ec7dcb01..9a78d91c 100644 --- a/src/python_client/emass_client/api/artifacts_api.py +++ b/src/python_client/emass_client/api/artifacts_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/artifacts_export_api.py b/src/python_client/emass_client/api/artifacts_export_api.py index 3bc68523..1aef9b7c 100644 --- a/src/python_client/emass_client/api/artifacts_export_api.py +++ b/src/python_client/emass_client/api/artifacts_export_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/cac_api.py b/src/python_client/emass_client/api/cac_api.py index 2e3c071a..e6beb14e 100644 --- a/src/python_client/emass_client/api/cac_api.py +++ b/src/python_client/emass_client/api/cac_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/cloud_resource_results_api.py b/src/python_client/emass_client/api/cloud_resource_results_api.py index 61cd5b73..31b87dc7 100644 --- a/src/python_client/emass_client/api/cloud_resource_results_api.py +++ b/src/python_client/emass_client/api/cloud_resource_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/cmmc_assessments_api.py b/src/python_client/emass_client/api/cmmc_assessments_api.py index 1dec20f0..6b96d438 100644 --- a/src/python_client/emass_client/api/cmmc_assessments_api.py +++ b/src/python_client/emass_client/api/cmmc_assessments_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/container_scan_results_api.py b/src/python_client/emass_client/api/container_scan_results_api.py index 69a9ad90..94281390 100644 --- a/src/python_client/emass_client/api/container_scan_results_api.py +++ b/src/python_client/emass_client/api/container_scan_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/controls_api.py b/src/python_client/emass_client/api/controls_api.py index bf0117ea..c561b210 100644 --- a/src/python_client/emass_client/api/controls_api.py +++ b/src/python_client/emass_client/api/controls_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/dashboards_api.py b/src/python_client/emass_client/api/dashboards_api.py index 15d4e1c4..472031ee 100644 --- a/src/python_client/emass_client/api/dashboards_api.py +++ b/src/python_client/emass_client/api/dashboards_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -83,7 +83,7 @@ def __init__(self, api_client=None): @validate_arguments def get_system_artifacts_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Artifacts Details # noqa: E501 Get system Artifacts details information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -118,7 +118,7 @@ def get_system_artifacts_details(self, org_id : Annotated[StrictInt, Field(..., @validate_arguments def get_system_artifacts_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Artifacts Details # noqa: E501 Get system Artifacts details information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -253,7 +253,7 @@ def get_system_artifacts_details_with_http_info(self, org_id : Annotated[StrictI @validate_arguments def get_system_artifacts_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Artifacts Summary # noqa: E501 Get system Artifacts summary information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -288,7 +288,7 @@ def get_system_artifacts_summary(self, org_id : Annotated[StrictInt, Field(..., @validate_arguments def get_system_artifacts_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Artifacts Summary # noqa: E501 Get system Artifacts summary information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -423,7 +423,7 @@ def get_system_artifacts_summary_with_http_info(self, org_id : Annotated[StrictI @validate_arguments def get_system_assessment_procedures_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Assessment Procedures Details # noqa: E501 Get systems assessement procdures details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -458,7 +458,7 @@ def get_system_assessment_procedures_details(self, org_id : Annotated[StrictInt, @validate_arguments def get_system_assessment_procedures_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Assessment Procedures Details # noqa: E501 Get systems assessement procdures details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -593,7 +593,7 @@ def get_system_assessment_procedures_details_with_http_info(self, org_id : Annot @validate_arguments def get_system_associations_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Associations Details # noqa: E501 Get system associations details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -628,7 +628,7 @@ def get_system_associations_details(self, org_id : Annotated[StrictInt, Field(.. @validate_arguments def get_system_associations_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Associations Details # noqa: E501 Get system associations details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -761,9 +761,179 @@ def get_system_associations_details_with_http_info(self, org_id : Annotated[Stri collection_formats=_collection_formats, _request_auth=_params.get('_request_auth')) + @validate_arguments + def get_system_common_integration_status_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + """System CONMON Integration Status # noqa: E501 + + Get system CONMON integration status dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_common_integration_status_summary(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: object + """ + kwargs['_return_http_data_only'] = True + if '_preload_content' in kwargs: + raise ValueError("Error! Please call the get_system_common_integration_status_summary_with_http_info method with `_preload_content` instead and obtain raw data from ApiResponse.raw_data") + return self.get_system_common_integration_status_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 + + @validate_arguments + def get_system_common_integration_status_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + """System CONMON Integration Status # noqa: E501 + + Get system CONMON integration status dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_common_integration_status_summary_with_http_info(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _preload_content: if False, the ApiResponse.data will + be set to none and raw_data will store the + HTTP response body without reading/decoding. + Default is True. + :type _preload_content: bool, optional + :param _return_http_data_only: response data instead of ApiResponse + object with status code, headers, etc + :type _return_http_data_only: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :param _request_auth: set to override the auth_settings for an a single + request; this effectively ignores the authentication + in the spec for a single request. + :type _request_auth: dict, optional + :type _content_type: string, optional: force content-type for the request + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: tuple(object, status_code(int), headers(HTTPHeaderDict)) + """ + + _params = locals() + + _all_params = [ + 'org_id', + 'excludeinherited', + 'page_index', + 'page_size' + ] + _all_params.extend( + [ + 'async_req', + '_return_http_data_only', + '_preload_content', + '_request_timeout', + '_request_auth', + '_content_type', + '_headers' + ] + ) + + # validate the arguments + for _key, _val in _params['kwargs'].items(): + if _key not in _all_params: + raise ApiTypeError( + "Got an unexpected keyword argument '%s'" + " to method get_system_common_integration_status_summary" % _key + ) + _params[_key] = _val + del _params['kwargs'] + + _collection_formats = {} + + # process the path parameters + _path_params = {} + + # process the query parameters + _query_params = [] + if _params.get('org_id') is not None: # noqa: E501 + _query_params.append(('orgId', _params['org_id'])) + + if _params.get('excludeinherited') is not None: # noqa: E501 + _query_params.append(('excludeinherited', _params['excludeinherited'])) + + if _params.get('page_index') is not None: # noqa: E501 + _query_params.append(('pageIndex', _params['page_index'])) + + if _params.get('page_size') is not None: # noqa: E501 + _query_params.append(('pageSize', _params['page_size'])) + + # process the header parameters + _header_params = dict(_params.get('_headers', {})) + # process the form parameters + _form_params = [] + _files = {} + # process the body parameter + _body_params = None + # set the HTTP header `Accept` + _header_params['Accept'] = self.api_client.select_header_accept( + ['application/json']) # noqa: E501 + + # authentication setting + _auth_settings = ['apiKey', 'mockType', 'userId'] # noqa: E501 + + _response_types_map = { + '200': "object", + '400': "Response400", + '401': "Response401", + '403': "Response403", + '404': "Response404", + '405': "Response405", + '490': "Response490", + '500': "Response500", + } + + return self.api_client.call_api( + '/api/dashboards/system-conmon-integration-status-summary', 'GET', + _path_params, + _query_params, + _header_params, + body=_body_params, + post_params=_form_params, + files=_files, + response_types_map=_response_types_map, + auth_settings=_auth_settings, + async_req=_params.get('async_req'), + _return_http_data_only=_params.get('_return_http_data_only'), # noqa: E501 + _preload_content=_params.get('_preload_content', True), + _request_timeout=_params.get('_request_timeout'), + collection_formats=_collection_formats, + _request_auth=_params.get('_request_auth')) + @validate_arguments def get_system_control_compliance_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Control Compliance Summary # noqa: E501 Get systems control compliance summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -798,7 +968,7 @@ def get_system_control_compliance_summary(self, org_id : Annotated[StrictInt, Fi @validate_arguments def get_system_control_compliance_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Control Compliance Summary # noqa: E501 Get systems control compliance summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -933,7 +1103,7 @@ def get_system_control_compliance_summary_with_http_info(self, org_id : Annotate @validate_arguments def get_system_hardware_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Hardware Details # noqa: E501 Get system hardware details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -968,7 +1138,7 @@ def get_system_hardware_details(self, org_id : Annotated[StrictInt, Field(..., d @validate_arguments def get_system_hardware_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Hardware Details # noqa: E501 Get system hardware details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1103,7 +1273,7 @@ def get_system_hardware_details_with_http_info(self, org_id : Annotated[StrictIn @validate_arguments def get_system_hardware_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Hardware Summary # noqa: E501 Get system hardware summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1138,7 +1308,7 @@ def get_system_hardware_summary(self, org_id : Annotated[StrictInt, Field(..., d @validate_arguments def get_system_hardware_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Hardware Summary # noqa: E501 Get system hardware summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1273,7 +1443,7 @@ def get_system_hardware_summary_with_http_info(self, org_id : Annotated[StrictIn @validate_arguments def get_system_poam_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System POA&M Details # noqa: E501 Get system POA&Ms details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1308,7 +1478,7 @@ def get_system_poam_details(self, org_id : Annotated[StrictInt, Field(..., descr @validate_arguments def get_system_poam_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System POA&M Details # noqa: E501 Get system POA&Ms details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1443,7 +1613,7 @@ def get_system_poam_details_with_http_info(self, org_id : Annotated[StrictInt, F @validate_arguments def get_system_poam_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System POA&M Summary # noqa: E501 Get systems POA&Ms summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1478,7 +1648,7 @@ def get_system_poam_summary(self, org_id : Annotated[StrictInt, Field(..., descr @validate_arguments def get_system_poam_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System POA&M Summary # noqa: E501 Get systems POA&Ms summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1613,7 +1783,7 @@ def get_system_poam_summary_with_http_info(self, org_id : Annotated[StrictInt, F @validate_arguments def get_system_ports_protocols_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Ports/Protocols Details # noqa: E501 Get system ports and protocols details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1648,7 +1818,7 @@ def get_system_ports_protocols_details(self, org_id : Annotated[StrictInt, Field @validate_arguments def get_system_ports_protocols_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Ports/Protocols Details # noqa: E501 Get system ports and protocols details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1783,7 +1953,7 @@ def get_system_ports_protocols_details_with_http_info(self, org_id : Annotated[S @validate_arguments def get_system_ports_protocols_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Ports/Protocols Summary # noqa: E501 Get system ports and protocols summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1818,7 +1988,7 @@ def get_system_ports_protocols_summary(self, org_id : Annotated[StrictInt, Field @validate_arguments def get_system_ports_protocols_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Ports/Protocols Summary # noqa: E501 Get system ports and protocols summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1953,7 +2123,7 @@ def get_system_ports_protocols_summary_with_http_info(self, org_id : Annotated[S @validate_arguments def get_system_privacy_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Privacy Summary # noqa: E501 Get user system privacy summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -1988,7 +2158,7 @@ def get_system_privacy_summary(self, org_id : Annotated[StrictInt, Field(..., de @validate_arguments def get_system_privacy_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Privacy Summary # noqa: E501 Get user system privacy summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2123,7 +2293,7 @@ def get_system_privacy_summary_with_http_info(self, org_id : Annotated[StrictInt @validate_arguments def get_system_security_control_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Control Compliance Details # noqa: E501 Get systems security control details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2158,7 +2328,7 @@ def get_system_security_control_details(self, org_id : Annotated[StrictInt, Fiel @validate_arguments def get_system_security_control_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Control Compliance Details # noqa: E501 Get systems security control details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2293,7 +2463,7 @@ def get_system_security_control_details_with_http_info(self, org_id : Annotated[ @validate_arguments def get_system_sensor_hardware_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Sensor Hardware Details # noqa: E501 Get system sensor hardware details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2328,7 +2498,7 @@ def get_system_sensor_hardware_details(self, org_id : Annotated[StrictInt, Field @validate_arguments def get_system_sensor_hardware_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Sensor Hardware Details # noqa: E501 Get system sensor hardware details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2463,7 +2633,7 @@ def get_system_sensor_hardware_details_with_http_info(self, org_id : Annotated[S @validate_arguments def get_system_sensor_hardware_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Sensor Hardware Summary # noqa: E501 Get system sensor hardware summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2498,7 +2668,7 @@ def get_system_sensor_hardware_summary(self, org_id : Annotated[StrictInt, Field @validate_arguments def get_system_sensor_hardware_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Sensor Hardware Summary # noqa: E501 Get system sensor hardware summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2631,9 +2801,349 @@ def get_system_sensor_hardware_summary_with_http_info(self, org_id : Annotated[S collection_formats=_collection_formats, _request_auth=_params.get('_request_auth')) + @validate_arguments + def get_system_software_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + """System Software Details # noqa: E501 + + Get system software details dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_software_details(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: object + """ + kwargs['_return_http_data_only'] = True + if '_preload_content' in kwargs: + raise ValueError("Error! Please call the get_system_software_details_with_http_info method with `_preload_content` instead and obtain raw data from ApiResponse.raw_data") + return self.get_system_software_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 + + @validate_arguments + def get_system_software_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + """System Software Details # noqa: E501 + + Get system software details dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_software_details_with_http_info(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _preload_content: if False, the ApiResponse.data will + be set to none and raw_data will store the + HTTP response body without reading/decoding. + Default is True. + :type _preload_content: bool, optional + :param _return_http_data_only: response data instead of ApiResponse + object with status code, headers, etc + :type _return_http_data_only: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :param _request_auth: set to override the auth_settings for an a single + request; this effectively ignores the authentication + in the spec for a single request. + :type _request_auth: dict, optional + :type _content_type: string, optional: force content-type for the request + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: tuple(object, status_code(int), headers(HTTPHeaderDict)) + """ + + _params = locals() + + _all_params = [ + 'org_id', + 'excludeinherited', + 'page_index', + 'page_size' + ] + _all_params.extend( + [ + 'async_req', + '_return_http_data_only', + '_preload_content', + '_request_timeout', + '_request_auth', + '_content_type', + '_headers' + ] + ) + + # validate the arguments + for _key, _val in _params['kwargs'].items(): + if _key not in _all_params: + raise ApiTypeError( + "Got an unexpected keyword argument '%s'" + " to method get_system_software_details" % _key + ) + _params[_key] = _val + del _params['kwargs'] + + _collection_formats = {} + + # process the path parameters + _path_params = {} + + # process the query parameters + _query_params = [] + if _params.get('org_id') is not None: # noqa: E501 + _query_params.append(('orgId', _params['org_id'])) + + if _params.get('excludeinherited') is not None: # noqa: E501 + _query_params.append(('excludeinherited', _params['excludeinherited'])) + + if _params.get('page_index') is not None: # noqa: E501 + _query_params.append(('pageIndex', _params['page_index'])) + + if _params.get('page_size') is not None: # noqa: E501 + _query_params.append(('pageSize', _params['page_size'])) + + # process the header parameters + _header_params = dict(_params.get('_headers', {})) + # process the form parameters + _form_params = [] + _files = {} + # process the body parameter + _body_params = None + # set the HTTP header `Accept` + _header_params['Accept'] = self.api_client.select_header_accept( + ['application/json']) # noqa: E501 + + # authentication setting + _auth_settings = ['apiKey', 'mockType', 'userId'] # noqa: E501 + + _response_types_map = { + '200': "object", + '400': "Response400", + '401': "Response401", + '403': "Response403", + '404': "Response404", + '405': "Response405", + '490': "Response490", + '500': "Response500", + } + + return self.api_client.call_api( + '/api/dashboards/system-software-details', 'GET', + _path_params, + _query_params, + _header_params, + body=_body_params, + post_params=_form_params, + files=_files, + response_types_map=_response_types_map, + auth_settings=_auth_settings, + async_req=_params.get('async_req'), + _return_http_data_only=_params.get('_return_http_data_only'), # noqa: E501 + _preload_content=_params.get('_preload_content', True), + _request_timeout=_params.get('_request_timeout'), + collection_formats=_collection_formats, + _request_auth=_params.get('_request_auth')) + + @validate_arguments + def get_system_software_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + """System Software Summary # noqa: E501 + + Get system software summary dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_software_summary(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: object + """ + kwargs['_return_http_data_only'] = True + if '_preload_content' in kwargs: + raise ValueError("Error! Please call the get_system_software_summary_with_http_info method with `_preload_content` instead and obtain raw data from ApiResponse.raw_data") + return self.get_system_software_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 + + @validate_arguments + def get_system_software_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + """System Software Summary # noqa: E501 + + Get system software summary dashboard information. # noqa: E501 + This method makes a synchronous HTTP request by default. To make an + asynchronous HTTP request, please pass async_req=True + + >>> thread = api.get_system_software_summary_with_http_info(org_id, excludeinherited, page_index, page_size, async_req=True) + >>> result = thread.get() + + :param org_id: **Organization Id**: The unique organization identifier. (required) + :type org_id: int + :param excludeinherited: **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + :type excludeinherited: bool + :param page_index: **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + :type page_index: int + :param page_size: **Page Size**: If no value is specified, the default returns 20000 per page. + :type page_size: int + :param async_req: Whether to execute the request asynchronously. + :type async_req: bool, optional + :param _preload_content: if False, the ApiResponse.data will + be set to none and raw_data will store the + HTTP response body without reading/decoding. + Default is True. + :type _preload_content: bool, optional + :param _return_http_data_only: response data instead of ApiResponse + object with status code, headers, etc + :type _return_http_data_only: bool, optional + :param _request_timeout: timeout setting for this request. If one + number provided, it will be total request + timeout. It can also be a pair (tuple) of + (connection, read) timeouts. + :param _request_auth: set to override the auth_settings for an a single + request; this effectively ignores the authentication + in the spec for a single request. + :type _request_auth: dict, optional + :type _content_type: string, optional: force content-type for the request + :return: Returns the result object. + If the method is called asynchronously, + returns the request thread. + :rtype: tuple(object, status_code(int), headers(HTTPHeaderDict)) + """ + + _params = locals() + + _all_params = [ + 'org_id', + 'excludeinherited', + 'page_index', + 'page_size' + ] + _all_params.extend( + [ + 'async_req', + '_return_http_data_only', + '_preload_content', + '_request_timeout', + '_request_auth', + '_content_type', + '_headers' + ] + ) + + # validate the arguments + for _key, _val in _params['kwargs'].items(): + if _key not in _all_params: + raise ApiTypeError( + "Got an unexpected keyword argument '%s'" + " to method get_system_software_summary" % _key + ) + _params[_key] = _val + del _params['kwargs'] + + _collection_formats = {} + + # process the path parameters + _path_params = {} + + # process the query parameters + _query_params = [] + if _params.get('org_id') is not None: # noqa: E501 + _query_params.append(('orgId', _params['org_id'])) + + if _params.get('excludeinherited') is not None: # noqa: E501 + _query_params.append(('excludeinherited', _params['excludeinherited'])) + + if _params.get('page_index') is not None: # noqa: E501 + _query_params.append(('pageIndex', _params['page_index'])) + + if _params.get('page_size') is not None: # noqa: E501 + _query_params.append(('pageSize', _params['page_size'])) + + # process the header parameters + _header_params = dict(_params.get('_headers', {})) + # process the form parameters + _form_params = [] + _files = {} + # process the body parameter + _body_params = None + # set the HTTP header `Accept` + _header_params['Accept'] = self.api_client.select_header_accept( + ['application/json']) # noqa: E501 + + # authentication setting + _auth_settings = ['apiKey', 'mockType', 'userId'] # noqa: E501 + + _response_types_map = { + '200': "object", + '400': "Response400", + '401': "Response401", + '403': "Response403", + '404': "Response404", + '405': "Response405", + '490': "Response490", + '500': "Response500", + } + + return self.api_client.call_api( + '/api/dashboards/system-software-summary', 'GET', + _path_params, + _query_params, + _header_params, + body=_body_params, + post_params=_form_params, + files=_files, + response_types_map=_response_types_map, + auth_settings=_auth_settings, + async_req=_params.get('async_req'), + _return_http_data_only=_params.get('_return_http_data_only'), # noqa: E501 + _preload_content=_params.get('_preload_content', True), + _request_timeout=_params.get('_request_timeout'), + collection_formats=_collection_formats, + _request_auth=_params.get('_request_auth')) + @validate_arguments def get_system_status_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Status Details # noqa: E501 Get systems status detail dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2668,7 +3178,7 @@ def get_system_status_details(self, org_id : Annotated[StrictInt, Field(..., des @validate_arguments def get_system_status_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """System Status Details # noqa: E501 Get systems status detail dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2803,7 +3313,7 @@ def get_system_status_details_with_http_info(self, org_id : Annotated[StrictInt, @validate_arguments def get_user_system_assignments_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """User System Assignments Details # noqa: E501 Get user system assignments details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2838,7 +3348,7 @@ def get_user_system_assignments_details(self, org_id : Annotated[StrictInt, Fiel @validate_arguments def get_user_system_assignments_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """User System Assignments Details # noqa: E501 Get user system assignments details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -2973,7 +3483,7 @@ def get_user_system_assignments_details_with_http_info(self, org_id : Annotated[ @validate_arguments def get_va_omb_fsma_saop_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA OMB FISMA SAOP Summary # noqa: E501 Get VA OMB-FISMA SAOP summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3008,7 +3518,7 @@ def get_va_omb_fsma_saop_summary(self, org_id : Annotated[StrictInt, Field(..., @validate_arguments def get_va_omb_fsma_saop_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA OMB FISMA SAOP Summary # noqa: E501 Get VA OMB-FISMA SAOP summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3143,7 +3653,7 @@ def get_va_omb_fsma_saop_summary_with_http_info(self, org_id : Annotated[StrictI @validate_arguments def get_va_system_a2_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System A2.0 Summary # noqa: E501 Get VA system A2.0 summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3178,7 +3688,7 @@ def get_va_system_a2_summary(self, org_id : Annotated[StrictInt, Field(..., desc @validate_arguments def get_va_system_a2_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System A2.0 Summary # noqa: E501 Get VA system A2.0 summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3313,7 +3823,7 @@ def get_va_system_a2_summary_with_http_info(self, org_id : Annotated[StrictInt, @validate_arguments def get_va_system_aa_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System A&A Summary # noqa: E501 Get VA system A&A summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3348,7 +3858,7 @@ def get_va_system_aa_summary(self, org_id : Annotated[StrictInt, Field(..., desc @validate_arguments def get_va_system_aa_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System A&A Summary # noqa: E501 Get VA system A&A summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3483,7 +3993,7 @@ def get_va_system_aa_summary_with_http_info(self, org_id : Annotated[StrictInt, @validate_arguments def get_va_system_fisma_invetory_crypto_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System FISMA Inventory Crypto Summary # noqa: E501 Get VA system FISMA inventory crypto summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3518,7 +4028,7 @@ def get_va_system_fisma_invetory_crypto_summary(self, org_id : Annotated[StrictI @validate_arguments def get_va_system_fisma_invetory_crypto_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System FISMA Inventory Crypto Summary # noqa: E501 Get VA system FISMA inventory crypto summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3653,7 +4163,7 @@ def get_va_system_fisma_invetory_crypto_summary_with_http_info(self, org_id : An @validate_arguments def get_va_system_fisma_invetory_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System FISMA Inventory Summary # noqa: E501 Get VA system FISMA inventory summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3688,7 +4198,7 @@ def get_va_system_fisma_invetory_summary(self, org_id : Annotated[StrictInt, Fie @validate_arguments def get_va_system_fisma_invetory_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System FISMA Inventory Summary # noqa: E501 Get VA system FISMA inventory summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3823,7 +4333,7 @@ def get_va_system_fisma_invetory_summary_with_http_info(self, org_id : Annotated @validate_arguments def get_va_system_pl109_reporting_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System P.L. 109 Reporting Summary # noqa: E501 Get VA system P.L. 109 reporting summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3858,7 +4368,7 @@ def get_va_system_pl109_reporting_summary(self, org_id : Annotated[StrictInt, Fi @validate_arguments def get_va_system_pl109_reporting_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System P.L. 109 Reporting Summary # noqa: E501 Get VA system P.L. 109 reporting summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -3993,7 +4503,7 @@ def get_va_system_pl109_reporting_summary_with_http_info(self, org_id : Annotate @validate_arguments def get_va_system_threat_architecture_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Architecture Details # noqa: E501 Get VA system threat architecture details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -4028,7 +4538,7 @@ def get_va_system_threat_architecture_details(self, org_id : Annotated[StrictInt @validate_arguments def get_va_system_threat_architecture_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Architecture Details # noqa: E501 Get VA system threat architecture details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -4163,7 +4673,7 @@ def get_va_system_threat_architecture_details_with_http_info(self, org_id : Anno @validate_arguments def get_va_system_threat_risk_summary(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Risks Summary # noqa: E501 Get VA system threat risk summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -4198,7 +4708,7 @@ def get_va_system_threat_risk_summary(self, org_id : Annotated[StrictInt, Field( @validate_arguments def get_va_system_threat_risk_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Risks Summary # noqa: E501 Get VA system threat risk summary dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -4333,7 +4843,7 @@ def get_va_system_threat_risk_summary_with_http_info(self, org_id : Annotated[St @validate_arguments def get_va_system_threat_source_details(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Sources Details # noqa: E501 Get VA system threat source details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an @@ -4368,7 +4878,7 @@ def get_va_system_threat_source_details(self, org_id : Annotated[StrictInt, Fiel @validate_arguments def get_va_system_threat_source_details_with_http_info(self, org_id : Annotated[StrictInt, Field(..., description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 - """Get dashboard information # noqa: E501 + """VA System Threat Sources Details # noqa: E501 Get VA system threat source details dashboard information. # noqa: E501 This method makes a synchronous HTTP request by default. To make an diff --git a/src/python_client/emass_client/api/milestones_api.py b/src/python_client/emass_client/api/milestones_api.py index 5092b8dd..7334a5b8 100644 --- a/src/python_client/emass_client/api/milestones_api.py +++ b/src/python_client/emass_client/api/milestones_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/pac_api.py b/src/python_client/emass_client/api/pac_api.py index 44943ae0..84dd570b 100644 --- a/src/python_client/emass_client/api/pac_api.py +++ b/src/python_client/emass_client/api/pac_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/poam_api.py b/src/python_client/emass_client/api/poam_api.py index 02706551..c17add2b 100644 --- a/src/python_client/emass_client/api/poam_api.py +++ b/src/python_client/emass_client/api/poam_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/registration_api.py b/src/python_client/emass_client/api/registration_api.py index 3163f5ac..94f9f0ca 100644 --- a/src/python_client/emass_client/api/registration_api.py +++ b/src/python_client/emass_client/api/registration_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/static_code_scans_api.py b/src/python_client/emass_client/api/static_code_scans_api.py index a876cc6c..29fb251c 100644 --- a/src/python_client/emass_client/api/static_code_scans_api.py +++ b/src/python_client/emass_client/api/static_code_scans_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/system_roles_api.py b/src/python_client/emass_client/api/system_roles_api.py index 4ba38b8f..3505132d 100644 --- a/src/python_client/emass_client/api/system_roles_api.py +++ b/src/python_client/emass_client/api/system_roles_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/systems_api.py b/src/python_client/emass_client/api/systems_api.py index c0edd989..776a6f2e 100644 --- a/src/python_client/emass_client/api/systems_api.py +++ b/src/python_client/emass_client/api/systems_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/test_api.py b/src/python_client/emass_client/api/test_api.py index 9aed9ef7..4ef6fae0 100644 --- a/src/python_client/emass_client/api/test_api.py +++ b/src/python_client/emass_client/api/test_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/test_results_api.py b/src/python_client/emass_client/api/test_results_api.py index 743b4268..08524b8c 100644 --- a/src/python_client/emass_client/api/test_results_api.py +++ b/src/python_client/emass_client/api/test_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/workflow_definitions_api.py b/src/python_client/emass_client/api/workflow_definitions_api.py index 650ee283..77fa1528 100644 --- a/src/python_client/emass_client/api/workflow_definitions_api.py +++ b/src/python_client/emass_client/api/workflow_definitions_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api/workflow_instances_api.py b/src/python_client/emass_client/api/workflow_instances_api.py index 9b09d7cc..6f027dcd 100644 --- a/src/python_client/emass_client/api/workflow_instances_api.py +++ b/src/python_client/emass_client/api/workflow_instances_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/api_client.py b/src/python_client/emass_client/api_client.py index f67ee653..e6ba250b 100644 --- a/src/python_client/emass_client/api_client.py +++ b/src/python_client/emass_client/api_client.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -113,7 +113,7 @@ def __init__(self, configuration=None, header_name=None, header_value=None, self.default_headers[header_name] = header_value self.cookie = cookie # Set default User-Agent. - self.user_agent = 'OpenAPI-Generator/3.9.1/python' + self.user_agent = 'OpenAPI-Generator/3.10.0/python' self.client_side_validation = configuration.client_side_validation def __enter__(self): diff --git a/src/python_client/emass_client/configuration.py b/src/python_client/emass_client/configuration.py index 3752f454..150f09dc 100644 --- a/src/python_client/emass_client/configuration.py +++ b/src/python_client/emass_client/configuration.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -451,8 +451,8 @@ def to_debug_report(self): return "Python SDK Debug Report:\n"\ "OS: {env}\n"\ "Python Version: {pyversion}\n"\ - "Version of the API: v3.9\n"\ - "SDK Package Version: 3.9.1".\ + "Version of the API: v3.10\n"\ + "SDK Package Version: 3.10.0".\ format(env=sys.platform, pyversion=sys.version) def get_host_settings(self): diff --git a/src/python_client/emass_client/exceptions.py b/src/python_client/emass_client/exceptions.py index bdd7edad..67ad7894 100644 --- a/src/python_client/emass_client/exceptions.py +++ b/src/python_client/emass_client/exceptions.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -163,6 +163,10 @@ def __str__(self): return error_message +class BadRequestException(ApiException): + + def __init__(self, status=None, reason=None, http_resp=None): + super(BadRequestException, self).__init__(status, reason, http_resp) class NotFoundException(ApiException): diff --git a/src/python_client/emass_client/models/__init__.py b/src/python_client/emass_client/models/__init__.py index 2063812c..5a713159 100644 --- a/src/python_client/emass_client/models/__init__.py +++ b/src/python_client/emass_client/models/__init__.py @@ -1,7 +1,7 @@ # coding: utf-8 # flake8: noqa -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -9,9 +9,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -73,6 +73,8 @@ from emass_client.models.controls_put import ControlsPut from emass_client.models.controls_response_get import ControlsResponseGet from emass_client.models.controls_response_put import ControlsResponsePut +from emass_client.models.dashboard_mock_response import DashboardMockResponse +from emass_client.models.dashboard_mock_response_pagination import DashboardMockResponsePagination from emass_client.models.definition_transitions import DefinitionTransitions from emass_client.models.instances_transitions import InstancesTransitions from emass_client.models.milestone_response_get import MilestoneResponseGet @@ -84,6 +86,7 @@ from emass_client.models.milestones_request_delete_body_inner import MilestonesRequestDeleteBodyInner from emass_client.models.milestones_required_post import MilestonesRequiredPost from emass_client.models.milestones_required_put import MilestonesRequiredPut +from emass_client.models.mock_object import MockObject from emass_client.models.pac_get import PacGet from emass_client.models.pac_post import PacPost from emass_client.models.pac_response_get import PacResponseGet diff --git a/src/python_client/emass_client/models/artifacts_get.py b/src/python_client/emass_client/models/artifacts_get.py index 8b39071c..fde8e30d 100644 --- a/src/python_client/emass_client/models/artifacts_get.py +++ b/src/python_client/emass_client/models/artifacts_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py b/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py index dcd23e84..849cadf1 100644 --- a/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_del.py b/src/python_client/emass_client/models/artifacts_response_del.py index 7b06d6ac..e9f6e62d 100644 --- a/src/python_client/emass_client/models/artifacts_response_del.py +++ b/src/python_client/emass_client/models/artifacts_response_del.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_del_data_inner.py b/src/python_client/emass_client/models/artifacts_response_del_data_inner.py index ebd0f123..40b14e8f 100644 --- a/src/python_client/emass_client/models/artifacts_response_del_data_inner.py +++ b/src/python_client/emass_client/models/artifacts_response_del_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_get.py b/src/python_client/emass_client/models/artifacts_response_get.py index 377b54e8..5ddecfe8 100644 --- a/src/python_client/emass_client/models/artifacts_response_get.py +++ b/src/python_client/emass_client/models/artifacts_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_put_post.py b/src/python_client/emass_client/models/artifacts_response_put_post.py index 037254cd..03acfece 100644 --- a/src/python_client/emass_client/models/artifacts_response_put_post.py +++ b/src/python_client/emass_client/models/artifacts_response_put_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py b/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py index 0a02fb20..0892682a 100644 --- a/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py +++ b/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_get.py b/src/python_client/emass_client/models/cac_get.py index 02d006f1..7d4d559a 100644 --- a/src/python_client/emass_client/models/cac_get.py +++ b/src/python_client/emass_client/models/cac_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_get.py b/src/python_client/emass_client/models/cac_response_get.py index 264d9e44..6d0c06c3 100644 --- a/src/python_client/emass_client/models/cac_response_get.py +++ b/src/python_client/emass_client/models/cac_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_post.py b/src/python_client/emass_client/models/cac_response_post.py index e43cf491..280237a1 100644 --- a/src/python_client/emass_client/models/cac_response_post.py +++ b/src/python_client/emass_client/models/cac_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_post_data_inner.py b/src/python_client/emass_client/models/cac_response_post_data_inner.py index 3395dd80..2c245b05 100644 --- a/src/python_client/emass_client/models/cac_response_post_data_inner.py +++ b/src/python_client/emass_client/models/cac_response_post_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_post.py b/src/python_client/emass_client/models/cloud_resources_post.py index eaf879cd..38cfffd3 100644 --- a/src/python_client/emass_client/models/cloud_resources_post.py +++ b/src/python_client/emass_client/models/cloud_resources_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_response_post.py b/src/python_client/emass_client/models/cloud_resources_response_post.py index 5e331813..a988f9c7 100644 --- a/src/python_client/emass_client/models/cloud_resources_response_post.py +++ b/src/python_client/emass_client/models/cloud_resources_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cmmc_get.py b/src/python_client/emass_client/models/cmmc_get.py index 46029e96..94594e44 100644 --- a/src/python_client/emass_client/models/cmmc_get.py +++ b/src/python_client/emass_client/models/cmmc_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cmmc_response_get.py b/src/python_client/emass_client/models/cmmc_response_get.py index b67ed702..4667e4c2 100644 --- a/src/python_client/emass_client/models/cmmc_response_get.py +++ b/src/python_client/emass_client/models/cmmc_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/connectivity_ccsd.py b/src/python_client/emass_client/models/connectivity_ccsd.py index d6681239..24dfd01c 100644 --- a/src/python_client/emass_client/models/connectivity_ccsd.py +++ b/src/python_client/emass_client/models/connectivity_ccsd.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/containers_resources_post.py b/src/python_client/emass_client/models/containers_resources_post.py index 877b3b14..4cfeac6c 100644 --- a/src/python_client/emass_client/models/containers_resources_post.py +++ b/src/python_client/emass_client/models/containers_resources_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/containers_response_post.py b/src/python_client/emass_client/models/containers_response_post.py index 34c79900..62139832 100644 --- a/src/python_client/emass_client/models/containers_response_post.py +++ b/src/python_client/emass_client/models/containers_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_get.py b/src/python_client/emass_client/models/controls_get.py index c10a69c7..7ca66474 100644 --- a/src/python_client/emass_client/models/controls_get.py +++ b/src/python_client/emass_client/models/controls_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_put.py b/src/python_client/emass_client/models/controls_put.py index 58ebaabd..619b8795 100644 --- a/src/python_client/emass_client/models/controls_put.py +++ b/src/python_client/emass_client/models/controls_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_response_get.py b/src/python_client/emass_client/models/controls_response_get.py index 3e759465..40c4025d 100644 --- a/src/python_client/emass_client/models/controls_response_get.py +++ b/src/python_client/emass_client/models/controls_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_response_put.py b/src/python_client/emass_client/models/controls_response_put.py index faf637eb..a1d18c24 100644 --- a/src/python_client/emass_client/models/controls_response_put.py +++ b/src/python_client/emass_client/models/controls_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/dashboard_mock_response.py b/src/python_client/emass_client/models/dashboard_mock_response.py new file mode 100644 index 00000000..b3046e64 --- /dev/null +++ b/src/python_client/emass_client/models/dashboard_mock_response.py @@ -0,0 +1,127 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +from __future__ import annotations +import pprint +import re # noqa: F401 +import json + + +from typing import List, Optional +from pydantic import BaseModel, conlist +from emass_client.models.dashboard_mock_response_pagination import DashboardMockResponsePagination +from emass_client.models.mock_object import MockObject +from emass_client.models.response200 import Response200 + +class DashboardMockResponse(BaseModel): + """ + DashboardMockResponse + """ + meta: Optional[Response200] = None + data: Optional[conlist(MockObject)] = None + pagination: Optional[DashboardMockResponsePagination] = None + __properties = ["meta", "data", "pagination"] + + class Config: + """Pydantic configuration""" + allow_population_by_field_name = True + validate_assignment = True + + def to_str(self) -> str: + """Returns the string representation of the model using alias""" + return pprint.pformat(self.dict(by_alias=True)) + + def to_json(self) -> str: + """Returns the JSON representation of the model using alias""" + return json.dumps(self.to_dict()) + + @classmethod + def from_json(cls, json_str: str) -> DashboardMockResponse: + """Create an instance of DashboardMockResponse from a JSON string""" + return cls.from_dict(json.loads(json_str)) + + def to_dict(self): + """Returns the dictionary representation of the model using alias""" + _dict = self.dict(by_alias=True, + exclude={ + }, + exclude_none=True) + # override the default output from pydantic by calling `to_dict()` of meta + if self.meta: + _dict['meta'] = self.meta.to_dict() + # override the default output from pydantic by calling `to_dict()` of each item in data (list) + _items = [] + if self.data: + for _item in self.data: + if _item: + _items.append(_item.to_dict()) + _dict['data'] = _items + # override the default output from pydantic by calling `to_dict()` of pagination + if self.pagination: + _dict['pagination'] = self.pagination.to_dict() + return _dict + + @classmethod + def from_dict(cls, obj: dict) -> DashboardMockResponse: + """Create an instance of DashboardMockResponse from a dict""" + if obj is None: + return None + + if not isinstance(obj, dict): + return DashboardMockResponse.parse_obj(obj) + + _obj = DashboardMockResponse.parse_obj({ + "meta": Response200.from_dict(obj.get("meta")) if obj.get("meta") is not None else None, + "data": [MockObject.from_dict(_item) for _item in obj.get("data")] if obj.get("data") is not None else None, + "pagination": DashboardMockResponsePagination.from_dict(obj.get("pagination")) if obj.get("pagination") is not None else None + }) + return _obj + diff --git a/src/python_client/emass_client/models/dashboard_mock_response_pagination.py b/src/python_client/emass_client/models/dashboard_mock_response_pagination.py new file mode 100644 index 00000000..e5aced20 --- /dev/null +++ b/src/python_client/emass_client/models/dashboard_mock_response_pagination.py @@ -0,0 +1,117 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +from __future__ import annotations +import pprint +import re # noqa: F401 +import json + + +from typing import Optional +from pydantic import BaseModel, Field, StrictInt, StrictStr + +class DashboardMockResponsePagination(BaseModel): + """ + DashboardMockResponsePagination + """ + total_count: Optional[StrictInt] = Field(None, alias="totalCount") + total_pages: Optional[StrictInt] = Field(None, alias="totalPages") + page_index: Optional[StrictInt] = Field(None, alias="pageIndex") + page_size: Optional[StrictInt] = Field(None, alias="pageSize") + prev_page_url: Optional[StrictStr] = Field(None, alias="prevPageUrl") + next_page_url: Optional[StrictStr] = Field(None, alias="nextPageUrl") + __properties = ["totalCount", "totalPages", "pageIndex", "pageSize", "prevPageUrl", "nextPageUrl"] + + class Config: + """Pydantic configuration""" + allow_population_by_field_name = True + validate_assignment = True + + def to_str(self) -> str: + """Returns the string representation of the model using alias""" + return pprint.pformat(self.dict(by_alias=True)) + + def to_json(self) -> str: + """Returns the JSON representation of the model using alias""" + return json.dumps(self.to_dict()) + + @classmethod + def from_json(cls, json_str: str) -> DashboardMockResponsePagination: + """Create an instance of DashboardMockResponsePagination from a JSON string""" + return cls.from_dict(json.loads(json_str)) + + def to_dict(self): + """Returns the dictionary representation of the model using alias""" + _dict = self.dict(by_alias=True, + exclude={ + }, + exclude_none=True) + return _dict + + @classmethod + def from_dict(cls, obj: dict) -> DashboardMockResponsePagination: + """Create an instance of DashboardMockResponsePagination from a dict""" + if obj is None: + return None + + if not isinstance(obj, dict): + return DashboardMockResponsePagination.parse_obj(obj) + + _obj = DashboardMockResponsePagination.parse_obj({ + "total_count": obj.get("totalCount"), + "total_pages": obj.get("totalPages"), + "page_index": obj.get("pageIndex"), + "page_size": obj.get("pageSize"), + "prev_page_url": obj.get("prevPageUrl"), + "next_page_url": obj.get("nextPageUrl") + }) + return _obj + diff --git a/src/python_client/emass_client/models/definition_transitions.py b/src/python_client/emass_client/models/definition_transitions.py index 41b7eb92..a72f8004 100644 --- a/src/python_client/emass_client/models/definition_transitions.py +++ b/src/python_client/emass_client/models/definition_transitions.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/instances_transitions.py b/src/python_client/emass_client/models/instances_transitions.py index 92f22284..88ca2107 100644 --- a/src/python_client/emass_client/models/instances_transitions.py +++ b/src/python_client/emass_client/models/instances_transitions.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_get.py b/src/python_client/emass_client/models/milestone_response_get.py index 68e7e5cf..af8e0bc0 100644 --- a/src/python_client/emass_client/models/milestone_response_get.py +++ b/src/python_client/emass_client/models/milestone_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_get_milestone.py b/src/python_client/emass_client/models/milestone_response_get_milestone.py index 9c45e4b9..82fd03f3 100644 --- a/src/python_client/emass_client/models/milestone_response_get_milestone.py +++ b/src/python_client/emass_client/models/milestone_response_get_milestone.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_post.py b/src/python_client/emass_client/models/milestone_response_post.py index 3216451a..e6d7eb51 100644 --- a/src/python_client/emass_client/models/milestone_response_post.py +++ b/src/python_client/emass_client/models/milestone_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_put.py b/src/python_client/emass_client/models/milestone_response_put.py index c0cb8d7a..2a284483 100644 --- a/src/python_client/emass_client/models/milestone_response_put.py +++ b/src/python_client/emass_client/models/milestone_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_get.py b/src/python_client/emass_client/models/milestones_get.py index f6eed302..0274e8ea 100644 --- a/src/python_client/emass_client/models/milestones_get.py +++ b/src/python_client/emass_client/models/milestones_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_put_post_delete.py b/src/python_client/emass_client/models/milestones_put_post_delete.py index 2803ad2c..34c71b67 100644 --- a/src/python_client/emass_client/models/milestones_put_post_delete.py +++ b/src/python_client/emass_client/models/milestones_put_post_delete.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_request_delete_body_inner.py b/src/python_client/emass_client/models/milestones_request_delete_body_inner.py index 92fd495f..6a167525 100644 --- a/src/python_client/emass_client/models/milestones_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/milestones_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_required_post.py b/src/python_client/emass_client/models/milestones_required_post.py index a1583ea0..c8c5720f 100644 --- a/src/python_client/emass_client/models/milestones_required_post.py +++ b/src/python_client/emass_client/models/milestones_required_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_required_put.py b/src/python_client/emass_client/models/milestones_required_put.py index 49d7cf68..5e87b55f 100644 --- a/src/python_client/emass_client/models/milestones_required_put.py +++ b/src/python_client/emass_client/models/milestones_required_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/mock_object.py b/src/python_client/emass_client/models/mock_object.py new file mode 100644 index 00000000..52f1b48d --- /dev/null +++ b/src/python_client/emass_client/models/mock_object.py @@ -0,0 +1,146 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +from __future__ import annotations +import pprint +import re # noqa: F401 +import json + + +from typing import Optional +from pydantic import BaseModel, Field, StrictBool, StrictInt, StrictStr + +class MockObject(BaseModel): + """ + MockObject + """ + poc_organization: Optional[StrictStr] = Field(None, alias="pocOrganization", description="[Required] Organization/Office represented. 100 Characters.") + resources: Optional[StrictStr] = Field(None, description="[Required] List of resources used. 250 Characters.") + owning_organization: Optional[StrictStr] = Field(None, alias="owningOrganization", description="[Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy.") + secondary_organization: Optional[StrictStr] = Field(None, alias="secondaryOrganization", description="[Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level.") + poc_first_name: Optional[StrictStr] = Field(None, alias="pocFirstName", description="[Conditional] First name of POC. 100 Characters.") + poc_last_name: Optional[StrictStr] = Field(None, alias="pocLastName", description="[Conditional] Last name of POC. 100 Characters.") + poc_email: Optional[StrictStr] = Field(None, alias="pocEmail", description="[Conditional] Email address of POC. 100 Characters.") + poc_phone_number: Optional[StrictStr] = Field(None, alias="pocPhoneNumber", description="[Conditional] Phone number of POC (area code) ***-**** format. 100 Characters.") + severity: Optional[StrictStr] = Field(None, description="[Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High)") + scheduled_completion_date: Optional[StrictInt] = Field(None, alias="scheduledCompletionDate", description="[Conditional] Required for ongoing and completed POA&M items. Unix time format.") + completion_date: Optional[StrictInt] = Field(None, alias="completionDate", description="[Conditional] Field is required for completed POA&M items. Unix time format.") + comments: Optional[StrictStr] = Field(None, description="[Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters") + is_active: Optional[StrictBool] = Field(None, alias="isActive", description="[Conditional] Optionally used in PUT to delete milestones when updating a POA&M.") + __properties = ["pocOrganization", "resources", "owningOrganization", "secondaryOrganization", "pocFirstName", "pocLastName", "pocEmail", "pocPhoneNumber", "severity", "scheduledCompletionDate", "completionDate", "comments", "isActive"] + + class Config: + """Pydantic configuration""" + allow_population_by_field_name = True + validate_assignment = True + + def to_str(self) -> str: + """Returns the string representation of the model using alias""" + return pprint.pformat(self.dict(by_alias=True)) + + def to_json(self) -> str: + """Returns the JSON representation of the model using alias""" + return json.dumps(self.to_dict()) + + @classmethod + def from_json(cls, json_str: str) -> MockObject: + """Create an instance of MockObject from a JSON string""" + return cls.from_dict(json.loads(json_str)) + + def to_dict(self): + """Returns the dictionary representation of the model using alias""" + _dict = self.dict(by_alias=True, + exclude={ + }, + exclude_none=True) + # set to None if owning_organization (nullable) is None + # and __fields_set__ contains the field + if self.owning_organization is None and "owning_organization" in self.__fields_set__: + _dict['owningOrganization'] = None + + # set to None if secondary_organization (nullable) is None + # and __fields_set__ contains the field + if self.secondary_organization is None and "secondary_organization" in self.__fields_set__: + _dict['secondaryOrganization'] = None + + # set to None if scheduled_completion_date (nullable) is None + # and __fields_set__ contains the field + if self.scheduled_completion_date is None and "scheduled_completion_date" in self.__fields_set__: + _dict['scheduledCompletionDate'] = None + + return _dict + + @classmethod + def from_dict(cls, obj: dict) -> MockObject: + """Create an instance of MockObject from a dict""" + if obj is None: + return None + + if not isinstance(obj, dict): + return MockObject.parse_obj(obj) + + _obj = MockObject.parse_obj({ + "poc_organization": obj.get("pocOrganization"), + "resources": obj.get("resources"), + "owning_organization": obj.get("owningOrganization"), + "secondary_organization": obj.get("secondaryOrganization"), + "poc_first_name": obj.get("pocFirstName"), + "poc_last_name": obj.get("pocLastName"), + "poc_email": obj.get("pocEmail"), + "poc_phone_number": obj.get("pocPhoneNumber"), + "severity": obj.get("severity"), + "scheduled_completion_date": obj.get("scheduledCompletionDate"), + "completion_date": obj.get("completionDate"), + "comments": obj.get("comments"), + "is_active": obj.get("isActive") + }) + return _obj + diff --git a/src/python_client/emass_client/models/pac_get.py b/src/python_client/emass_client/models/pac_get.py index 7afd4550..5a39d20c 100644 --- a/src/python_client/emass_client/models/pac_get.py +++ b/src/python_client/emass_client/models/pac_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_post.py b/src/python_client/emass_client/models/pac_post.py index a1351d38..5738933a 100644 --- a/src/python_client/emass_client/models/pac_post.py +++ b/src/python_client/emass_client/models/pac_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_response_get.py b/src/python_client/emass_client/models/pac_response_get.py index 42b6ea47..96219021 100644 --- a/src/python_client/emass_client/models/pac_response_get.py +++ b/src/python_client/emass_client/models/pac_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_response_post.py b/src/python_client/emass_client/models/pac_response_post.py index f211d96b..d5e87921 100644 --- a/src/python_client/emass_client/models/pac_response_post.py +++ b/src/python_client/emass_client/models/pac_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_get.py b/src/python_client/emass_client/models/poam_get.py index df97d74d..e2f2242b 100644 --- a/src/python_client/emass_client/models/poam_get.py +++ b/src/python_client/emass_client/models/poam_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_post_put_del.py b/src/python_client/emass_client/models/poam_post_put_del.py index 5bd57bd2..9af378a0 100644 --- a/src/python_client/emass_client/models/poam_post_put_del.py +++ b/src/python_client/emass_client/models/poam_post_put_del.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_request_delete_body_inner.py b/src/python_client/emass_client/models/poam_request_delete_body_inner.py index fcc2faf3..317bff76 100644 --- a/src/python_client/emass_client/models/poam_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/poam_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_delete.py b/src/python_client/emass_client/models/poam_response_delete.py index 29b7e130..3101abed 100644 --- a/src/python_client/emass_client/models/poam_response_delete.py +++ b/src/python_client/emass_client/models/poam_response_delete.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_get_poams.py b/src/python_client/emass_client/models/poam_response_get_poams.py index 4e341c72..d09ad3fd 100644 --- a/src/python_client/emass_client/models/poam_response_get_poams.py +++ b/src/python_client/emass_client/models/poam_response_get_poams.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_get_systems.py b/src/python_client/emass_client/models/poam_response_get_systems.py index 1cf53101..68a6d422 100644 --- a/src/python_client/emass_client/models/poam_response_get_systems.py +++ b/src/python_client/emass_client/models/poam_response_get_systems.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_post.py b/src/python_client/emass_client/models/poam_response_post.py index 68622df7..621b4f57 100644 --- a/src/python_client/emass_client/models/poam_response_post.py +++ b/src/python_client/emass_client/models/poam_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_put.py b/src/python_client/emass_client/models/poam_response_put.py index 11e17206..f7472d22 100644 --- a/src/python_client/emass_client/models/poam_response_put.py +++ b/src/python_client/emass_client/models/poam_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register.py b/src/python_client/emass_client/models/register.py index 712b8b42..cbacb62d 100644 --- a/src/python_client/emass_client/models/register.py +++ b/src/python_client/emass_client/models/register.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register_data.py b/src/python_client/emass_client/models/register_data.py index 66377f30..b4a73dd6 100644 --- a/src/python_client/emass_client/models/register_data.py +++ b/src/python_client/emass_client/models/register_data.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register_user_request_post_body.py b/src/python_client/emass_client/models/register_user_request_post_body.py index 8af80acd..96b1d939 100644 --- a/src/python_client/emass_client/models/register_user_request_post_body.py +++ b/src/python_client/emass_client/models/register_user_request_post_body.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response200.py b/src/python_client/emass_client/models/response200.py index a41dc049..3cb9b447 100644 --- a/src/python_client/emass_client/models/response200.py +++ b/src/python_client/emass_client/models/response200.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response201.py b/src/python_client/emass_client/models/response201.py index 64544f48..d1c3d793 100644 --- a/src/python_client/emass_client/models/response201.py +++ b/src/python_client/emass_client/models/response201.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response201_meta.py b/src/python_client/emass_client/models/response201_meta.py index 9875ab64..31bf2456 100644 --- a/src/python_client/emass_client/models/response201_meta.py +++ b/src/python_client/emass_client/models/response201_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response400.py b/src/python_client/emass_client/models/response400.py index 325fb684..b2060eca 100644 --- a/src/python_client/emass_client/models/response400.py +++ b/src/python_client/emass_client/models/response400.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response400_meta.py b/src/python_client/emass_client/models/response400_meta.py index e0853f55..04768b41 100644 --- a/src/python_client/emass_client/models/response400_meta.py +++ b/src/python_client/emass_client/models/response400_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response401.py b/src/python_client/emass_client/models/response401.py index e9ae79ba..7277725b 100644 --- a/src/python_client/emass_client/models/response401.py +++ b/src/python_client/emass_client/models/response401.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response401_meta.py b/src/python_client/emass_client/models/response401_meta.py index 37248e54..e5693b92 100644 --- a/src/python_client/emass_client/models/response401_meta.py +++ b/src/python_client/emass_client/models/response401_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response403.py b/src/python_client/emass_client/models/response403.py index 3c20c7a5..1b055d03 100644 --- a/src/python_client/emass_client/models/response403.py +++ b/src/python_client/emass_client/models/response403.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response403_meta.py b/src/python_client/emass_client/models/response403_meta.py index 43150681..fcbd5d0d 100644 --- a/src/python_client/emass_client/models/response403_meta.py +++ b/src/python_client/emass_client/models/response403_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response404.py b/src/python_client/emass_client/models/response404.py index bda4759b..48b22182 100644 --- a/src/python_client/emass_client/models/response404.py +++ b/src/python_client/emass_client/models/response404.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response405.py b/src/python_client/emass_client/models/response405.py index 8ff77b82..cf743396 100644 --- a/src/python_client/emass_client/models/response405.py +++ b/src/python_client/emass_client/models/response405.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response405_meta.py b/src/python_client/emass_client/models/response405_meta.py index 341dd999..1a940efb 100644 --- a/src/python_client/emass_client/models/response405_meta.py +++ b/src/python_client/emass_client/models/response405_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response411.py b/src/python_client/emass_client/models/response411.py index 14453e5f..671d539e 100644 --- a/src/python_client/emass_client/models/response411.py +++ b/src/python_client/emass_client/models/response411.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response411_meta.py b/src/python_client/emass_client/models/response411_meta.py index c559abab..e0c6198d 100644 --- a/src/python_client/emass_client/models/response411_meta.py +++ b/src/python_client/emass_client/models/response411_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response490.py b/src/python_client/emass_client/models/response490.py index 9a730011..151af4fd 100644 --- a/src/python_client/emass_client/models/response490.py +++ b/src/python_client/emass_client/models/response490.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response490_meta.py b/src/python_client/emass_client/models/response490_meta.py index 0b4c504a..e2830f63 100644 --- a/src/python_client/emass_client/models/response490_meta.py +++ b/src/python_client/emass_client/models/response490_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response500.py b/src/python_client/emass_client/models/response500.py index 0bf566fc..e7873db2 100644 --- a/src/python_client/emass_client/models/response500.py +++ b/src/python_client/emass_client/models/response500.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response500_meta.py b/src/python_client/emass_client/models/response500_meta.py index d1d7a8ef..71d1e291 100644 --- a/src/python_client/emass_client/models/response500_meta.py +++ b/src/python_client/emass_client/models/response500_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/role_category.py b/src/python_client/emass_client/models/role_category.py index c854695a..5e74aae0 100644 --- a/src/python_client/emass_client/models/role_category.py +++ b/src/python_client/emass_client/models/role_category.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/roles.py b/src/python_client/emass_client/models/roles.py index 39a1236d..c36a6e71 100644 --- a/src/python_client/emass_client/models/roles.py +++ b/src/python_client/emass_client/models/roles.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/ssps.py b/src/python_client/emass_client/models/ssps.py index 71587765..e24dc0dc 100644 --- a/src/python_client/emass_client/models/ssps.py +++ b/src/python_client/emass_client/models/ssps.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/stage.py b/src/python_client/emass_client/models/stage.py index da51fa77..6d8a4152 100644 --- a/src/python_client/emass_client/models/stage.py +++ b/src/python_client/emass_client/models/stage.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_application.py b/src/python_client/emass_client/models/static_code_application.py index 7da88afe..928e4f1e 100644 --- a/src/python_client/emass_client/models/static_code_application.py +++ b/src/python_client/emass_client/models/static_code_application.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_post.py b/src/python_client/emass_client/models/static_code_post.py index c8e2a689..f1c854b3 100644 --- a/src/python_client/emass_client/models/static_code_post.py +++ b/src/python_client/emass_client/models/static_code_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_request_post_body.py b/src/python_client/emass_client/models/static_code_request_post_body.py index 3675470f..72a5ae18 100644 --- a/src/python_client/emass_client/models/static_code_request_post_body.py +++ b/src/python_client/emass_client/models/static_code_request_post_body.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_request_post_body_application.py b/src/python_client/emass_client/models/static_code_request_post_body_application.py index 825698b6..3b316433 100644 --- a/src/python_client/emass_client/models/static_code_request_post_body_application.py +++ b/src/python_client/emass_client/models/static_code_request_post_body_application.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_response_post.py b/src/python_client/emass_client/models/static_code_response_post.py index ecc9f001..04891434 100644 --- a/src/python_client/emass_client/models/static_code_response_post.py +++ b/src/python_client/emass_client/models/static_code_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/success200_response.py b/src/python_client/emass_client/models/success200_response.py index 25d4f5b7..b56ac506 100644 --- a/src/python_client/emass_client/models/success200_response.py +++ b/src/python_client/emass_client/models/success200_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/success200_response_data_inner.py b/src/python_client/emass_client/models/success200_response_data_inner.py index 8bb7417f..b9688fa2 100644 --- a/src/python_client/emass_client/models/success200_response_data_inner.py +++ b/src/python_client/emass_client/models/success200_response_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_response.py b/src/python_client/emass_client/models/system_response.py index 9ac9bf59..bac9c9f7 100644 --- a/src/python_client/emass_client/models/system_response.py +++ b/src/python_client/emass_client/models/system_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_category_response.py b/src/python_client/emass_client/models/system_roles_category_response.py index a77981e8..7ca04d6f 100644 --- a/src/python_client/emass_client/models/system_roles_category_response.py +++ b/src/python_client/emass_client/models/system_roles_category_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_response.py b/src/python_client/emass_client/models/system_roles_response.py index 8c6f4e90..578ca6be 100644 --- a/src/python_client/emass_client/models/system_roles_response.py +++ b/src/python_client/emass_client/models/system_roles_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_response_data_inner.py b/src/python_client/emass_client/models/system_roles_response_data_inner.py index 027b151e..0836db10 100644 --- a/src/python_client/emass_client/models/system_roles_response_data_inner.py +++ b/src/python_client/emass_client/models/system_roles_response_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/systems.py b/src/python_client/emass_client/models/systems.py index a8f07c68..89f26fd6 100644 --- a/src/python_client/emass_client/models/systems.py +++ b/src/python_client/emass_client/models/systems.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -158,9 +158,11 @@ class Systems(BaseModel): atc_termination_date: Optional[StrictInt] = Field(None, alias="atcTerminationDate", description="[Read-Only] The Connectivity Authorization Termination Date.") system_development_life_cycle: Optional[StrictStr] = Field(None, alias="systemDevelopmentLifeCycle", description="[Read-Only] Indicate the date by which the System needs to be deployed to a production environment. VA only.") is_fisma_reportable: Optional[StrictBool] = Field(None, alias="isFISMAReportable", description="[Read-Only] Is this IS reportable per Federal Information Security Management Act (FISMA) established requirements? VA only") + group_tagging: Optional[StrictStr] = Field(None, alias="groupTagging", description="[Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only.") + group_tag_descriptions: Optional[StrictStr] = Field(None, alias="groupTagDescriptions", description="[Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only.") package: Optional[conlist(PacGet)] = None connectivity_ccsd: Optional[conlist(ConnectivityCcsd)] = Field(None, alias="connectivityCcsd") - __properties = ["registrationCompletionDate", "systemLifeCycleAcquisitionPhase", "specialType", "specialTypeDescription", "missionPortfolio", "isNNPI", "isRBC", "isWaiver", "programOffice", "vramId", "systemId", "policy", "registrationType", "name", "acronym", "description", "instance", "owningOrganization", "secondaryOrganization", "versionReleaseNo", "systemType", "isNSS", "isPublicFacing", "coamsId", "isTypeAuthorization", "ditprId", "apmsId", "vasiId", "authorizationStatus", "authorizationDate", "authorizationTerminationDate", "authorizationLength", "termsForAuth", "securityPlanApprovalStatus", "securityPlanApprovalDate", "missionCriticality", "geographicalAssociation", "systemOwnership", "governingMissionArea", "primaryFunctionalArea", "secondaryFunctionalArea", "primaryControlSet", "confidentiality", "integrity", "availability", "appliedOverlays", "rmfActivity", "crossDomainTicket", "ditprDonId", "mac", "dodConfidentiality", "contingencyPlanTested", "contingencyPlanTestDate", "securityReviewDate", "hasOpenPoamItem", "hasOpenPoamItem90to120PastScheduledCompletionDate", "hasOpenPoamItem120PlusPastScheudledCompletionDate", "impact", "hasCUI", "hasPII", "hasPHI", "ppsmRegistryNumber", "interconnectedInformationSystemAndIdentifiers", "isPiaRequired", "piaStatus", "piaDate", "userDefinedField1", "userDefinedField2", "userDefinedField3", "userDefinedField4", "userDefinedField5", "currentRmfLifecycleStep", "otherInformation", "reportsForScorecard", "highestSystemDataClassification", "overallClassification", "isHVA", "isFinancialManagement", "isReciprocity", "reciprocityExemption", "cloudComputing", "cloudType", "atcStatus", "isSaaS", "isPaaS", "isIaaS", "otherServiceModels", "needDate", "overallRiskScore", "isHRR", "atcDate", "atcTerminationDate", "systemDevelopmentLifeCycle", "isFISMAReportable", "package", "connectivityCcsd"] + __properties = ["registrationCompletionDate", "systemLifeCycleAcquisitionPhase", "specialType", "specialTypeDescription", "missionPortfolio", "isNNPI", "isRBC", "isWaiver", "programOffice", "vramId", "systemId", "policy", "registrationType", "name", "acronym", "description", "instance", "owningOrganization", "secondaryOrganization", "versionReleaseNo", "systemType", "isNSS", "isPublicFacing", "coamsId", "isTypeAuthorization", "ditprId", "apmsId", "vasiId", "authorizationStatus", "authorizationDate", "authorizationTerminationDate", "authorizationLength", "termsForAuth", "securityPlanApprovalStatus", "securityPlanApprovalDate", "missionCriticality", "geographicalAssociation", "systemOwnership", "governingMissionArea", "primaryFunctionalArea", "secondaryFunctionalArea", "primaryControlSet", "confidentiality", "integrity", "availability", "appliedOverlays", "rmfActivity", "crossDomainTicket", "ditprDonId", "mac", "dodConfidentiality", "contingencyPlanTested", "contingencyPlanTestDate", "securityReviewDate", "hasOpenPoamItem", "hasOpenPoamItem90to120PastScheduledCompletionDate", "hasOpenPoamItem120PlusPastScheudledCompletionDate", "impact", "hasCUI", "hasPII", "hasPHI", "ppsmRegistryNumber", "interconnectedInformationSystemAndIdentifiers", "isPiaRequired", "piaStatus", "piaDate", "userDefinedField1", "userDefinedField2", "userDefinedField3", "userDefinedField4", "userDefinedField5", "currentRmfLifecycleStep", "otherInformation", "reportsForScorecard", "highestSystemDataClassification", "overallClassification", "isHVA", "isFinancialManagement", "isReciprocity", "reciprocityExemption", "cloudComputing", "cloudType", "atcStatus", "isSaaS", "isPaaS", "isIaaS", "otherServiceModels", "needDate", "overallRiskScore", "isHRR", "atcDate", "atcTerminationDate", "systemDevelopmentLifeCycle", "isFISMAReportable", "groupTagging", "groupTagDescriptions", "package", "connectivityCcsd"] @validator('policy') def policy_validate_enum(cls, value): @@ -810,6 +812,16 @@ def to_dict(self): if self.is_fisma_reportable is None and "is_fisma_reportable" in self.__fields_set__: _dict['isFISMAReportable'] = None + # set to None if group_tagging (nullable) is None + # and __fields_set__ contains the field + if self.group_tagging is None and "group_tagging" in self.__fields_set__: + _dict['groupTagging'] = None + + # set to None if group_tag_descriptions (nullable) is None + # and __fields_set__ contains the field + if self.group_tag_descriptions is None and "group_tag_descriptions" in self.__fields_set__: + _dict['groupTagDescriptions'] = None + # set to None if package (nullable) is None # and __fields_set__ contains the field if self.package is None and "package" in self.__fields_set__: @@ -926,6 +938,8 @@ def from_dict(cls, obj: dict) -> Systems: "atc_termination_date": obj.get("atcTerminationDate"), "system_development_life_cycle": obj.get("systemDevelopmentLifeCycle"), "is_fisma_reportable": obj.get("isFISMAReportable"), + "group_tagging": obj.get("groupTagging"), + "group_tag_descriptions": obj.get("groupTagDescriptions"), "package": [PacGet.from_dict(_item) for _item in obj.get("package")] if obj.get("package") is not None else None, "connectivity_ccsd": [ConnectivityCcsd.from_dict(_item) for _item in obj.get("connectivityCcsd")] if obj.get("connectivityCcsd") is not None else None }) diff --git a/src/python_client/emass_client/models/systems_response.py b/src/python_client/emass_client/models/systems_response.py index 87a7465c..a5d3dd84 100644 --- a/src/python_client/emass_client/models/systems_response.py +++ b/src/python_client/emass_client/models/systems_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test.py b/src/python_client/emass_client/models/test.py index 4a5b92db..868b3ea2 100644 --- a/src/python_client/emass_client/models/test.py +++ b/src/python_client/emass_client/models/test.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_data.py b/src/python_client/emass_client/models/test_data.py index fa4d6953..d1264d68 100644 --- a/src/python_client/emass_client/models/test_data.py +++ b/src/python_client/emass_client/models/test_data.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_get.py b/src/python_client/emass_client/models/test_results_get.py index 22399ea7..f2cc3766 100644 --- a/src/python_client/emass_client/models/test_results_get.py +++ b/src/python_client/emass_client/models/test_results_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_post.py b/src/python_client/emass_client/models/test_results_post.py index 637b16dd..91c83946 100644 --- a/src/python_client/emass_client/models/test_results_post.py +++ b/src/python_client/emass_client/models/test_results_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_response_get.py b/src/python_client/emass_client/models/test_results_response_get.py index fb2482f7..7c1a5407 100644 --- a/src/python_client/emass_client/models/test_results_response_get.py +++ b/src/python_client/emass_client/models/test_results_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_response_post.py b/src/python_client/emass_client/models/test_results_response_post.py index 336d87e4..45a32714 100644 --- a/src/python_client/emass_client/models/test_results_response_post.py +++ b/src/python_client/emass_client/models/test_results_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/users.py b/src/python_client/emass_client/models/users.py index 6fdbb82a..59cdcabc 100644 --- a/src/python_client/emass_client/models/users.py +++ b/src/python_client/emass_client/models/users.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_definition_get.py b/src/python_client/emass_client/models/workflow_definition_get.py index 9c1f4f7a..7dde21ee 100644 --- a/src/python_client/emass_client/models/workflow_definition_get.py +++ b/src/python_client/emass_client/models/workflow_definition_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_definition_response_get.py b/src/python_client/emass_client/models/workflow_definition_response_get.py index ed8c214c..15aec301 100644 --- a/src/python_client/emass_client/models/workflow_definition_response_get.py +++ b/src/python_client/emass_client/models/workflow_definition_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instance_get.py b/src/python_client/emass_client/models/workflow_instance_get.py index be1b294b..576b50d4 100644 --- a/src/python_client/emass_client/models/workflow_instance_get.py +++ b/src/python_client/emass_client/models/workflow_instance_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instance_response_get.py b/src/python_client/emass_client/models/workflow_instance_response_get.py index b023171b..4bd46901 100644 --- a/src/python_client/emass_client/models/workflow_instance_response_get.py +++ b/src/python_client/emass_client/models/workflow_instance_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -55,8 +55,8 @@ import json -from typing import List, Optional -from pydantic import BaseModel, conlist +from typing import Optional +from pydantic import BaseModel from emass_client.models.response200 import Response200 from emass_client.models.workflow_instance_get import WorkflowInstanceGet @@ -65,7 +65,7 @@ class WorkflowInstanceResponseGet(BaseModel): WorkflowInstanceResponseGet """ meta: Optional[Response200] = None - data: Optional[conlist(WorkflowInstanceGet)] = None + data: Optional[WorkflowInstanceGet] = None __properties = ["meta", "data"] class Config: @@ -95,13 +95,9 @@ def to_dict(self): # override the default output from pydantic by calling `to_dict()` of meta if self.meta: _dict['meta'] = self.meta.to_dict() - # override the default output from pydantic by calling `to_dict()` of each item in data (list) - _items = [] + # override the default output from pydantic by calling `to_dict()` of data if self.data: - for _item in self.data: - if _item: - _items.append(_item.to_dict()) - _dict['data'] = _items + _dict['data'] = self.data.to_dict() return _dict @classmethod @@ -115,7 +111,7 @@ def from_dict(cls, obj: dict) -> WorkflowInstanceResponseGet: _obj = WorkflowInstanceResponseGet.parse_obj({ "meta": Response200.from_dict(obj.get("meta")) if obj.get("meta") is not None else None, - "data": [WorkflowInstanceGet.from_dict(_item) for _item in obj.get("data")] if obj.get("data") is not None else None + "data": WorkflowInstanceGet.from_dict(obj.get("data")) if obj.get("data") is not None else None }) return _obj diff --git a/src/python_client/emass_client/models/workflow_instances_get.py b/src/python_client/emass_client/models/workflow_instances_get.py index 82fa65ef..217f1760 100644 --- a/src/python_client/emass_client/models/workflow_instances_get.py +++ b/src/python_client/emass_client/models/workflow_instances_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instances_response_get.py b/src/python_client/emass_client/models/workflow_instances_response_get.py index 7ddeab57..50583611 100644 --- a/src/python_client/emass_client/models/workflow_instances_response_get.py +++ b/src/python_client/emass_client/models/workflow_instances_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py b/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py index cd6ccbf9..c744cdbe 100644 --- a/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py +++ b/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/py.typed b/src/python_client/emass_client/py.typed new file mode 100644 index 00000000..e69de29b diff --git a/src/python_client/emass_client/rest.py b/src/python_client/emass_client/rest.py index 7134b4a6..92f302b4 100644 --- a/src/python_client/emass_client/rest.py +++ b/src/python_client/emass_client/rest.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -58,7 +58,7 @@ from urllib.parse import urlencode, quote_plus import urllib3 -from emass_client.exceptions import ApiException, UnauthorizedException, ForbiddenException, NotFoundException, ServiceException, ApiValueError +from emass_client.exceptions import ApiException, UnauthorizedException, ForbiddenException, NotFoundException, ServiceException, ApiValueError, BadRequestException logger = logging.getLogger(__name__) @@ -255,6 +255,9 @@ def request(self, method, url, query_params=None, headers=None, logger.debug("response body: %s", r.data) if not 200 <= r.status <= 299: + if r.status == 400: + raise BadRequestException(http_resp=r) + if r.status == 401: raise UnauthorizedException(http_resp=r) diff --git a/src/python_client/pyproject.toml b/src/python_client/pyproject.toml index 00c2cc2f..b4ccf7bb 100644 --- a/src/python_client/pyproject.toml +++ b/src/python_client/pyproject.toml @@ -1,12 +1,13 @@ [tool.poetry] name = "emass_client" -version = "3.9.1" +version = "3.10.0" description = "Enterprise Mission Assurance Support Service (eMASS)" authors = ["eMASS Tier III support "] license = "Apache-2.0" readme = "README.md" repository = "https://github.com/GIT_USER_ID/GIT_REPO_ID" keywords = ["OpenAPI", "OpenAPI-Generator", "Enterprise Mission Assurance Support Service (eMASS)"] +include = ["emass_client/py.typed"] [tool.poetry.dependencies] python = "^3.7" diff --git a/src/python_client/requirements.txt b/src/python_client/requirements.txt index 74ede174..258c179c 100644 --- a/src/python_client/requirements.txt +++ b/src/python_client/requirements.txt @@ -1,5 +1,5 @@ python_dateutil >= 2.5.3 setuptools >= 21.0.0 -urllib3 >= 1.25.3 +urllib3 >= 1.25.3, < 2.1.0 pydantic >= 1.10.5, < 2 aenum >= 3.1.11 diff --git a/src/python_client/setup.py b/src/python_client/setup.py index 75cf67fd..45c49292 100644 --- a/src/python_client/setup.py +++ b/src/python_client/setup.py @@ -9,7 +9,7 @@ # prerequisite: setuptools # http://pypi.python.org/pypi/setuptools NAME = "emass_client_api" -VERSION = "3.9.1" +VERSION = "3.10.0" PYTHON_REQUIRES = ">=3.7" REQUIRES = [ "urllib3 >= 1.25.3", @@ -32,7 +32,7 @@ license="Apache-2.0", long_description_content_type='text/markdown', long_description="""\ - ## eMASS API v3.9 Specification + ## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -40,9 +40,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_api.py b/src/python_client/test/test_artifacts_api.py index 8925a8e7..523cfa20 100644 --- a/src/python_client/test/test_artifacts_api.py +++ b/src/python_client/test/test_artifacts_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_export_api.py b/src/python_client/test/test_artifacts_export_api.py index 5abde9e8..7fef210d 100644 --- a/src/python_client/test/test_artifacts_export_api.py +++ b/src/python_client/test/test_artifacts_export_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_get.py b/src/python_client/test/test_artifacts_get.py index 24b90c53..e1d3f12a 100644 --- a/src/python_client/test/test_artifacts_get.py +++ b/src/python_client/test/test_artifacts_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_request_delete_body_inner.py b/src/python_client/test/test_artifacts_request_delete_body_inner.py index b78a6478..9ba04b45 100644 --- a/src/python_client/test/test_artifacts_request_delete_body_inner.py +++ b/src/python_client/test/test_artifacts_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_del.py b/src/python_client/test/test_artifacts_response_del.py index 5eeb5fb8..cda17775 100644 --- a/src/python_client/test/test_artifacts_response_del.py +++ b/src/python_client/test/test_artifacts_response_del.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_del_data_inner.py b/src/python_client/test/test_artifacts_response_del_data_inner.py index 25e06be3..1ff869d3 100644 --- a/src/python_client/test/test_artifacts_response_del_data_inner.py +++ b/src/python_client/test/test_artifacts_response_del_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_get.py b/src/python_client/test/test_artifacts_response_get.py index f731b00d..fbadcd2f 100644 --- a/src/python_client/test/test_artifacts_response_get.py +++ b/src/python_client/test/test_artifacts_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_put_post.py b/src/python_client/test/test_artifacts_response_put_post.py index 9e79c198..7a15d76c 100644 --- a/src/python_client/test/test_artifacts_response_put_post.py +++ b/src/python_client/test/test_artifacts_response_put_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_put_post_data_inner.py b/src/python_client/test/test_artifacts_response_put_post_data_inner.py index 7f19c59a..5399ce58 100644 --- a/src/python_client/test/test_artifacts_response_put_post_data_inner.py +++ b/src/python_client/test/test_artifacts_response_put_post_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_api.py b/src/python_client/test/test_cac_api.py index 01ba4cd2..c94c2b43 100644 --- a/src/python_client/test/test_cac_api.py +++ b/src/python_client/test/test_cac_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_get.py b/src/python_client/test/test_cac_get.py index c7302fe5..87a44963 100644 --- a/src/python_client/test/test_cac_get.py +++ b/src/python_client/test/test_cac_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_get.py b/src/python_client/test/test_cac_response_get.py index 9a985c97..13518a4b 100644 --- a/src/python_client/test/test_cac_response_get.py +++ b/src/python_client/test/test_cac_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_post.py b/src/python_client/test/test_cac_response_post.py index 42bdcd05..755a89bd 100644 --- a/src/python_client/test/test_cac_response_post.py +++ b/src/python_client/test/test_cac_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_post_data_inner.py b/src/python_client/test/test_cac_response_post_data_inner.py index a8169d15..7eb906c2 100644 --- a/src/python_client/test/test_cac_response_post_data_inner.py +++ b/src/python_client/test/test_cac_response_post_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resource_results_api.py b/src/python_client/test/test_cloud_resource_results_api.py index c064d67b..08b25ae2 100644 --- a/src/python_client/test/test_cloud_resource_results_api.py +++ b/src/python_client/test/test_cloud_resource_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_post.py b/src/python_client/test/test_cloud_resources_post.py index 2a34ccee..5f01ecab 100644 --- a/src/python_client/test/test_cloud_resources_post.py +++ b/src/python_client/test/test_cloud_resources_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_response_post.py b/src/python_client/test/test_cloud_resources_response_post.py index f127c02f..3b6de017 100644 --- a/src/python_client/test/test_cloud_resources_response_post.py +++ b/src/python_client/test/test_cloud_resources_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_assessments_api.py b/src/python_client/test/test_cmmc_assessments_api.py index 9baef73e..26ad87c0 100644 --- a/src/python_client/test/test_cmmc_assessments_api.py +++ b/src/python_client/test/test_cmmc_assessments_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_get.py b/src/python_client/test/test_cmmc_get.py index c34b75cf..0d6ea9da 100644 --- a/src/python_client/test/test_cmmc_get.py +++ b/src/python_client/test/test_cmmc_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_response_get.py b/src/python_client/test/test_cmmc_response_get.py index e51af540..7fa68dde 100644 --- a/src/python_client/test/test_cmmc_response_get.py +++ b/src/python_client/test/test_cmmc_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_connectivity_ccsd.py b/src/python_client/test/test_connectivity_ccsd.py index c8014889..16e53b86 100644 --- a/src/python_client/test/test_connectivity_ccsd.py +++ b/src/python_client/test/test_connectivity_ccsd.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_container_scan_results_api.py b/src/python_client/test/test_container_scan_results_api.py index 8cd51c5d..092e174a 100644 --- a/src/python_client/test/test_container_scan_results_api.py +++ b/src/python_client/test/test_container_scan_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_containers_resources_post.py b/src/python_client/test/test_containers_resources_post.py index ecdde18c..ef076570 100644 --- a/src/python_client/test/test_containers_resources_post.py +++ b/src/python_client/test/test_containers_resources_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_containers_response_post.py b/src/python_client/test/test_containers_response_post.py index e6e67aba..2a0df1a9 100644 --- a/src/python_client/test/test_containers_response_post.py +++ b/src/python_client/test/test_containers_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_api.py b/src/python_client/test/test_controls_api.py index 4adae362..6bc7200d 100644 --- a/src/python_client/test/test_controls_api.py +++ b/src/python_client/test/test_controls_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_get.py b/src/python_client/test/test_controls_get.py index cb23b0e2..feb305c2 100644 --- a/src/python_client/test/test_controls_get.py +++ b/src/python_client/test/test_controls_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_put.py b/src/python_client/test/test_controls_put.py index c69332b2..a88cfbdf 100644 --- a/src/python_client/test/test_controls_put.py +++ b/src/python_client/test/test_controls_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_response_get.py b/src/python_client/test/test_controls_response_get.py index 4f03140e..e4b203be 100644 --- a/src/python_client/test/test_controls_response_get.py +++ b/src/python_client/test/test_controls_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_response_put.py b/src/python_client/test/test_controls_response_put.py index f4fc2fea..7f0655ba 100644 --- a/src/python_client/test/test_controls_response_put.py +++ b/src/python_client/test/test_controls_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_dashboard_mock_response.py b/src/python_client/test/test_dashboard_mock_response.py new file mode 100644 index 00000000..9589a0a9 --- /dev/null +++ b/src/python_client/test/test_dashboard_mock_response.py @@ -0,0 +1,115 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +import unittest +import datetime + +import emass_client +from emass_client.models.dashboard_mock_response import DashboardMockResponse # noqa: E501 +from emass_client.rest import ApiException + +class TestDashboardMockResponse(unittest.TestCase): + """DashboardMockResponse unit test stubs""" + + def setUp(self): + pass + + def tearDown(self): + pass + + def make_instance(self, include_optional): + """Test DashboardMockResponse + include_option is a boolean, when False only required + params are included, when True both required and + optional params are included """ + # uncomment below to create an instance of `DashboardMockResponse` + """ + model = emass_client.models.dashboard_mock_response.DashboardMockResponse() # noqa: E501 + if include_optional : + return DashboardMockResponse( + meta = emass_client.models.ok.OK( + code = 200, ), + data = [ + emass_client.models.object_mock_data.Object mock data( + poc_organization = 'Army', + resources = 'Resource text.', + owning_organization = 'Defense Information Systems Agency', + secondary_organization = 'ID31', + poc_first_name = 'John', + poc_last_name = 'Smith', + poc_email = 'smith@ah.com', + poc_phone_number = '555-555-5555', + severity = 'Low', + scheduled_completion_date = 1599644800, + completion_date = 1505916276, + comments = 'Comments text.', + is_active = True, ) + ], + pagination = emass_client.models.dashboard_mock_response_pagination.DashboardMockResponse_pagination( + total_count = 2, + total_pages = 1, + page_index = 2, + page_size = 20000, + prev_page_url = 'https://myfakeurl.reponse.page.com?PreviousPage', + next_page_url = 'https://myfakeurl.reponse.page.com?NextPage', ) + ) + else : + return DashboardMockResponse( + ) + """ + + def testDashboardMockResponse(self): + """Test DashboardMockResponse""" + # inst_req_only = self.make_instance(include_optional=False) + # inst_req_and_optional = self.make_instance(include_optional=True) + +if __name__ == '__main__': + unittest.main() diff --git a/src/python_client/test/test_dashboard_mock_response_pagination.py b/src/python_client/test/test_dashboard_mock_response_pagination.py new file mode 100644 index 00000000..59c5119f --- /dev/null +++ b/src/python_client/test/test_dashboard_mock_response_pagination.py @@ -0,0 +1,96 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +import unittest +import datetime + +import emass_client +from emass_client.models.dashboard_mock_response_pagination import DashboardMockResponsePagination # noqa: E501 +from emass_client.rest import ApiException + +class TestDashboardMockResponsePagination(unittest.TestCase): + """DashboardMockResponsePagination unit test stubs""" + + def setUp(self): + pass + + def tearDown(self): + pass + + def make_instance(self, include_optional): + """Test DashboardMockResponsePagination + include_option is a boolean, when False only required + params are included, when True both required and + optional params are included """ + # uncomment below to create an instance of `DashboardMockResponsePagination` + """ + model = emass_client.models.dashboard_mock_response_pagination.DashboardMockResponsePagination() # noqa: E501 + if include_optional : + return DashboardMockResponsePagination( + total_count = 2, + total_pages = 1, + page_index = 2, + page_size = 20000, + prev_page_url = 'https://myfakeurl.reponse.page.com?PreviousPage', + next_page_url = 'https://myfakeurl.reponse.page.com?NextPage' + ) + else : + return DashboardMockResponsePagination( + ) + """ + + def testDashboardMockResponsePagination(self): + """Test DashboardMockResponsePagination""" + # inst_req_only = self.make_instance(include_optional=False) + # inst_req_and_optional = self.make_instance(include_optional=True) + +if __name__ == '__main__': + unittest.main() diff --git a/src/python_client/test/test_dashboards_api.py b/src/python_client/test/test_dashboards_api.py index 67008ed5..95ede325 100644 --- a/src/python_client/test/test_dashboards_api.py +++ b/src/python_client/test/test_dashboards_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -68,182 +68,203 @@ def tearDown(self): def test_get_system_artifacts_details(self): """Test case for get_system_artifacts_details - Get dashboard information # noqa: E501 + System Artifacts Details # noqa: E501 """ pass def test_get_system_artifacts_summary(self): """Test case for get_system_artifacts_summary - Get dashboard information # noqa: E501 + System Artifacts Summary # noqa: E501 """ pass def test_get_system_assessment_procedures_details(self): """Test case for get_system_assessment_procedures_details - Get dashboard information # noqa: E501 + System Assessment Procedures Details # noqa: E501 """ pass def test_get_system_associations_details(self): """Test case for get_system_associations_details - Get dashboard information # noqa: E501 + System Associations Details # noqa: E501 + """ + pass + + def test_get_system_common_integration_status_summary(self): + """Test case for get_system_common_integration_status_summary + + System CONMON Integration Status # noqa: E501 """ pass def test_get_system_control_compliance_summary(self): """Test case for get_system_control_compliance_summary - Get dashboard information # noqa: E501 + System Control Compliance Summary # noqa: E501 """ pass def test_get_system_hardware_details(self): """Test case for get_system_hardware_details - Get dashboard information # noqa: E501 + System Hardware Details # noqa: E501 """ pass def test_get_system_hardware_summary(self): """Test case for get_system_hardware_summary - Get dashboard information # noqa: E501 + System Hardware Summary # noqa: E501 """ pass def test_get_system_poam_details(self): """Test case for get_system_poam_details - Get dashboard information # noqa: E501 + System POA&M Details # noqa: E501 """ pass def test_get_system_poam_summary(self): """Test case for get_system_poam_summary - Get dashboard information # noqa: E501 + System POA&M Summary # noqa: E501 """ pass def test_get_system_ports_protocols_details(self): """Test case for get_system_ports_protocols_details - Get dashboard information # noqa: E501 + System Ports/Protocols Details # noqa: E501 """ pass def test_get_system_ports_protocols_summary(self): """Test case for get_system_ports_protocols_summary - Get dashboard information # noqa: E501 + System Ports/Protocols Summary # noqa: E501 """ pass def test_get_system_privacy_summary(self): """Test case for get_system_privacy_summary - Get dashboard information # noqa: E501 + System Privacy Summary # noqa: E501 """ pass def test_get_system_security_control_details(self): """Test case for get_system_security_control_details - Get dashboard information # noqa: E501 + System Control Compliance Details # noqa: E501 """ pass def test_get_system_sensor_hardware_details(self): """Test case for get_system_sensor_hardware_details - Get dashboard information # noqa: E501 + System Sensor Hardware Details # noqa: E501 """ pass def test_get_system_sensor_hardware_summary(self): """Test case for get_system_sensor_hardware_summary - Get dashboard information # noqa: E501 + System Sensor Hardware Summary # noqa: E501 + """ + pass + + def test_get_system_software_details(self): + """Test case for get_system_software_details + + System Software Details # noqa: E501 + """ + pass + + def test_get_system_software_summary(self): + """Test case for get_system_software_summary + + System Software Summary # noqa: E501 """ pass def test_get_system_status_details(self): """Test case for get_system_status_details - Get dashboard information # noqa: E501 + System Status Details # noqa: E501 """ pass def test_get_user_system_assignments_details(self): """Test case for get_user_system_assignments_details - Get dashboard information # noqa: E501 + User System Assignments Details # noqa: E501 """ pass def test_get_va_omb_fsma_saop_summary(self): """Test case for get_va_omb_fsma_saop_summary - Get dashboard information # noqa: E501 + VA OMB FISMA SAOP Summary # noqa: E501 """ pass def test_get_va_system_a2_summary(self): """Test case for get_va_system_a2_summary - Get dashboard information # noqa: E501 + VA System A2.0 Summary # noqa: E501 """ pass def test_get_va_system_aa_summary(self): """Test case for get_va_system_aa_summary - Get dashboard information # noqa: E501 + VA System A&A Summary # noqa: E501 """ pass def test_get_va_system_fisma_invetory_crypto_summary(self): """Test case for get_va_system_fisma_invetory_crypto_summary - Get dashboard information # noqa: E501 + VA System FISMA Inventory Crypto Summary # noqa: E501 """ pass def test_get_va_system_fisma_invetory_summary(self): """Test case for get_va_system_fisma_invetory_summary - Get dashboard information # noqa: E501 + VA System FISMA Inventory Summary # noqa: E501 """ pass def test_get_va_system_pl109_reporting_summary(self): """Test case for get_va_system_pl109_reporting_summary - Get dashboard information # noqa: E501 + VA System P.L. 109 Reporting Summary # noqa: E501 """ pass def test_get_va_system_threat_architecture_details(self): """Test case for get_va_system_threat_architecture_details - Get dashboard information # noqa: E501 + VA System Threat Architecture Details # noqa: E501 """ pass def test_get_va_system_threat_risk_summary(self): """Test case for get_va_system_threat_risk_summary - Get dashboard information # noqa: E501 + VA System Threat Risks Summary # noqa: E501 """ pass def test_get_va_system_threat_source_details(self): """Test case for get_va_system_threat_source_details - Get dashboard information # noqa: E501 + VA System Threat Sources Details # noqa: E501 """ pass diff --git a/src/python_client/test/test_definition_transitions.py b/src/python_client/test/test_definition_transitions.py index 7969f247..33c975e7 100644 --- a/src/python_client/test/test_definition_transitions.py +++ b/src/python_client/test/test_definition_transitions.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_instances_transitions.py b/src/python_client/test/test_instances_transitions.py index 1edfdba7..4e5da72f 100644 --- a/src/python_client/test/test_instances_transitions.py +++ b/src/python_client/test/test_instances_transitions.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_get.py b/src/python_client/test/test_milestone_response_get.py index 21b939fc..30832303 100644 --- a/src/python_client/test/test_milestone_response_get.py +++ b/src/python_client/test/test_milestone_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_get_milestone.py b/src/python_client/test/test_milestone_response_get_milestone.py index eac7b4d1..d069dc79 100644 --- a/src/python_client/test/test_milestone_response_get_milestone.py +++ b/src/python_client/test/test_milestone_response_get_milestone.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_post.py b/src/python_client/test/test_milestone_response_post.py index 9f614bcf..b0b1d4f3 100644 --- a/src/python_client/test/test_milestone_response_post.py +++ b/src/python_client/test/test_milestone_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_put.py b/src/python_client/test/test_milestone_response_put.py index 3c7fbdb6..b72dd857 100644 --- a/src/python_client/test/test_milestone_response_put.py +++ b/src/python_client/test/test_milestone_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_api.py b/src/python_client/test/test_milestones_api.py index 256297a5..3567fed5 100644 --- a/src/python_client/test/test_milestones_api.py +++ b/src/python_client/test/test_milestones_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_get.py b/src/python_client/test/test_milestones_get.py index 70dae670..dd5ecf1a 100644 --- a/src/python_client/test/test_milestones_get.py +++ b/src/python_client/test/test_milestones_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_put_post_delete.py b/src/python_client/test/test_milestones_put_post_delete.py index 36161e12..b3d53349 100644 --- a/src/python_client/test/test_milestones_put_post_delete.py +++ b/src/python_client/test/test_milestones_put_post_delete.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_request_delete_body_inner.py b/src/python_client/test/test_milestones_request_delete_body_inner.py index 0f5c2572..974f857f 100644 --- a/src/python_client/test/test_milestones_request_delete_body_inner.py +++ b/src/python_client/test/test_milestones_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_required_post.py b/src/python_client/test/test_milestones_required_post.py index bd45085d..c1d05dbd 100644 --- a/src/python_client/test/test_milestones_required_post.py +++ b/src/python_client/test/test_milestones_required_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_required_put.py b/src/python_client/test/test_milestones_required_put.py index 1eec13aa..32ee9fb0 100644 --- a/src/python_client/test/test_milestones_required_put.py +++ b/src/python_client/test/test_milestones_required_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_mock_object.py b/src/python_client/test/test_mock_object.py new file mode 100644 index 00000000..90c8df57 --- /dev/null +++ b/src/python_client/test/test_mock_object.py @@ -0,0 +1,103 @@ +# coding: utf-8 + +## eMASS API v3.10 Specification + +The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) +Representational State Transfer (REST) Application Programming Interface (API) specifications. + + +This Python package was generated from the eMASS API specification: + +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] + +## Requirements. + +Python + +## Installation & Usage +### pip install + +If the python package is hosted on a repository, you can install directly using: + +```sh +pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git +``` +(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/GIT_USER_ID/GIT_REPO_ID.git`) + +Then import the package: +```python +import emass_client +``` + +### Setuptools + +Install via [Setuptools](http://pypi.python.org/pypi/setuptools). + +```sh +python setup.py install --user +``` +(or `sudo python setup.py install` to install the package for all users) + +Then import the package: +```python +import emass_client +``` + +### Tests + +Execute `pytest` to run the tests. + +import unittest +import datetime + +import emass_client +from emass_client.models.mock_object import MockObject # noqa: E501 +from emass_client.rest import ApiException + +class TestMockObject(unittest.TestCase): + """MockObject unit test stubs""" + + def setUp(self): + pass + + def tearDown(self): + pass + + def make_instance(self, include_optional): + """Test MockObject + include_option is a boolean, when False only required + params are included, when True both required and + optional params are included """ + # uncomment below to create an instance of `MockObject` + """ + model = emass_client.models.mock_object.MockObject() # noqa: E501 + if include_optional : + return MockObject( + poc_organization = 'Army', + resources = 'Resource text.', + owning_organization = 'Defense Information Systems Agency', + secondary_organization = 'ID31', + poc_first_name = 'John', + poc_last_name = 'Smith', + poc_email = 'smith@ah.com', + poc_phone_number = '555-555-5555', + severity = 'Low', + scheduled_completion_date = 1599644800, + completion_date = 1505916276, + comments = 'Comments text.', + is_active = True + ) + else : + return MockObject( + ) + """ + + def testMockObject(self): + """Test MockObject""" + # inst_req_only = self.make_instance(include_optional=False) + # inst_req_and_optional = self.make_instance(include_optional=True) + +if __name__ == '__main__': + unittest.main() diff --git a/src/python_client/test/test_pac_api.py b/src/python_client/test/test_pac_api.py index 8459d27a..d4ea0f7e 100644 --- a/src/python_client/test/test_pac_api.py +++ b/src/python_client/test/test_pac_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_get.py b/src/python_client/test/test_pac_get.py index 0d6e50c9..241ad784 100644 --- a/src/python_client/test/test_pac_get.py +++ b/src/python_client/test/test_pac_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_post.py b/src/python_client/test/test_pac_post.py index 88169f60..0441f4e5 100644 --- a/src/python_client/test/test_pac_post.py +++ b/src/python_client/test/test_pac_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_response_get.py b/src/python_client/test/test_pac_response_get.py index d45e40ea..d5e61d08 100644 --- a/src/python_client/test/test_pac_response_get.py +++ b/src/python_client/test/test_pac_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_response_post.py b/src/python_client/test/test_pac_response_post.py index 858b553d..904eca64 100644 --- a/src/python_client/test/test_pac_response_post.py +++ b/src/python_client/test/test_pac_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_api.py b/src/python_client/test/test_poam_api.py index 3fc5e13f..f5ed8eb5 100644 --- a/src/python_client/test/test_poam_api.py +++ b/src/python_client/test/test_poam_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_get.py b/src/python_client/test/test_poam_get.py index d7156069..62d70d53 100644 --- a/src/python_client/test/test_poam_get.py +++ b/src/python_client/test/test_poam_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_post_put_del.py b/src/python_client/test/test_poam_post_put_del.py index ea686812..2180fdaa 100644 --- a/src/python_client/test/test_poam_post_put_del.py +++ b/src/python_client/test/test_poam_post_put_del.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_request_delete_body_inner.py b/src/python_client/test/test_poam_request_delete_body_inner.py index e4202321..83d4ed23 100644 --- a/src/python_client/test/test_poam_request_delete_body_inner.py +++ b/src/python_client/test/test_poam_request_delete_body_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_delete.py b/src/python_client/test/test_poam_response_delete.py index 1e4d9c05..696cff30 100644 --- a/src/python_client/test/test_poam_response_delete.py +++ b/src/python_client/test/test_poam_response_delete.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_get_poams.py b/src/python_client/test/test_poam_response_get_poams.py index 302762ed..b7ba1f6d 100644 --- a/src/python_client/test/test_poam_response_get_poams.py +++ b/src/python_client/test/test_poam_response_get_poams.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_get_systems.py b/src/python_client/test/test_poam_response_get_systems.py index f51d108b..bfd7d8a2 100644 --- a/src/python_client/test/test_poam_response_get_systems.py +++ b/src/python_client/test/test_poam_response_get_systems.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_post.py b/src/python_client/test/test_poam_response_post.py index 7f3acb67..ad97d603 100644 --- a/src/python_client/test/test_poam_response_post.py +++ b/src/python_client/test/test_poam_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_put.py b/src/python_client/test/test_poam_response_put.py index b8084496..9b8c899b 100644 --- a/src/python_client/test/test_poam_response_put.py +++ b/src/python_client/test/test_poam_response_put.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register.py b/src/python_client/test/test_register.py index 1d922fcb..45d7ae81 100644 --- a/src/python_client/test/test_register.py +++ b/src/python_client/test/test_register.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register_data.py b/src/python_client/test/test_register_data.py index 2c4c8575..20894e7b 100644 --- a/src/python_client/test/test_register_data.py +++ b/src/python_client/test/test_register_data.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register_user_request_post_body.py b/src/python_client/test/test_register_user_request_post_body.py index 67e5fe7a..9a2e59ba 100644 --- a/src/python_client/test/test_register_user_request_post_body.py +++ b/src/python_client/test/test_register_user_request_post_body.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_registration_api.py b/src/python_client/test/test_registration_api.py index de63503c..701b19c1 100644 --- a/src/python_client/test/test_registration_api.py +++ b/src/python_client/test/test_registration_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response200.py b/src/python_client/test/test_response200.py index e676ed24..2c7585f6 100644 --- a/src/python_client/test/test_response200.py +++ b/src/python_client/test/test_response200.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response201.py b/src/python_client/test/test_response201.py index f0640d9b..a1d0a837 100644 --- a/src/python_client/test/test_response201.py +++ b/src/python_client/test/test_response201.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response201_meta.py b/src/python_client/test/test_response201_meta.py index c674c30f..c900af2c 100644 --- a/src/python_client/test/test_response201_meta.py +++ b/src/python_client/test/test_response201_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response400.py b/src/python_client/test/test_response400.py index 69ae3172..0ecb31f2 100644 --- a/src/python_client/test/test_response400.py +++ b/src/python_client/test/test_response400.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response400_meta.py b/src/python_client/test/test_response400_meta.py index bebebf35..b0c321fe 100644 --- a/src/python_client/test/test_response400_meta.py +++ b/src/python_client/test/test_response400_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response401.py b/src/python_client/test/test_response401.py index 1081671a..556964b2 100644 --- a/src/python_client/test/test_response401.py +++ b/src/python_client/test/test_response401.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response401_meta.py b/src/python_client/test/test_response401_meta.py index 4901a305..578f1563 100644 --- a/src/python_client/test/test_response401_meta.py +++ b/src/python_client/test/test_response401_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response403.py b/src/python_client/test/test_response403.py index 2f7383f3..dd6bbfae 100644 --- a/src/python_client/test/test_response403.py +++ b/src/python_client/test/test_response403.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response403_meta.py b/src/python_client/test/test_response403_meta.py index 36fa1ee8..8606f106 100644 --- a/src/python_client/test/test_response403_meta.py +++ b/src/python_client/test/test_response403_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response404.py b/src/python_client/test/test_response404.py index d1b385b1..50421359 100644 --- a/src/python_client/test/test_response404.py +++ b/src/python_client/test/test_response404.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response405.py b/src/python_client/test/test_response405.py index 23b87cd2..3702b2db 100644 --- a/src/python_client/test/test_response405.py +++ b/src/python_client/test/test_response405.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response405_meta.py b/src/python_client/test/test_response405_meta.py index 1a4815f3..c5aed94a 100644 --- a/src/python_client/test/test_response405_meta.py +++ b/src/python_client/test/test_response405_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response411.py b/src/python_client/test/test_response411.py index 9291fc6c..00979f99 100644 --- a/src/python_client/test/test_response411.py +++ b/src/python_client/test/test_response411.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response411_meta.py b/src/python_client/test/test_response411_meta.py index 97f7f603..9ad37563 100644 --- a/src/python_client/test/test_response411_meta.py +++ b/src/python_client/test/test_response411_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response490.py b/src/python_client/test/test_response490.py index 4d42faea..80c02c07 100644 --- a/src/python_client/test/test_response490.py +++ b/src/python_client/test/test_response490.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response490_meta.py b/src/python_client/test/test_response490_meta.py index 8276bbb2..78af72a2 100644 --- a/src/python_client/test/test_response490_meta.py +++ b/src/python_client/test/test_response490_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response500.py b/src/python_client/test/test_response500.py index d5934b8f..50fac797 100644 --- a/src/python_client/test/test_response500.py +++ b/src/python_client/test/test_response500.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response500_meta.py b/src/python_client/test/test_response500_meta.py index e45d6883..3724b8f2 100644 --- a/src/python_client/test/test_response500_meta.py +++ b/src/python_client/test/test_response500_meta.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_role_category.py b/src/python_client/test/test_role_category.py index cb2784c1..b0f18f68 100644 --- a/src/python_client/test/test_role_category.py +++ b/src/python_client/test/test_role_category.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_roles.py b/src/python_client/test/test_roles.py index 973240e2..44901cb3 100644 --- a/src/python_client/test/test_roles.py +++ b/src/python_client/test/test_roles.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_ssps.py b/src/python_client/test/test_ssps.py index 4b84c2da..42507852 100644 --- a/src/python_client/test/test_ssps.py +++ b/src/python_client/test/test_ssps.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_stage.py b/src/python_client/test/test_stage.py index ad161f14..dd54cf40 100644 --- a/src/python_client/test/test_stage.py +++ b/src/python_client/test/test_stage.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_application.py b/src/python_client/test/test_static_code_application.py index a5266c7c..13109f34 100644 --- a/src/python_client/test/test_static_code_application.py +++ b/src/python_client/test/test_static_code_application.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_post.py b/src/python_client/test/test_static_code_post.py index 6e2580f9..362c28da 100644 --- a/src/python_client/test/test_static_code_post.py +++ b/src/python_client/test/test_static_code_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_request_post_body.py b/src/python_client/test/test_static_code_request_post_body.py index 52f11871..215f1d24 100644 --- a/src/python_client/test/test_static_code_request_post_body.py +++ b/src/python_client/test/test_static_code_request_post_body.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_request_post_body_application.py b/src/python_client/test/test_static_code_request_post_body_application.py index be598e7d..c80d7389 100644 --- a/src/python_client/test/test_static_code_request_post_body_application.py +++ b/src/python_client/test/test_static_code_request_post_body_application.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_response_post.py b/src/python_client/test/test_static_code_response_post.py index fc84c31d..64f399f1 100644 --- a/src/python_client/test/test_static_code_response_post.py +++ b/src/python_client/test/test_static_code_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_scans_api.py b/src/python_client/test/test_static_code_scans_api.py index 42d6ce98..410ee106 100644 --- a/src/python_client/test/test_static_code_scans_api.py +++ b/src/python_client/test/test_static_code_scans_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_success200_response.py b/src/python_client/test/test_success200_response.py index 6340f664..6ed1245a 100644 --- a/src/python_client/test/test_success200_response.py +++ b/src/python_client/test/test_success200_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_success200_response_data_inner.py b/src/python_client/test/test_success200_response_data_inner.py index 1395533b..7d68d16e 100644 --- a/src/python_client/test/test_success200_response_data_inner.py +++ b/src/python_client/test/test_success200_response_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_response.py b/src/python_client/test/test_system_response.py index b87622ac..897832dc 100644 --- a/src/python_client/test/test_system_response.py +++ b/src/python_client/test/test_system_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -106,7 +106,7 @@ def make_instance(self, include_optional): ditpr_id = '30498', apms_id = '30498', vasi_id = '30498', - authorization_status = '', + authorization_status = 'Not Yet Authorized', authorization_date = 1638741660, authorization_termination_date = 1638741660, authorization_length = 365, @@ -172,6 +172,8 @@ def make_instance(self, include_optional): atc_termination_date = 1638741660, system_development_life_cycle = 'Test Other Service', is_fisma_reportable = False, + group_tagging = 'Group Tag 1', + group_tag_descriptions = 'Group Tag 1 explanation', package = [ emass_client.models.pac___return_query_from_the_server_for_the_get_call.PAC - return query from the server for the GET call( system_id = 35, diff --git a/src/python_client/test/test_system_roles_api.py b/src/python_client/test/test_system_roles_api.py index 99437495..541afeba 100644 --- a/src/python_client/test/test_system_roles_api.py +++ b/src/python_client/test/test_system_roles_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_category_response.py b/src/python_client/test/test_system_roles_category_response.py index 6c2072b3..b11adf1e 100644 --- a/src/python_client/test/test_system_roles_category_response.py +++ b/src/python_client/test/test_system_roles_category_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_response.py b/src/python_client/test/test_system_roles_response.py index f0e71a6e..cbe12695 100644 --- a/src/python_client/test/test_system_roles_response.py +++ b/src/python_client/test/test_system_roles_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_response_data_inner.py b/src/python_client/test/test_system_roles_response_data_inner.py index 0654a809..f060d54f 100644 --- a/src/python_client/test/test_system_roles_response_data_inner.py +++ b/src/python_client/test/test_system_roles_response_data_inner.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_systems.py b/src/python_client/test/test_systems.py index 1274d562..ccb1cc31 100644 --- a/src/python_client/test/test_systems.py +++ b/src/python_client/test/test_systems.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -103,7 +103,7 @@ def make_instance(self, include_optional): ditpr_id = '30498', apms_id = '30498', vasi_id = '30498', - authorization_status = '', + authorization_status = 'Not Yet Authorized', authorization_date = 1638741660, authorization_termination_date = 1638741660, authorization_length = 365, @@ -169,6 +169,8 @@ def make_instance(self, include_optional): atc_termination_date = 1638741660, system_development_life_cycle = 'Test Other Service', is_fisma_reportable = False, + group_tagging = 'Group Tag 1', + group_tag_descriptions = 'Group Tag 1 explanation', package = [ emass_client.models.pac___return_query_from_the_server_for_the_get_call.PAC - return query from the server for the GET call( system_id = 35, diff --git a/src/python_client/test/test_systems_api.py b/src/python_client/test/test_systems_api.py index d3812896..639bfb40 100644 --- a/src/python_client/test/test_systems_api.py +++ b/src/python_client/test/test_systems_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_systems_response.py b/src/python_client/test/test_systems_response.py index 76cd7549..a36cceaf 100644 --- a/src/python_client/test/test_systems_response.py +++ b/src/python_client/test/test_systems_response.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -107,7 +107,7 @@ def make_instance(self, include_optional): ditpr_id = '30498', apms_id = '30498', vasi_id = '30498', - authorization_status = '', + authorization_status = 'Not Yet Authorized', authorization_date = 1638741660, authorization_termination_date = 1638741660, authorization_length = 365, @@ -173,6 +173,8 @@ def make_instance(self, include_optional): atc_termination_date = 1638741660, system_development_life_cycle = 'Test Other Service', is_fisma_reportable = False, + group_tagging = 'Group Tag 1', + group_tag_descriptions = 'Group Tag 1 explanation', package = [ emass_client.models.pac___return_query_from_the_server_for_the_get_call.PAC - return query from the server for the GET call( system_id = 35, diff --git a/src/python_client/test/test_test.py b/src/python_client/test/test_test.py index 6427f0f5..ac16ae90 100644 --- a/src/python_client/test/test_test.py +++ b/src/python_client/test/test_test.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_api.py b/src/python_client/test/test_test_api.py index d42d681d..d9070165 100644 --- a/src/python_client/test/test_test_api.py +++ b/src/python_client/test/test_test_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_data.py b/src/python_client/test/test_test_data.py index 7d1a5896..ebd0daee 100644 --- a/src/python_client/test/test_test_data.py +++ b/src/python_client/test/test_test_data.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_api.py b/src/python_client/test/test_test_results_api.py index 7e2d19df..fa9bbb1d 100644 --- a/src/python_client/test/test_test_results_api.py +++ b/src/python_client/test/test_test_results_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_get.py b/src/python_client/test/test_test_results_get.py index 5d8f2ae9..78954bc5 100644 --- a/src/python_client/test/test_test_results_get.py +++ b/src/python_client/test/test_test_results_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_post.py b/src/python_client/test/test_test_results_post.py index 072cf02d..fda764ba 100644 --- a/src/python_client/test/test_test_results_post.py +++ b/src/python_client/test/test_test_results_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_response_get.py b/src/python_client/test/test_test_results_response_get.py index d7c85713..9ac5c360 100644 --- a/src/python_client/test/test_test_results_response_get.py +++ b/src/python_client/test/test_test_results_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_response_post.py b/src/python_client/test/test_test_results_response_post.py index f640186b..41518e20 100644 --- a/src/python_client/test/test_test_results_response_post.py +++ b/src/python_client/test/test_test_results_response_post.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_users.py b/src/python_client/test/test_users.py index 5d0b0b3f..06e85487 100644 --- a/src/python_client/test/test_users.py +++ b/src/python_client/test/test_users.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definition_get.py b/src/python_client/test/test_workflow_definition_get.py index eb6646ad..2e1e60a3 100644 --- a/src/python_client/test/test_workflow_definition_get.py +++ b/src/python_client/test/test_workflow_definition_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definition_response_get.py b/src/python_client/test/test_workflow_definition_response_get.py index 7af20aba..3890205d 100644 --- a/src/python_client/test/test_workflow_definition_response_get.py +++ b/src/python_client/test/test_workflow_definition_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definitions_api.py b/src/python_client/test/test_workflow_definitions_api.py index e70037fb..2a4688c7 100644 --- a/src/python_client/test/test_workflow_definitions_api.py +++ b/src/python_client/test/test_workflow_definitions_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instance_get.py b/src/python_client/test/test_workflow_instance_get.py index 1a69d0b4..136f1a1e 100644 --- a/src/python_client/test/test_workflow_instance_get.py +++ b/src/python_client/test/test_workflow_instance_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instance_response_get.py b/src/python_client/test/test_workflow_instance_response_get.py index 8114f4a8..af5b6c84 100644 --- a/src/python_client/test/test_workflow_instance_response_get.py +++ b/src/python_client/test/test_workflow_instance_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. @@ -77,28 +77,26 @@ def make_instance(self, include_optional): return WorkflowInstanceResponseGet( meta = emass_client.models.ok.OK( code = 200, ), - data = [ - emass_client.models.workflow_instances___return_query_for_the_get_workflow_instance_by_id.Workflow Instances - return query for the GET workflow instance by ID( - workflow_uid = '6f810301-5b3b-4f89-81e7-587fef9142a9', - system_name = 'Test system 1', - workflow_instance_id = 35, - package_name = 'Test RMF Step 1 package', - created_date = 1636124623, - last_edited_date = 1631130837, - last_edited_by = 'john.doe.ctr@mail.mil', - workflow = 'RMF Step 1: Security Category', - version = '4', - current_stage = 'Echelon II', - transitions = [ - emass_client.models.workflow_instances_transition.Workflow Instances Transition( - comments = 'Approved the categorization', - created_by = 'john.doe.ctr@mail.mil', - created_date = 1636124623, - description = 'Submit New Package', - end_stage = 'Submit Categorization', - start_stage = 'Not Started', ) - ], ) - ] + data = emass_client.models.workflow_instances___return_query_for_the_get_workflow_instance_by_id.Workflow Instances - return query for the GET workflow instance by ID( + workflow_uid = '6f810301-5b3b-4f89-81e7-587fef9142a9', + system_name = 'Test system 1', + workflow_instance_id = 35, + package_name = 'Test RMF Step 1 package', + created_date = 1636124623, + last_edited_date = 1631130837, + last_edited_by = 'john.doe.ctr@mail.mil', + workflow = 'RMF Step 1: Security Category', + version = '4', + current_stage = 'Echelon II', + transitions = [ + emass_client.models.workflow_instances_transition.Workflow Instances Transition( + comments = 'Approved the categorization', + created_by = 'john.doe.ctr@mail.mil', + created_date = 1636124623, + description = 'Submit New Package', + end_stage = 'Submit Categorization', + start_stage = 'Not Started', ) + ], ) ) else : return WorkflowInstanceResponseGet( diff --git a/src/python_client/test/test_workflow_instances_api.py b/src/python_client/test/test_workflow_instances_api.py index 7d7fe795..3219a1a5 100644 --- a/src/python_client/test/test_workflow_instances_api.py +++ b/src/python_client/test/test_workflow_instances_api.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_get.py b/src/python_client/test/test_workflow_instances_get.py index f33bf9db..580b52b5 100644 --- a/src/python_client/test/test_workflow_instances_get.py +++ b/src/python_client/test/test_workflow_instances_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_response_get.py b/src/python_client/test/test_workflow_instances_response_get.py index 21f2d480..aba34fe5 100644 --- a/src/python_client/test/test_workflow_instances_response_get.py +++ b/src/python_client/test/test_workflow_instances_response_get.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_response_get_pagination.py b/src/python_client/test/test_workflow_instances_response_get_pagination.py index 9cff223c..fefdf412 100644 --- a/src/python_client/test/test_workflow_instances_response_get_pagination.py +++ b/src/python_client/test/test_workflow_instances_response_get_pagination.py @@ -1,6 +1,6 @@ # coding: utf-8 -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification The emass_client_api is a Python client that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications. @@ -8,9 +8,9 @@ This Python package was generated from the eMASS API specification: -- API version: v3.9 -- Package version: 3.9.1 -- Build date: 2023-05-23T01:07:18.461999Z[Etc/UTC] +- API version: v3.10 +- Package version: 3.10.0 +- Build date: 2023-06-13T13:46:18.843637Z[Etc/UTC] ## Requirements. diff --git a/src/ruby_client/.openapi-generator/FILES b/src/ruby_client/.openapi-generator/FILES index 1d06a81e..31a5f52a 100644 --- a/src/ruby_client/.openapi-generator/FILES +++ b/src/ruby_client/.openapi-generator/FILES @@ -36,6 +36,8 @@ docs/ControlsGet.md docs/ControlsPut.md docs/ControlsResponseGet.md docs/ControlsResponsePut.md +docs/DashboardMockResponse.md +docs/DashboardMockResponsePagination.md docs/DashboardsApi.md docs/DefinitionTransitions.md docs/InstancesTransitions.md @@ -49,6 +51,7 @@ docs/MilestonesPutPostDelete.md docs/MilestonesRequestDeleteBodyInner.md docs/MilestonesRequiredPost.md docs/MilestonesRequiredPut.md +docs/MockObject.md docs/PACApi.md docs/POAMApi.md docs/PacGet.md @@ -170,6 +173,8 @@ lib/emass_client/models/controls_get.rb lib/emass_client/models/controls_put.rb lib/emass_client/models/controls_response_get.rb lib/emass_client/models/controls_response_put.rb +lib/emass_client/models/dashboard_mock_response.rb +lib/emass_client/models/dashboard_mock_response_pagination.rb lib/emass_client/models/definition_transitions.rb lib/emass_client/models/instances_transitions.rb lib/emass_client/models/milestone_response_get.rb @@ -181,6 +186,7 @@ lib/emass_client/models/milestones_put_post_delete.rb lib/emass_client/models/milestones_request_delete_body_inner.rb lib/emass_client/models/milestones_required_post.rb lib/emass_client/models/milestones_required_put.rb +lib/emass_client/models/mock_object.rb lib/emass_client/models/pac_get.rb lib/emass_client/models/pac_post.rb lib/emass_client/models/pac_response_get.rb @@ -289,6 +295,8 @@ spec/models/controls_get_spec.rb spec/models/controls_put_spec.rb spec/models/controls_response_get_spec.rb spec/models/controls_response_put_spec.rb +spec/models/dashboard_mock_response_pagination_spec.rb +spec/models/dashboard_mock_response_spec.rb spec/models/definition_transitions_spec.rb spec/models/instances_transitions_spec.rb spec/models/milestone_response_get_milestone_spec.rb @@ -300,6 +308,7 @@ spec/models/milestones_put_post_delete_spec.rb spec/models/milestones_request_delete_body_inner_spec.rb spec/models/milestones_required_post_spec.rb spec/models/milestones_required_put_spec.rb +spec/models/mock_object_spec.rb spec/models/pac_get_spec.rb spec/models/pac_post_spec.rb spec/models/pac_response_get_spec.rb diff --git a/src/ruby_client/.travis.yml b/src/ruby_client/.travis.yml index e96b8217..2a203b0d 100644 --- a/src/ruby_client/.travis.yml +++ b/src/ruby_client/.travis.yml @@ -8,4 +8,4 @@ script: - bundle install --path vendor/bundle - bundle exec rspec - gem build emass_client.gemspec - - gem install ./emass_client-3.9.1.gem + - gem install ./emass_client-3.9.10.gem diff --git a/src/ruby_client/README.md b/src/ruby_client/README.md index 7ab916ba..3247000c 100644 --- a/src/ruby_client/README.md +++ b/src/ruby_client/README.md @@ -53,8 +53,8 @@ To establish an account with eMASS and/or acquire an api-key/user-uid, contact o This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project: -- API version: v3.9 -- Package version: 3.9.1 +- API version: v3.10 +- Package version: 3.9.10 - Build package: org.openapitools.codegen.languages.RubyClientCodegen For more information, please visit [https://www.dcsa.mil/is/emass/](https://www.dcsa.mil/is/emass/) @@ -71,16 +71,16 @@ gem build emass_client.gemspec Then either install the gem locally: ```shell -gem install ./emass_client-3.9.1.gem +gem install ./emass_client-3.9.10.gem ``` -(for development, run `gem install --dev ./emass_client-3.9.1.gem` to install the development dependencies) +(for development, run `gem install --dev ./emass_client-3.9.10.gem` to install the development dependencies) or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/). Finally add this to the Gemfile: - gem 'emass_client', '~> 3.9.1' + gem 'emass_client', '~> 3.9.10' ### Install from Git @@ -160,32 +160,35 @@ Class | Method | HTTP request | Description *EmassClient::ContainerScanResultsApi* | [**add_container_sans_by_system_id**](docs/ContainerScanResultsApi.md#add_container_sans_by_system_id) | **POST** /api/systems/{systemId}/container-scan-results | Add one or many containers and their scan results *EmassClient::ControlsApi* | [**get_system_controls**](docs/ControlsApi.md#get_system_controls) | **GET** /api/systems/{systemId}/controls | Get control information in a system for one or many controls *EmassClient::ControlsApi* | [**update_control_by_system_id**](docs/ControlsApi.md#update_control_by_system_id) | **PUT** /api/systems/{systemId}/controls | Update control information in a system for one or many controls -*EmassClient::DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | Get dashboard information -*EmassClient::DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | Get dashboard information +*EmassClient::DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | System Artifacts Details +*EmassClient::DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | System Artifacts Summary +*EmassClient::DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | System Assessment Procedures Details +*EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | System Associations Details +*EmassClient::DashboardsApi* | [**get_system_common_integration_status_summary**](docs/DashboardsApi.md#get_system_common_integration_status_summary) | **GET** /api/dashboards/system-conmon-integration-status-summary | System CONMON Integration Status +*EmassClient::DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | System Control Compliance Summary +*EmassClient::DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | System Hardware Details +*EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | System Hardware Summary +*EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | System POA&M Details +*EmassClient::DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | System POA&M Summary +*EmassClient::DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | System Ports/Protocols Details +*EmassClient::DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | System Ports/Protocols Summary +*EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | System Privacy Summary +*EmassClient::DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | System Control Compliance Details +*EmassClient::DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | System Sensor Hardware Details +*EmassClient::DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | System Sensor Hardware Summary +*EmassClient::DashboardsApi* | [**get_system_software_details**](docs/DashboardsApi.md#get_system_software_details) | **GET** /api/dashboards/system-software-details | System Software Details +*EmassClient::DashboardsApi* | [**get_system_software_summary**](docs/DashboardsApi.md#get_system_software_summary) | **GET** /api/dashboards/system-software-summary | System Software Summary +*EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | System Status Details +*EmassClient::DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | User System Assignments Details +*EmassClient::DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | VA OMB FISMA SAOP Summary +*EmassClient::DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | VA System A2.0 Summary +*EmassClient::DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | VA System A&A Summary +*EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | VA System FISMA Inventory Crypto Summary +*EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | VA System FISMA Inventory Summary +*EmassClient::DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | VA System P.L. 109 Reporting Summary +*EmassClient::DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | VA System Threat Architecture Details +*EmassClient::DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | VA System Threat Risks Summary +*EmassClient::DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | VA System Threat Sources Details *EmassClient::MilestonesApi* | [**add_milestone_by_system_id_and_poam_id**](docs/MilestonesApi.md#add_milestone_by_system_id_and_poam_id) | **POST** /api/systems/{systemId}/poams/{poamId}/milestones | Add milestones to one or many POA&M items in a system *EmassClient::MilestonesApi* | [**delete_milestone**](docs/MilestonesApi.md#delete_milestone) | **DELETE** /api/systems/{systemId}/poams/{poamId}/milestones | Remove milestones in a system for one or many POA&M items *EmassClient::MilestonesApi* | [**get_system_milestones_by_poam_id**](docs/MilestonesApi.md#get_system_milestones_by_poam_id) | **GET** /api/systems/{systemId}/poams/{poamId}/milestones | Get milestones in one or many POA&M items in a system @@ -236,6 +239,8 @@ Class | Method | HTTP request | Description - [EmassClient::ControlsPut](docs/ControlsPut.md) - [EmassClient::ControlsResponseGet](docs/ControlsResponseGet.md) - [EmassClient::ControlsResponsePut](docs/ControlsResponsePut.md) + - [EmassClient::DashboardMockResponse](docs/DashboardMockResponse.md) + - [EmassClient::DashboardMockResponsePagination](docs/DashboardMockResponsePagination.md) - [EmassClient::DefinitionTransitions](docs/DefinitionTransitions.md) - [EmassClient::InstancesTransitions](docs/InstancesTransitions.md) - [EmassClient::MilestoneResponseGet](docs/MilestoneResponseGet.md) @@ -247,6 +252,7 @@ Class | Method | HTTP request | Description - [EmassClient::MilestonesRequestDeleteBodyInner](docs/MilestonesRequestDeleteBodyInner.md) - [EmassClient::MilestonesRequiredPost](docs/MilestonesRequiredPost.md) - [EmassClient::MilestonesRequiredPut](docs/MilestonesRequiredPut.md) + - [EmassClient::MockObject](docs/MockObject.md) - [EmassClient::PacGet](docs/PacGet.md) - [EmassClient::PacPost](docs/PacPost.md) - [EmassClient::PacResponseGet](docs/PacResponseGet.md) diff --git a/src/ruby_client/docs/DashboardMockResponse.md b/src/ruby_client/docs/DashboardMockResponse.md new file mode 100644 index 00000000..5a662550 --- /dev/null +++ b/src/ruby_client/docs/DashboardMockResponse.md @@ -0,0 +1,22 @@ +# EmassClient::DashboardMockResponse + +## Properties + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **meta** | [**Response200**](Response200.md) | | [optional] | +| **data** | [**Array<MockObject>**](MockObject.md) | | [optional] | +| **pagination** | [**DashboardMockResponsePagination**](DashboardMockResponsePagination.md) | | [optional] | + +## Example + +```ruby +require 'emass_client' + +instance = EmassClient::DashboardMockResponse.new( + meta: null, + data: null, + pagination: null +) +``` + diff --git a/src/ruby_client/docs/DashboardMockResponsePagination.md b/src/ruby_client/docs/DashboardMockResponsePagination.md new file mode 100644 index 00000000..0b9c62fa --- /dev/null +++ b/src/ruby_client/docs/DashboardMockResponsePagination.md @@ -0,0 +1,28 @@ +# EmassClient::DashboardMockResponsePagination + +## Properties + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **total_count** | **Integer** | | [optional] | +| **total_pages** | **Integer** | | [optional] | +| **page_index** | **Integer** | | [optional] | +| **page_size** | **Integer** | | [optional] | +| **prev_page_url** | **String** | | [optional] | +| **next_page_url** | **String** | | [optional] | + +## Example + +```ruby +require 'emass_client' + +instance = EmassClient::DashboardMockResponsePagination.new( + total_count: 2, + total_pages: 1, + page_index: 2, + page_size: 20000, + prev_page_url: https://myfakeurl.reponse.page.com?PreviousPage, + next_page_url: https://myfakeurl.reponse.page.com?NextPage +) +``` + diff --git a/src/ruby_client/docs/DashboardsApi.md b/src/ruby_client/docs/DashboardsApi.md index 8246ca0b..16ba4461 100644 --- a/src/ruby_client/docs/DashboardsApi.md +++ b/src/ruby_client/docs/DashboardsApi.md @@ -4,39 +4,42 @@ All URIs are relative to *http://localhost:4010* | Method | HTTP request | Description | | ------ | ------------ | ----------- | -| [**get_system_artifacts_details**](DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | Get dashboard information | -| [**get_system_artifacts_summary**](DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | Get dashboard information | -| [**get_system_assessment_procedures_details**](DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information | -| [**get_system_associations_details**](DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information | -| [**get_system_control_compliance_summary**](DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information | -| [**get_system_hardware_details**](DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information | -| [**get_system_hardware_summary**](DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information | -| [**get_system_poam_details**](DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information | -| [**get_system_poam_summary**](DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information | -| [**get_system_ports_protocols_details**](DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | Get dashboard information | -| [**get_system_ports_protocols_summary**](DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | Get dashboard information | -| [**get_system_privacy_summary**](DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information | -| [**get_system_security_control_details**](DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information | -| [**get_system_sensor_hardware_details**](DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | Get dashboard information | -| [**get_system_sensor_hardware_summary**](DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | Get dashboard information | -| [**get_system_status_details**](DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information | -| [**get_user_system_assignments_details**](DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information | -| [**get_va_omb_fsma_saop_summary**](DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information | -| [**get_va_system_a2_summary**](DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information | -| [**get_va_system_aa_summary**](DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information | -| [**get_va_system_fisma_invetory_crypto_summary**](DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | Get dashboard information | -| [**get_va_system_fisma_invetory_summary**](DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information | -| [**get_va_system_pl109_reporting_summary**](DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information | -| [**get_va_system_threat_architecture_details**](DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | Get dashboard information | -| [**get_va_system_threat_risk_summary**](DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | Get dashboard information | -| [**get_va_system_threat_source_details**](DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | Get dashboard information | +| [**get_system_artifacts_details**](DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | System Artifacts Details | +| [**get_system_artifacts_summary**](DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | System Artifacts Summary | +| [**get_system_assessment_procedures_details**](DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | System Assessment Procedures Details | +| [**get_system_associations_details**](DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | System Associations Details | +| [**get_system_common_integration_status_summary**](DashboardsApi.md#get_system_common_integration_status_summary) | **GET** /api/dashboards/system-conmon-integration-status-summary | System CONMON Integration Status | +| [**get_system_control_compliance_summary**](DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | System Control Compliance Summary | +| [**get_system_hardware_details**](DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | System Hardware Details | +| [**get_system_hardware_summary**](DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | System Hardware Summary | +| [**get_system_poam_details**](DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | System POA&M Details | +| [**get_system_poam_summary**](DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | System POA&M Summary | +| [**get_system_ports_protocols_details**](DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | System Ports/Protocols Details | +| [**get_system_ports_protocols_summary**](DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | System Ports/Protocols Summary | +| [**get_system_privacy_summary**](DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | System Privacy Summary | +| [**get_system_security_control_details**](DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | System Control Compliance Details | +| [**get_system_sensor_hardware_details**](DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | System Sensor Hardware Details | +| [**get_system_sensor_hardware_summary**](DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | System Sensor Hardware Summary | +| [**get_system_software_details**](DashboardsApi.md#get_system_software_details) | **GET** /api/dashboards/system-software-details | System Software Details | +| [**get_system_software_summary**](DashboardsApi.md#get_system_software_summary) | **GET** /api/dashboards/system-software-summary | System Software Summary | +| [**get_system_status_details**](DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | System Status Details | +| [**get_user_system_assignments_details**](DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | User System Assignments Details | +| [**get_va_omb_fsma_saop_summary**](DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | VA OMB FISMA SAOP Summary | +| [**get_va_system_a2_summary**](DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | VA System A2.0 Summary | +| [**get_va_system_aa_summary**](DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | VA System A&A Summary | +| [**get_va_system_fisma_invetory_crypto_summary**](DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | VA System FISMA Inventory Crypto Summary | +| [**get_va_system_fisma_invetory_summary**](DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | VA System FISMA Inventory Summary | +| [**get_va_system_pl109_reporting_summary**](DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | VA System P.L. 109 Reporting Summary | +| [**get_va_system_threat_architecture_details**](DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | VA System Threat Architecture Details | +| [**get_va_system_threat_risk_summary**](DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | VA System Threat Risks Summary | +| [**get_va_system_threat_source_details**](DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | VA System Threat Sources Details | ## get_system_artifacts_details > Object get_system_artifacts_details(org_id, opts) -Get dashboard information +System Artifacts Details Get system Artifacts details information. @@ -72,7 +75,7 @@ opts = { } begin - # Get dashboard information + # System Artifacts Details result = api_instance.get_system_artifacts_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -88,7 +91,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Artifacts Details data, status_code, headers = api_instance.get_system_artifacts_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -125,7 +128,7 @@ end > Object get_system_artifacts_summary(org_id, opts) -Get dashboard information +System Artifacts Summary Get system Artifacts summary information. @@ -161,7 +164,7 @@ opts = { } begin - # Get dashboard information + # System Artifacts Summary result = api_instance.get_system_artifacts_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -177,7 +180,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Artifacts Summary data, status_code, headers = api_instance.get_system_artifacts_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -214,7 +217,7 @@ end > Object get_system_assessment_procedures_details(org_id, opts) -Get dashboard information +System Assessment Procedures Details Get systems assessement procdures details dashboard information. @@ -250,7 +253,7 @@ opts = { } begin - # Get dashboard information + # System Assessment Procedures Details result = api_instance.get_system_assessment_procedures_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -266,7 +269,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Assessment Procedures Details data, status_code, headers = api_instance.get_system_assessment_procedures_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -303,7 +306,7 @@ end > Object get_system_associations_details(org_id, opts) -Get dashboard information +System Associations Details Get system associations details dashboard information. @@ -339,7 +342,7 @@ opts = { } begin - # Get dashboard information + # System Associations Details result = api_instance.get_system_associations_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -355,7 +358,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Associations Details data, status_code, headers = api_instance.get_system_associations_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -388,11 +391,100 @@ end - **Accept**: application/json +## get_system_common_integration_status_summary + +> Object get_system_common_integration_status_summary(org_id, opts) + +System CONMON Integration Status + +Get system CONMON integration status dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + excludeinherited: true, # Boolean | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # System CONMON Integration Status + result = api_instance.get_system_common_integration_status_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_common_integration_status_summary: #{e}" +end +``` + +#### Using the get_system_common_integration_status_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_common_integration_status_summary_with_http_info(org_id, opts) + +```ruby +begin + # System CONMON Integration Status + data, status_code, headers = api_instance.get_system_common_integration_status_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_common_integration_status_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **excludeinherited** | **Boolean** | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional][default to false] | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + ## get_system_control_compliance_summary > Object get_system_control_compliance_summary(org_id, opts) -Get dashboard information +System Control Compliance Summary Get systems control compliance summary dashboard information. @@ -428,7 +520,7 @@ opts = { } begin - # Get dashboard information + # System Control Compliance Summary result = api_instance.get_system_control_compliance_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -444,7 +536,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Control Compliance Summary data, status_code, headers = api_instance.get_system_control_compliance_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -481,7 +573,7 @@ end > Object get_system_hardware_details(org_id, opts) -Get dashboard information +System Hardware Details Get system hardware details dashboard information. @@ -517,7 +609,7 @@ opts = { } begin - # Get dashboard information + # System Hardware Details result = api_instance.get_system_hardware_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -533,7 +625,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Hardware Details data, status_code, headers = api_instance.get_system_hardware_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -570,7 +662,7 @@ end > Object get_system_hardware_summary(org_id, opts) -Get dashboard information +System Hardware Summary Get system hardware summary dashboard information. @@ -606,7 +698,7 @@ opts = { } begin - # Get dashboard information + # System Hardware Summary result = api_instance.get_system_hardware_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -622,7 +714,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Hardware Summary data, status_code, headers = api_instance.get_system_hardware_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -659,7 +751,7 @@ end > Object get_system_poam_details(org_id, opts) -Get dashboard information +System POA&M Details Get system POA&Ms details dashboard information. @@ -695,7 +787,7 @@ opts = { } begin - # Get dashboard information + # System POA&M Details result = api_instance.get_system_poam_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -711,7 +803,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System POA&M Details data, status_code, headers = api_instance.get_system_poam_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -748,7 +840,7 @@ end > Object get_system_poam_summary(org_id, opts) -Get dashboard information +System POA&M Summary Get systems POA&Ms summary dashboard information. @@ -784,7 +876,7 @@ opts = { } begin - # Get dashboard information + # System POA&M Summary result = api_instance.get_system_poam_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -800,7 +892,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System POA&M Summary data, status_code, headers = api_instance.get_system_poam_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -837,7 +929,7 @@ end > Object get_system_ports_protocols_details(org_id, opts) -Get dashboard information +System Ports/Protocols Details Get system ports and protocols details dashboard information. @@ -873,7 +965,7 @@ opts = { } begin - # Get dashboard information + # System Ports/Protocols Details result = api_instance.get_system_ports_protocols_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -889,7 +981,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Ports/Protocols Details data, status_code, headers = api_instance.get_system_ports_protocols_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -926,7 +1018,7 @@ end > Object get_system_ports_protocols_summary(org_id, opts) -Get dashboard information +System Ports/Protocols Summary Get system ports and protocols summary dashboard information. @@ -962,7 +1054,7 @@ opts = { } begin - # Get dashboard information + # System Ports/Protocols Summary result = api_instance.get_system_ports_protocols_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -978,7 +1070,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Ports/Protocols Summary data, status_code, headers = api_instance.get_system_ports_protocols_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1015,7 +1107,7 @@ end > Object get_system_privacy_summary(org_id, opts) -Get dashboard information +System Privacy Summary Get user system privacy summary dashboard information. @@ -1051,7 +1143,7 @@ opts = { } begin - # Get dashboard information + # System Privacy Summary result = api_instance.get_system_privacy_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1067,7 +1159,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Privacy Summary data, status_code, headers = api_instance.get_system_privacy_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1104,7 +1196,7 @@ end > Object get_system_security_control_details(org_id, opts) -Get dashboard information +System Control Compliance Details Get systems security control details dashboard information. @@ -1140,7 +1232,7 @@ opts = { } begin - # Get dashboard information + # System Control Compliance Details result = api_instance.get_system_security_control_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1156,7 +1248,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Control Compliance Details data, status_code, headers = api_instance.get_system_security_control_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1193,7 +1285,7 @@ end > Object get_system_sensor_hardware_details(org_id, opts) -Get dashboard information +System Sensor Hardware Details Get system sensor hardware details dashboard information. @@ -1229,7 +1321,7 @@ opts = { } begin - # Get dashboard information + # System Sensor Hardware Details result = api_instance.get_system_sensor_hardware_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1245,7 +1337,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Sensor Hardware Details data, status_code, headers = api_instance.get_system_sensor_hardware_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1282,7 +1374,7 @@ end > Object get_system_sensor_hardware_summary(org_id, opts) -Get dashboard information +System Sensor Hardware Summary Get system sensor hardware summary dashboard information. @@ -1318,7 +1410,7 @@ opts = { } begin - # Get dashboard information + # System Sensor Hardware Summary result = api_instance.get_system_sensor_hardware_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1334,7 +1426,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Sensor Hardware Summary data, status_code, headers = api_instance.get_system_sensor_hardware_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1367,11 +1459,189 @@ end - **Accept**: application/json +## get_system_software_details + +> Object get_system_software_details(org_id, opts) + +System Software Details + +Get system software details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + excludeinherited: true, # Boolean | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # System Software Details + result = api_instance.get_system_software_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_software_details: #{e}" +end +``` + +#### Using the get_system_software_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_software_details_with_http_info(org_id, opts) + +```ruby +begin + # System Software Details + data, status_code, headers = api_instance.get_system_software_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_software_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **excludeinherited** | **Boolean** | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional][default to false] | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_software_summary + +> Object get_system_software_summary(org_id, opts) + +System Software Summary + +Get system software summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + excludeinherited: true, # Boolean | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # System Software Summary + result = api_instance.get_system_software_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_software_summary: #{e}" +end +``` + +#### Using the get_system_software_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_software_summary_with_http_info(org_id, opts) + +```ruby +begin + # System Software Summary + data, status_code, headers = api_instance.get_system_software_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_software_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **excludeinherited** | **Boolean** | **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. | [optional][default to false] | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + ## get_system_status_details > Object get_system_status_details(org_id, opts) -Get dashboard information +System Status Details Get systems status detail dashboard information. @@ -1407,7 +1677,7 @@ opts = { } begin - # Get dashboard information + # System Status Details result = api_instance.get_system_status_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1423,7 +1693,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # System Status Details data, status_code, headers = api_instance.get_system_status_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1460,7 +1730,7 @@ end > Object get_user_system_assignments_details(org_id, opts) -Get dashboard information +User System Assignments Details Get user system assignments details dashboard information. @@ -1496,7 +1766,7 @@ opts = { } begin - # Get dashboard information + # User System Assignments Details result = api_instance.get_user_system_assignments_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1512,7 +1782,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # User System Assignments Details data, status_code, headers = api_instance.get_user_system_assignments_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1549,7 +1819,7 @@ end > Object get_va_omb_fsma_saop_summary(org_id, opts) -Get dashboard information +VA OMB FISMA SAOP Summary Get VA OMB-FISMA SAOP summary dashboard information. @@ -1585,7 +1855,7 @@ opts = { } begin - # Get dashboard information + # VA OMB FISMA SAOP Summary result = api_instance.get_va_omb_fsma_saop_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1601,7 +1871,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA OMB FISMA SAOP Summary data, status_code, headers = api_instance.get_va_omb_fsma_saop_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1638,7 +1908,7 @@ end > Object get_va_system_a2_summary(org_id, opts) -Get dashboard information +VA System A2.0 Summary Get VA system A2.0 summary dashboard information. @@ -1674,7 +1944,7 @@ opts = { } begin - # Get dashboard information + # VA System A2.0 Summary result = api_instance.get_va_system_a2_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1690,7 +1960,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System A2.0 Summary data, status_code, headers = api_instance.get_va_system_a2_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1727,7 +1997,7 @@ end > Object get_va_system_aa_summary(org_id, opts) -Get dashboard information +VA System A&A Summary Get VA system A&A summary dashboard information. @@ -1763,7 +2033,7 @@ opts = { } begin - # Get dashboard information + # VA System A&A Summary result = api_instance.get_va_system_aa_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1779,7 +2049,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System A&A Summary data, status_code, headers = api_instance.get_va_system_aa_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1816,7 +2086,7 @@ end > Object get_va_system_fisma_invetory_crypto_summary(org_id, opts) -Get dashboard information +VA System FISMA Inventory Crypto Summary Get VA system FISMA inventory crypto summary dashboard information. @@ -1852,7 +2122,7 @@ opts = { } begin - # Get dashboard information + # VA System FISMA Inventory Crypto Summary result = api_instance.get_va_system_fisma_invetory_crypto_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1868,7 +2138,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System FISMA Inventory Crypto Summary data, status_code, headers = api_instance.get_va_system_fisma_invetory_crypto_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1905,7 +2175,7 @@ end > Object get_va_system_fisma_invetory_summary(org_id, opts) -Get dashboard information +VA System FISMA Inventory Summary Get VA system FISMA inventory summary dashboard information. @@ -1941,7 +2211,7 @@ opts = { } begin - # Get dashboard information + # VA System FISMA Inventory Summary result = api_instance.get_va_system_fisma_invetory_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -1957,7 +2227,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System FISMA Inventory Summary data, status_code, headers = api_instance.get_va_system_fisma_invetory_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -1994,7 +2264,7 @@ end > Object get_va_system_pl109_reporting_summary(org_id, opts) -Get dashboard information +VA System P.L. 109 Reporting Summary Get VA system P.L. 109 reporting summary dashboard information. @@ -2030,7 +2300,7 @@ opts = { } begin - # Get dashboard information + # VA System P.L. 109 Reporting Summary result = api_instance.get_va_system_pl109_reporting_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -2046,7 +2316,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System P.L. 109 Reporting Summary data, status_code, headers = api_instance.get_va_system_pl109_reporting_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -2083,7 +2353,7 @@ end > Object get_va_system_threat_architecture_details(org_id, opts) -Get dashboard information +VA System Threat Architecture Details Get VA system threat architecture details dashboard information. @@ -2119,7 +2389,7 @@ opts = { } begin - # Get dashboard information + # VA System Threat Architecture Details result = api_instance.get_va_system_threat_architecture_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -2135,7 +2405,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System Threat Architecture Details data, status_code, headers = api_instance.get_va_system_threat_architecture_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -2172,7 +2442,7 @@ end > Object get_va_system_threat_risk_summary(org_id, opts) -Get dashboard information +VA System Threat Risks Summary Get VA system threat risk summary dashboard information. @@ -2208,7 +2478,7 @@ opts = { } begin - # Get dashboard information + # VA System Threat Risks Summary result = api_instance.get_va_system_threat_risk_summary(org_id, opts) p result rescue EmassClient::ApiError => e @@ -2224,7 +2494,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System Threat Risks Summary data, status_code, headers = api_instance.get_va_system_threat_risk_summary_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } @@ -2261,7 +2531,7 @@ end > Object get_va_system_threat_source_details(org_id, opts) -Get dashboard information +VA System Threat Sources Details Get VA system threat source details dashboard information. @@ -2297,7 +2567,7 @@ opts = { } begin - # Get dashboard information + # VA System Threat Sources Details result = api_instance.get_va_system_threat_source_details(org_id, opts) p result rescue EmassClient::ApiError => e @@ -2313,7 +2583,7 @@ This returns an Array which contains the response data, status code and headers. ```ruby begin - # Get dashboard information + # VA System Threat Sources Details data, status_code, headers = api_instance.get_va_system_threat_source_details_with_http_info(org_id, opts) p status_code # => 2xx p headers # => { ... } diff --git a/src/ruby_client/docs/MockObject.md b/src/ruby_client/docs/MockObject.md new file mode 100644 index 00000000..1be29360 --- /dev/null +++ b/src/ruby_client/docs/MockObject.md @@ -0,0 +1,42 @@ +# EmassClient::MockObject + +## Properties + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **poc_organization** | **String** | [Required] Organization/Office represented. 100 Characters. | [optional] | +| **resources** | **String** | [Required] List of resources used. 250 Characters. | [optional] | +| **owning_organization** | **String** | [Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy. | [optional] | +| **secondary_organization** | **String** | [Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level. | [optional] | +| **poc_first_name** | **String** | [Conditional] First name of POC. 100 Characters. | [optional] | +| **poc_last_name** | **String** | [Conditional] Last name of POC. 100 Characters. | [optional] | +| **poc_email** | **String** | [Conditional] Email address of POC. 100 Characters. | [optional] | +| **poc_phone_number** | **String** | [Conditional] Phone number of POC (area code) ***-**** format. 100 Characters. | [optional] | +| **severity** | **String** | [Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High) | [optional] | +| **scheduled_completion_date** | **Integer** | [Conditional] Required for ongoing and completed POA&M items. Unix time format. | [optional] | +| **completion_date** | **Integer** | [Conditional] Field is required for completed POA&M items. Unix time format. | [optional] | +| **comments** | **String** | [Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters | [optional] | +| **is_active** | **Boolean** | [Conditional] Optionally used in PUT to delete milestones when updating a POA&M. | [optional] | + +## Example + +```ruby +require 'emass_client' + +instance = EmassClient::MockObject.new( + poc_organization: Army, + resources: Resource text., + owning_organization: Defense Information Systems Agency, + secondary_organization: ID31, + poc_first_name: John, + poc_last_name: Smith, + poc_email: smith@ah.com, + poc_phone_number: 555-555-5555, + severity: Low, + scheduled_completion_date: 1599644800, + completion_date: 1505916276, + comments: Comments text., + is_active: true +) +``` + diff --git a/src/ruby_client/docs/Systems.md b/src/ruby_client/docs/Systems.md index 664870f4..04f4d3e0 100644 --- a/src/ruby_client/docs/Systems.md +++ b/src/ruby_client/docs/Systems.md @@ -98,6 +98,8 @@ | **atc_termination_date** | **Integer** | [Read-Only] The Connectivity Authorization Termination Date. | [optional] | | **system_development_life_cycle** | **String** | [Read-Only] Indicate the date by which the System needs to be deployed to a production environment. VA only. | [optional] | | **is_fisma_reportable** | **Boolean** | [Read-Only] Is this IS reportable per Federal Information Security Management Act (FISMA) established requirements? VA only | [optional] | +| **group_tagging** | **String** | [Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only. | [optional] | +| **group_tag_descriptions** | **String** | [Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only. | [optional] | | **package** | [**Array<PacGet>**](PacGet.md) | | [optional] | | **connectivity_ccsd** | [**Array<ConnectivityCcsd>**](ConnectivityCcsd.md) | | [optional] | @@ -135,7 +137,7 @@ instance = EmassClient::Systems.new( ditpr_id: 30498, apms_id: 30498, vasi_id: 30498, - authorization_status: null, + authorization_status: Not Yet Authorized, authorization_date: 1638741660, authorization_termination_date: 1638741660, authorization_length: 365, @@ -201,6 +203,8 @@ instance = EmassClient::Systems.new( atc_termination_date: 1638741660, system_development_life_cycle: Test Other Service, is_fisma_reportable: false, + group_tagging: Group Tag 1, + group_tag_descriptions: Group Tag 1 explanation, package: null, connectivity_ccsd: null ) diff --git a/src/ruby_client/docs/WorkflowInstanceResponseGet.md b/src/ruby_client/docs/WorkflowInstanceResponseGet.md index 1dd10f8c..13474bbe 100644 --- a/src/ruby_client/docs/WorkflowInstanceResponseGet.md +++ b/src/ruby_client/docs/WorkflowInstanceResponseGet.md @@ -5,7 +5,7 @@ | Name | Type | Description | Notes | | ---- | ---- | ----------- | ----- | | **meta** | [**Response200**](Response200.md) | | [optional] | -| **data** | [**Array<WorkflowInstanceGet>**](WorkflowInstanceGet.md) | | [optional] | +| **data** | [**WorkflowInstanceGet**](WorkflowInstanceGet.md) | | [optional] | ## Example diff --git a/src/ruby_client/emass_client.gemspec b/src/ruby_client/emass_client.gemspec index c5d810e8..c7b722a3 100644 --- a/src/ruby_client/emass_client.gemspec +++ b/src/ruby_client/emass_client.gemspec @@ -5,7 +5,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client.rb b/src/ruby_client/lib/emass_client.rb index 6fe6c916..3a7b6739 100644 --- a/src/ruby_client/lib/emass_client.rb +++ b/src/ruby_client/lib/emass_client.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -39,6 +39,8 @@ require 'emass_client/models/controls_put' require 'emass_client/models/controls_response_get' require 'emass_client/models/controls_response_put' +require 'emass_client/models/dashboard_mock_response' +require 'emass_client/models/dashboard_mock_response_pagination' require 'emass_client/models/definition_transitions' require 'emass_client/models/instances_transitions' require 'emass_client/models/milestone_response_get' @@ -50,6 +52,7 @@ require 'emass_client/models/milestones_request_delete_body_inner' require 'emass_client/models/milestones_required_post' require 'emass_client/models/milestones_required_put' +require 'emass_client/models/mock_object' require 'emass_client/models/pac_get' require 'emass_client/models/pac_post' require 'emass_client/models/pac_response_get' diff --git a/src/ruby_client/lib/emass_client/api/artifacts_api.rb b/src/ruby_client/lib/emass_client/api/artifacts_api.rb index cd3f7556..9a97ef60 100644 --- a/src/ruby_client/lib/emass_client/api/artifacts_api.rb +++ b/src/ruby_client/lib/emass_client/api/artifacts_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb b/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb index 397de286..85389c78 100644 --- a/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb +++ b/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/cac_api.rb b/src/ruby_client/lib/emass_client/api/cac_api.rb index 7389fe0a..e2f3eaae 100644 --- a/src/ruby_client/lib/emass_client/api/cac_api.rb +++ b/src/ruby_client/lib/emass_client/api/cac_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb b/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb index 30e97288..c6b23de1 100644 --- a/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb b/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb index e0d80daa..21e87816 100644 --- a/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb +++ b/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb b/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb index 0a2edd98..75b57be6 100644 --- a/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/controls_api.rb b/src/ruby_client/lib/emass_client/api/controls_api.rb index 3f27a9c9..665021da 100644 --- a/src/ruby_client/lib/emass_client/api/controls_api.rb +++ b/src/ruby_client/lib/emass_client/api/controls_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/dashboards_api.rb b/src/ruby_client/lib/emass_client/api/dashboards_api.rb index fa7bd24e..bf408226 100644 --- a/src/ruby_client/lib/emass_client/api/dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/dashboards_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -19,7 +19,7 @@ class DashboardsApi def initialize(api_client = ApiClient.default) @api_client = api_client end - # Get dashboard information + # System Artifacts Details # Get system Artifacts details information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -32,7 +32,7 @@ def get_system_artifacts_details(org_id, opts = {}) data end - # Get dashboard information + # System Artifacts Details # Get system Artifacts details information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -92,7 +92,7 @@ def get_system_artifacts_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Artifacts Summary # Get system Artifacts summary information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -105,7 +105,7 @@ def get_system_artifacts_summary(org_id, opts = {}) data end - # Get dashboard information + # System Artifacts Summary # Get system Artifacts summary information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -165,7 +165,7 @@ def get_system_artifacts_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Assessment Procedures Details # Get systems assessement procdures details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -178,7 +178,7 @@ def get_system_assessment_procedures_details(org_id, opts = {}) data end - # Get dashboard information + # System Assessment Procedures Details # Get systems assessement procdures details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -238,7 +238,7 @@ def get_system_assessment_procedures_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Associations Details # Get system associations details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -251,7 +251,7 @@ def get_system_associations_details(org_id, opts = {}) data end - # Get dashboard information + # System Associations Details # Get system associations details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -311,7 +311,80 @@ def get_system_associations_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System CONMON Integration Status + # Get system CONMON integration status dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_common_integration_status_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_common_integration_status_summary_with_http_info(org_id, opts) + data + end + + # System CONMON Integration Status + # Get system CONMON integration status dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_common_integration_status_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_common_integration_status_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_common_integration_status_summary" + end + # resource path + local_var_path = '/api/dashboards/system-conmon-integration-status-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'excludeinherited'] = opts[:'excludeinherited'] if !opts[:'excludeinherited'].nil? + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_common_integration_status_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_common_integration_status_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # System Control Compliance Summary # Get systems control compliance summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -324,7 +397,7 @@ def get_system_control_compliance_summary(org_id, opts = {}) data end - # Get dashboard information + # System Control Compliance Summary # Get systems control compliance summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -384,7 +457,7 @@ def get_system_control_compliance_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Hardware Details # Get system hardware details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -397,7 +470,7 @@ def get_system_hardware_details(org_id, opts = {}) data end - # Get dashboard information + # System Hardware Details # Get system hardware details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -457,7 +530,7 @@ def get_system_hardware_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Hardware Summary # Get system hardware summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -470,7 +543,7 @@ def get_system_hardware_summary(org_id, opts = {}) data end - # Get dashboard information + # System Hardware Summary # Get system hardware summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -530,7 +603,7 @@ def get_system_hardware_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System POA&M Details # Get system POA&Ms details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -543,7 +616,7 @@ def get_system_poam_details(org_id, opts = {}) data end - # Get dashboard information + # System POA&M Details # Get system POA&Ms details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -603,7 +676,7 @@ def get_system_poam_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System POA&M Summary # Get systems POA&Ms summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -616,7 +689,7 @@ def get_system_poam_summary(org_id, opts = {}) data end - # Get dashboard information + # System POA&M Summary # Get systems POA&Ms summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -676,7 +749,7 @@ def get_system_poam_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Ports/Protocols Details # Get system ports and protocols details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -689,7 +762,7 @@ def get_system_ports_protocols_details(org_id, opts = {}) data end - # Get dashboard information + # System Ports/Protocols Details # Get system ports and protocols details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -749,7 +822,7 @@ def get_system_ports_protocols_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Ports/Protocols Summary # Get system ports and protocols summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -762,7 +835,7 @@ def get_system_ports_protocols_summary(org_id, opts = {}) data end - # Get dashboard information + # System Ports/Protocols Summary # Get system ports and protocols summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -822,7 +895,7 @@ def get_system_ports_protocols_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Privacy Summary # Get user system privacy summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -835,7 +908,7 @@ def get_system_privacy_summary(org_id, opts = {}) data end - # Get dashboard information + # System Privacy Summary # Get user system privacy summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -895,7 +968,7 @@ def get_system_privacy_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Control Compliance Details # Get systems security control details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -908,7 +981,7 @@ def get_system_security_control_details(org_id, opts = {}) data end - # Get dashboard information + # System Control Compliance Details # Get systems security control details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -968,7 +1041,7 @@ def get_system_security_control_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Sensor Hardware Details # Get system sensor hardware details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -981,7 +1054,7 @@ def get_system_sensor_hardware_details(org_id, opts = {}) data end - # Get dashboard information + # System Sensor Hardware Details # Get system sensor hardware details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1041,7 +1114,7 @@ def get_system_sensor_hardware_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Sensor Hardware Summary # Get system sensor hardware summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1054,7 +1127,7 @@ def get_system_sensor_hardware_summary(org_id, opts = {}) data end - # Get dashboard information + # System Sensor Hardware Summary # Get system sensor hardware summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1114,7 +1187,153 @@ def get_system_sensor_hardware_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # System Software Details + # Get system software details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_software_details(org_id, opts = {}) + data, _status_code, _headers = get_system_software_details_with_http_info(org_id, opts) + data + end + + # System Software Details + # Get system software details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_software_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_software_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_software_details" + end + # resource path + local_var_path = '/api/dashboards/system-software-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'excludeinherited'] = opts[:'excludeinherited'] if !opts[:'excludeinherited'].nil? + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_software_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_software_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # System Software Summary + # Get system software summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_software_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_software_summary_with_http_info(org_id, opts) + data + end + + # System Software Summary + # Get system software summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. (default to false) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_software_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_software_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_software_summary" + end + # resource path + local_var_path = '/api/dashboards/system-software-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'excludeinherited'] = opts[:'excludeinherited'] if !opts[:'excludeinherited'].nil? + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_software_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_software_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # System Status Details # Get systems status detail dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1127,7 +1346,7 @@ def get_system_status_details(org_id, opts = {}) data end - # Get dashboard information + # System Status Details # Get systems status detail dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1187,7 +1406,7 @@ def get_system_status_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # User System Assignments Details # Get user system assignments details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1200,7 +1419,7 @@ def get_user_system_assignments_details(org_id, opts = {}) data end - # Get dashboard information + # User System Assignments Details # Get user system assignments details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1260,7 +1479,7 @@ def get_user_system_assignments_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA OMB FISMA SAOP Summary # Get VA OMB-FISMA SAOP summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1273,7 +1492,7 @@ def get_va_omb_fsma_saop_summary(org_id, opts = {}) data end - # Get dashboard information + # VA OMB FISMA SAOP Summary # Get VA OMB-FISMA SAOP summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1333,7 +1552,7 @@ def get_va_omb_fsma_saop_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System A2.0 Summary # Get VA system A2.0 summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1346,7 +1565,7 @@ def get_va_system_a2_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System A2.0 Summary # Get VA system A2.0 summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1406,7 +1625,7 @@ def get_va_system_a2_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System A&A Summary # Get VA system A&A summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1419,7 +1638,7 @@ def get_va_system_aa_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System A&A Summary # Get VA system A&A summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1479,7 +1698,7 @@ def get_va_system_aa_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System FISMA Inventory Crypto Summary # Get VA system FISMA inventory crypto summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1492,7 +1711,7 @@ def get_va_system_fisma_invetory_crypto_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System FISMA Inventory Crypto Summary # Get VA system FISMA inventory crypto summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1552,7 +1771,7 @@ def get_va_system_fisma_invetory_crypto_summary_with_http_info(org_id, opts = {} return data, status_code, headers end - # Get dashboard information + # VA System FISMA Inventory Summary # Get VA system FISMA inventory summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1565,7 +1784,7 @@ def get_va_system_fisma_invetory_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System FISMA Inventory Summary # Get VA system FISMA inventory summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1625,7 +1844,7 @@ def get_va_system_fisma_invetory_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System P.L. 109 Reporting Summary # Get VA system P.L. 109 reporting summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1638,7 +1857,7 @@ def get_va_system_pl109_reporting_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System P.L. 109 Reporting Summary # Get VA system P.L. 109 reporting summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1698,7 +1917,7 @@ def get_va_system_pl109_reporting_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System Threat Architecture Details # Get VA system threat architecture details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1711,7 +1930,7 @@ def get_va_system_threat_architecture_details(org_id, opts = {}) data end - # Get dashboard information + # VA System Threat Architecture Details # Get VA system threat architecture details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1771,7 +1990,7 @@ def get_va_system_threat_architecture_details_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System Threat Risks Summary # Get VA system threat risk summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1784,7 +2003,7 @@ def get_va_system_threat_risk_summary(org_id, opts = {}) data end - # Get dashboard information + # VA System Threat Risks Summary # Get VA system threat risk summary dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1844,7 +2063,7 @@ def get_va_system_threat_risk_summary_with_http_info(org_id, opts = {}) return data, status_code, headers end - # Get dashboard information + # VA System Threat Sources Details # Get VA system threat source details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -1857,7 +2076,7 @@ def get_va_system_threat_source_details(org_id, opts = {}) data end - # Get dashboard information + # VA System Threat Sources Details # Get VA system threat source details dashboard information. # @param org_id [Integer] **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters diff --git a/src/ruby_client/lib/emass_client/api/milestones_api.rb b/src/ruby_client/lib/emass_client/api/milestones_api.rb index c25f0c92..2692e06d 100644 --- a/src/ruby_client/lib/emass_client/api/milestones_api.rb +++ b/src/ruby_client/lib/emass_client/api/milestones_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/pac_api.rb b/src/ruby_client/lib/emass_client/api/pac_api.rb index ab22ebeb..247924f9 100644 --- a/src/ruby_client/lib/emass_client/api/pac_api.rb +++ b/src/ruby_client/lib/emass_client/api/pac_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/poam_api.rb b/src/ruby_client/lib/emass_client/api/poam_api.rb index 769a1fb5..a9fda489 100644 --- a/src/ruby_client/lib/emass_client/api/poam_api.rb +++ b/src/ruby_client/lib/emass_client/api/poam_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/registration_api.rb b/src/ruby_client/lib/emass_client/api/registration_api.rb index 32e418d6..ae4f701a 100644 --- a/src/ruby_client/lib/emass_client/api/registration_api.rb +++ b/src/ruby_client/lib/emass_client/api/registration_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb b/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb index a722aeb7..62792f8f 100644 --- a/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb +++ b/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/system_roles_api.rb b/src/ruby_client/lib/emass_client/api/system_roles_api.rb index 5903df7f..6eb25cfa 100644 --- a/src/ruby_client/lib/emass_client/api/system_roles_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_roles_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/systems_api.rb b/src/ruby_client/lib/emass_client/api/systems_api.rb index c7d318c6..88d790c7 100644 --- a/src/ruby_client/lib/emass_client/api/systems_api.rb +++ b/src/ruby_client/lib/emass_client/api/systems_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/test_api.rb b/src/ruby_client/lib/emass_client/api/test_api.rb index ff1b014d..e3367ea4 100644 --- a/src/ruby_client/lib/emass_client/api/test_api.rb +++ b/src/ruby_client/lib/emass_client/api/test_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/test_results_api.rb b/src/ruby_client/lib/emass_client/api/test_results_api.rb index 5bc4d461..2721d658 100644 --- a/src/ruby_client/lib/emass_client/api/test_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/test_results_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb b/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb index 725e99fa..8142ba7d 100644 --- a/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb +++ b/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb b/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb index d4369f31..55657d9d 100644 --- a/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb +++ b/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api_client.rb b/src/ruby_client/lib/emass_client/api_client.rb index b8b5e9a9..c457463f 100644 --- a/src/ruby_client/lib/emass_client/api_client.rb +++ b/src/ruby_client/lib/emass_client/api_client.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/api_error.rb b/src/ruby_client/lib/emass_client/api_error.rb index 9e94bffe..88ee25d2 100644 --- a/src/ruby_client/lib/emass_client/api_error.rb +++ b/src/ruby_client/lib/emass_client/api_error.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/configuration.rb b/src/ruby_client/lib/emass_client/configuration.rb index 2986826e..1b67d2a3 100644 --- a/src/ruby_client/lib/emass_client/configuration.rb +++ b/src/ruby_client/lib/emass_client/configuration.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_get.rb b/src/ruby_client/lib/emass_client/models/artifacts_get.rb index 7cc04db6..cdfd8ce1 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_get.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb index ec561aad..a5c8d8f4 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb index cd03362d..49fc572d 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb index 8d8ae6b0..b81ff756 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb index afdee868..4f8af590 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb index 1a1a1f9c..744b4ded 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb index 592ce03e..a9001544 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cac_get.rb b/src/ruby_client/lib/emass_client/models/cac_get.rb index 3faaa4f6..e31d25ff 100644 --- a/src/ruby_client/lib/emass_client/models/cac_get.rb +++ b/src/ruby_client/lib/emass_client/models/cac_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cac_response_get.rb b/src/ruby_client/lib/emass_client/models/cac_response_get.rb index d4a98a4b..218a3955 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cac_response_post.rb b/src/ruby_client/lib/emass_client/models/cac_response_post.rb index 0ce0c27e..6d5abe8a 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb b/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb index 61a78a78..5f827332 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb index a4ce8415..647e9db2 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb index fa44858b..7c9a021d 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cmmc_get.rb b/src/ruby_client/lib/emass_client/models/cmmc_get.rb index 8e174ea2..a9a5bab8 100644 --- a/src/ruby_client/lib/emass_client/models/cmmc_get.rb +++ b/src/ruby_client/lib/emass_client/models/cmmc_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb b/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb index ceb68b98..2c59b9cd 100644 --- a/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb b/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb index 2238e340..3befb759 100644 --- a/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb +++ b/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/containers_resources_post.rb b/src/ruby_client/lib/emass_client/models/containers_resources_post.rb index 96bdbe89..cb069f64 100644 --- a/src/ruby_client/lib/emass_client/models/containers_resources_post.rb +++ b/src/ruby_client/lib/emass_client/models/containers_resources_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/containers_response_post.rb b/src/ruby_client/lib/emass_client/models/containers_response_post.rb index 49dc7b00..6f7fdffa 100644 --- a/src/ruby_client/lib/emass_client/models/containers_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/containers_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/controls_get.rb b/src/ruby_client/lib/emass_client/models/controls_get.rb index d1eb0278..a300b688 100644 --- a/src/ruby_client/lib/emass_client/models/controls_get.rb +++ b/src/ruby_client/lib/emass_client/models/controls_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/controls_put.rb b/src/ruby_client/lib/emass_client/models/controls_put.rb index 56e1549c..814a6143 100644 --- a/src/ruby_client/lib/emass_client/models/controls_put.rb +++ b/src/ruby_client/lib/emass_client/models/controls_put.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/controls_response_get.rb b/src/ruby_client/lib/emass_client/models/controls_response_get.rb index 5c00d18a..5e971c54 100644 --- a/src/ruby_client/lib/emass_client/models/controls_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/controls_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/controls_response_put.rb b/src/ruby_client/lib/emass_client/models/controls_response_put.rb index 4731650c..433c038e 100644 --- a/src/ruby_client/lib/emass_client/models/controls_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/controls_response_put.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb b/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb new file mode 100644 index 00000000..51e37533 --- /dev/null +++ b/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb @@ -0,0 +1,239 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'date' +require 'time' + +module EmassClient + class DashboardMockResponse + attr_accessor :meta + + attr_accessor :data + + attr_accessor :pagination + + # Attribute mapping from ruby-style variable name to JSON key. + def self.attribute_map + { + :'meta' => :'meta', + :'data' => :'data', + :'pagination' => :'pagination' + } + end + + # Returns all the JSON keys this model knows about + def self.acceptable_attributes + attribute_map.values + end + + # Attribute type mapping. + def self.openapi_types + { + :'meta' => :'Response200', + :'data' => :'Array', + :'pagination' => :'DashboardMockResponsePagination' + } + end + + # List of attributes with nullable: true + def self.openapi_nullable + Set.new([ + ]) + end + + # Initializes the object + # @param [Hash] attributes Model attributes in the form of hash + def initialize(attributes = {}) + if (!attributes.is_a?(Hash)) + fail ArgumentError, "The input argument (attributes) must be a hash in `EmassClient::DashboardMockResponse` initialize method" + end + + # check to see if the attribute exists and convert string to symbol for hash key + attributes = attributes.each_with_object({}) { |(k, v), h| + if (!self.class.attribute_map.key?(k.to_sym)) + fail ArgumentError, "`#{k}` is not a valid attribute in `EmassClient::DashboardMockResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + end + h[k.to_sym] = v + } + + if attributes.key?(:'meta') + self.meta = attributes[:'meta'] + end + + if attributes.key?(:'data') + if (value = attributes[:'data']).is_a?(Array) + self.data = value + end + end + + if attributes.key?(:'pagination') + self.pagination = attributes[:'pagination'] + end + end + + # Show invalid properties with the reasons. Usually used together with valid? + # @return Array for valid properties with the reasons + def list_invalid_properties + invalid_properties = Array.new + invalid_properties + end + + # Check to see if the all the properties in the model are valid + # @return true if the model is valid + def valid? + true + end + + # Checks equality by comparing each attribute. + # @param [Object] Object to be compared + def ==(o) + return true if self.equal?(o) + self.class == o.class && + meta == o.meta && + data == o.data && + pagination == o.pagination + end + + # @see the `==` method + # @param [Object] Object to be compared + def eql?(o) + self == o + end + + # Calculates hash code according to all attributes. + # @return [Integer] Hash code + def hash + [meta, data, pagination].hash + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def self.build_from_hash(attributes) + new.build_from_hash(attributes) + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def build_from_hash(attributes) + return nil unless attributes.is_a?(Hash) + attributes = attributes.transform_keys(&:to_sym) + self.class.openapi_types.each_pair do |key, type| + if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key) + self.send("#{key}=", nil) + elsif type =~ /\AArray<(.*)>/i + # check to ensure the input is an array given that the attribute + # is documented as an array but the input is not + if attributes[self.class.attribute_map[key]].is_a?(Array) + self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) }) + end + elsif !attributes[self.class.attribute_map[key]].nil? + self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]])) + end + end + + self + end + + # Deserializes the data based on type + # @param string type Data type + # @param string value Value to be deserialized + # @return [Object] Deserialized data + def _deserialize(type, value) + case type.to_sym + when :Time + Time.parse(value) + when :Date + Date.parse(value) + when :String + value.to_s + when :Integer + value.to_i + when :Float + value.to_f + when :Boolean + if value.to_s =~ /\A(true|t|yes|y|1)\z/i + true + else + false + end + when :Object + # generic object (usually a Hash), return directly + value + when /\AArray<(?.+)>\z/ + inner_type = Regexp.last_match[:inner_type] + value.map { |v| _deserialize(inner_type, v) } + when /\AHash<(?.+?), (?.+)>\z/ + k_type = Regexp.last_match[:k_type] + v_type = Regexp.last_match[:v_type] + {}.tap do |hash| + value.each do |k, v| + hash[_deserialize(k_type, k)] = _deserialize(v_type, v) + end + end + else # model + # models (e.g. Pet) or oneOf + klass = EmassClient.const_get(type) + klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value) + end + end + + # Returns the string representation of the object + # @return [String] String presentation of the object + def to_s + to_hash.to_s + end + + # to_body is an alias to to_hash (backward compatibility) + # @return [Hash] Returns the object in the form of hash + def to_body + to_hash + end + + # Returns the object in the form of hash + # @return [Hash] Returns the object in the form of hash + def to_hash + hash = {} + self.class.attribute_map.each_pair do |attr, param| + value = self.send(attr) + if value.nil? + is_nullable = self.class.openapi_nullable.include?(attr) + next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}")) + end + + hash[param] = _to_hash(value) + end + hash + end + + # Outputs non-array value in the form of hash + # For object, use to_hash. Otherwise, just return the value + # @param [Object] value Any valid value + # @return [Hash] Returns the value in the form of hash + def _to_hash(value) + if value.is_a?(Array) + value.compact.map { |v| _to_hash(v) } + elsif value.is_a?(Hash) + {}.tap do |hash| + value.each { |k, v| hash[k] = _to_hash(v) } + end + elsif value.respond_to? :to_hash + value.to_hash + else + value + end + end + + end + +end diff --git a/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb b/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb new file mode 100644 index 00000000..140cc628 --- /dev/null +++ b/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb @@ -0,0 +1,264 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'date' +require 'time' + +module EmassClient + class DashboardMockResponsePagination + attr_accessor :total_count + + attr_accessor :total_pages + + attr_accessor :page_index + + attr_accessor :page_size + + attr_accessor :prev_page_url + + attr_accessor :next_page_url + + # Attribute mapping from ruby-style variable name to JSON key. + def self.attribute_map + { + :'total_count' => :'totalCount', + :'total_pages' => :'totalPages', + :'page_index' => :'pageIndex', + :'page_size' => :'pageSize', + :'prev_page_url' => :'prevPageUrl', + :'next_page_url' => :'nextPageUrl' + } + end + + # Returns all the JSON keys this model knows about + def self.acceptable_attributes + attribute_map.values + end + + # Attribute type mapping. + def self.openapi_types + { + :'total_count' => :'Integer', + :'total_pages' => :'Integer', + :'page_index' => :'Integer', + :'page_size' => :'Integer', + :'prev_page_url' => :'String', + :'next_page_url' => :'String' + } + end + + # List of attributes with nullable: true + def self.openapi_nullable + Set.new([ + ]) + end + + # Initializes the object + # @param [Hash] attributes Model attributes in the form of hash + def initialize(attributes = {}) + if (!attributes.is_a?(Hash)) + fail ArgumentError, "The input argument (attributes) must be a hash in `EmassClient::DashboardMockResponsePagination` initialize method" + end + + # check to see if the attribute exists and convert string to symbol for hash key + attributes = attributes.each_with_object({}) { |(k, v), h| + if (!self.class.attribute_map.key?(k.to_sym)) + fail ArgumentError, "`#{k}` is not a valid attribute in `EmassClient::DashboardMockResponsePagination`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + end + h[k.to_sym] = v + } + + if attributes.key?(:'total_count') + self.total_count = attributes[:'total_count'] + end + + if attributes.key?(:'total_pages') + self.total_pages = attributes[:'total_pages'] + end + + if attributes.key?(:'page_index') + self.page_index = attributes[:'page_index'] + end + + if attributes.key?(:'page_size') + self.page_size = attributes[:'page_size'] + end + + if attributes.key?(:'prev_page_url') + self.prev_page_url = attributes[:'prev_page_url'] + end + + if attributes.key?(:'next_page_url') + self.next_page_url = attributes[:'next_page_url'] + end + end + + # Show invalid properties with the reasons. Usually used together with valid? + # @return Array for valid properties with the reasons + def list_invalid_properties + invalid_properties = Array.new + invalid_properties + end + + # Check to see if the all the properties in the model are valid + # @return true if the model is valid + def valid? + true + end + + # Checks equality by comparing each attribute. + # @param [Object] Object to be compared + def ==(o) + return true if self.equal?(o) + self.class == o.class && + total_count == o.total_count && + total_pages == o.total_pages && + page_index == o.page_index && + page_size == o.page_size && + prev_page_url == o.prev_page_url && + next_page_url == o.next_page_url + end + + # @see the `==` method + # @param [Object] Object to be compared + def eql?(o) + self == o + end + + # Calculates hash code according to all attributes. + # @return [Integer] Hash code + def hash + [total_count, total_pages, page_index, page_size, prev_page_url, next_page_url].hash + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def self.build_from_hash(attributes) + new.build_from_hash(attributes) + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def build_from_hash(attributes) + return nil unless attributes.is_a?(Hash) + attributes = attributes.transform_keys(&:to_sym) + self.class.openapi_types.each_pair do |key, type| + if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key) + self.send("#{key}=", nil) + elsif type =~ /\AArray<(.*)>/i + # check to ensure the input is an array given that the attribute + # is documented as an array but the input is not + if attributes[self.class.attribute_map[key]].is_a?(Array) + self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) }) + end + elsif !attributes[self.class.attribute_map[key]].nil? + self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]])) + end + end + + self + end + + # Deserializes the data based on type + # @param string type Data type + # @param string value Value to be deserialized + # @return [Object] Deserialized data + def _deserialize(type, value) + case type.to_sym + when :Time + Time.parse(value) + when :Date + Date.parse(value) + when :String + value.to_s + when :Integer + value.to_i + when :Float + value.to_f + when :Boolean + if value.to_s =~ /\A(true|t|yes|y|1)\z/i + true + else + false + end + when :Object + # generic object (usually a Hash), return directly + value + when /\AArray<(?.+)>\z/ + inner_type = Regexp.last_match[:inner_type] + value.map { |v| _deserialize(inner_type, v) } + when /\AHash<(?.+?), (?.+)>\z/ + k_type = Regexp.last_match[:k_type] + v_type = Regexp.last_match[:v_type] + {}.tap do |hash| + value.each do |k, v| + hash[_deserialize(k_type, k)] = _deserialize(v_type, v) + end + end + else # model + # models (e.g. Pet) or oneOf + klass = EmassClient.const_get(type) + klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value) + end + end + + # Returns the string representation of the object + # @return [String] String presentation of the object + def to_s + to_hash.to_s + end + + # to_body is an alias to to_hash (backward compatibility) + # @return [Hash] Returns the object in the form of hash + def to_body + to_hash + end + + # Returns the object in the form of hash + # @return [Hash] Returns the object in the form of hash + def to_hash + hash = {} + self.class.attribute_map.each_pair do |attr, param| + value = self.send(attr) + if value.nil? + is_nullable = self.class.openapi_nullable.include?(attr) + next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}")) + end + + hash[param] = _to_hash(value) + end + hash + end + + # Outputs non-array value in the form of hash + # For object, use to_hash. Otherwise, just return the value + # @param [Object] value Any valid value + # @return [Hash] Returns the value in the form of hash + def _to_hash(value) + if value.is_a?(Array) + value.compact.map { |v| _to_hash(v) } + elsif value.is_a?(Hash) + {}.tap do |hash| + value.each { |k, v| hash[k] = _to_hash(v) } + end + elsif value.respond_to? :to_hash + value.to_hash + else + value + end + end + + end + +end diff --git a/src/ruby_client/lib/emass_client/models/definition_transitions.rb b/src/ruby_client/lib/emass_client/models/definition_transitions.rb index 395d64f7..ae67c603 100644 --- a/src/ruby_client/lib/emass_client/models/definition_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/definition_transitions.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/instances_transitions.rb b/src/ruby_client/lib/emass_client/models/instances_transitions.rb index 564b20e0..2a70158a 100644 --- a/src/ruby_client/lib/emass_client/models/instances_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/instances_transitions.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_get.rb b/src/ruby_client/lib/emass_client/models/milestone_response_get.rb index d52e03de..1b159eca 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb b/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb index f900c217..9d9a33fd 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_post.rb b/src/ruby_client/lib/emass_client/models/milestone_response_post.rb index 3ce6179e..c0ae209c 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_put.rb b/src/ruby_client/lib/emass_client/models/milestone_response_put.rb index 3cb55fe5..ff853c64 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_put.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestones_get.rb b/src/ruby_client/lib/emass_client/models/milestones_get.rb index 85495a49..8fb61e49 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_get.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb b/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb index 00fdfa78..4fe1881e 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb index 210ff2cc..4c18d0d4 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestones_required_post.rb b/src/ruby_client/lib/emass_client/models/milestones_required_post.rb index 6bfc8087..9c6914ca 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_required_post.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_required_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/milestones_required_put.rb b/src/ruby_client/lib/emass_client/models/milestones_required_put.rb index 763ec1cc..beaae698 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_required_put.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_required_put.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/mock_object.rb b/src/ruby_client/lib/emass_client/models/mock_object.rb new file mode 100644 index 00000000..67178d2d --- /dev/null +++ b/src/ruby_client/lib/emass_client/models/mock_object.rb @@ -0,0 +1,343 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'date' +require 'time' + +module EmassClient + class MockObject + # [Required] Organization/Office represented. 100 Characters. + attr_accessor :poc_organization + + # [Required] List of resources used. 250 Characters. + attr_accessor :resources + + # [Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy. + attr_accessor :owning_organization + + # [Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level. + attr_accessor :secondary_organization + + # [Conditional] First name of POC. 100 Characters. + attr_accessor :poc_first_name + + # [Conditional] Last name of POC. 100 Characters. + attr_accessor :poc_last_name + + # [Conditional] Email address of POC. 100 Characters. + attr_accessor :poc_email + + # [Conditional] Phone number of POC (area code) ***-**** format. 100 Characters. + attr_accessor :poc_phone_number + + # [Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High) + attr_accessor :severity + + # [Conditional] Required for ongoing and completed POA&M items. Unix time format. + attr_accessor :scheduled_completion_date + + # [Conditional] Field is required for completed POA&M items. Unix time format. + attr_accessor :completion_date + + # [Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters + attr_accessor :comments + + # [Conditional] Optionally used in PUT to delete milestones when updating a POA&M. + attr_accessor :is_active + + # Attribute mapping from ruby-style variable name to JSON key. + def self.attribute_map + { + :'poc_organization' => :'pocOrganization', + :'resources' => :'resources', + :'owning_organization' => :'owningOrganization', + :'secondary_organization' => :'secondaryOrganization', + :'poc_first_name' => :'pocFirstName', + :'poc_last_name' => :'pocLastName', + :'poc_email' => :'pocEmail', + :'poc_phone_number' => :'pocPhoneNumber', + :'severity' => :'severity', + :'scheduled_completion_date' => :'scheduledCompletionDate', + :'completion_date' => :'completionDate', + :'comments' => :'comments', + :'is_active' => :'isActive' + } + end + + # Returns all the JSON keys this model knows about + def self.acceptable_attributes + attribute_map.values + end + + # Attribute type mapping. + def self.openapi_types + { + :'poc_organization' => :'String', + :'resources' => :'String', + :'owning_organization' => :'String', + :'secondary_organization' => :'String', + :'poc_first_name' => :'String', + :'poc_last_name' => :'String', + :'poc_email' => :'String', + :'poc_phone_number' => :'String', + :'severity' => :'String', + :'scheduled_completion_date' => :'Integer', + :'completion_date' => :'Integer', + :'comments' => :'String', + :'is_active' => :'Boolean' + } + end + + # List of attributes with nullable: true + def self.openapi_nullable + Set.new([ + :'owning_organization', + :'secondary_organization', + :'scheduled_completion_date', + ]) + end + + # Initializes the object + # @param [Hash] attributes Model attributes in the form of hash + def initialize(attributes = {}) + if (!attributes.is_a?(Hash)) + fail ArgumentError, "The input argument (attributes) must be a hash in `EmassClient::MockObject` initialize method" + end + + # check to see if the attribute exists and convert string to symbol for hash key + attributes = attributes.each_with_object({}) { |(k, v), h| + if (!self.class.attribute_map.key?(k.to_sym)) + fail ArgumentError, "`#{k}` is not a valid attribute in `EmassClient::MockObject`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + end + h[k.to_sym] = v + } + + if attributes.key?(:'poc_organization') + self.poc_organization = attributes[:'poc_organization'] + end + + if attributes.key?(:'resources') + self.resources = attributes[:'resources'] + end + + if attributes.key?(:'owning_organization') + self.owning_organization = attributes[:'owning_organization'] + end + + if attributes.key?(:'secondary_organization') + self.secondary_organization = attributes[:'secondary_organization'] + end + + if attributes.key?(:'poc_first_name') + self.poc_first_name = attributes[:'poc_first_name'] + end + + if attributes.key?(:'poc_last_name') + self.poc_last_name = attributes[:'poc_last_name'] + end + + if attributes.key?(:'poc_email') + self.poc_email = attributes[:'poc_email'] + end + + if attributes.key?(:'poc_phone_number') + self.poc_phone_number = attributes[:'poc_phone_number'] + end + + if attributes.key?(:'severity') + self.severity = attributes[:'severity'] + end + + if attributes.key?(:'scheduled_completion_date') + self.scheduled_completion_date = attributes[:'scheduled_completion_date'] + end + + if attributes.key?(:'completion_date') + self.completion_date = attributes[:'completion_date'] + end + + if attributes.key?(:'comments') + self.comments = attributes[:'comments'] + end + + if attributes.key?(:'is_active') + self.is_active = attributes[:'is_active'] + end + end + + # Show invalid properties with the reasons. Usually used together with valid? + # @return Array for valid properties with the reasons + def list_invalid_properties + invalid_properties = Array.new + invalid_properties + end + + # Check to see if the all the properties in the model are valid + # @return true if the model is valid + def valid? + true + end + + # Checks equality by comparing each attribute. + # @param [Object] Object to be compared + def ==(o) + return true if self.equal?(o) + self.class == o.class && + poc_organization == o.poc_organization && + resources == o.resources && + owning_organization == o.owning_organization && + secondary_organization == o.secondary_organization && + poc_first_name == o.poc_first_name && + poc_last_name == o.poc_last_name && + poc_email == o.poc_email && + poc_phone_number == o.poc_phone_number && + severity == o.severity && + scheduled_completion_date == o.scheduled_completion_date && + completion_date == o.completion_date && + comments == o.comments && + is_active == o.is_active + end + + # @see the `==` method + # @param [Object] Object to be compared + def eql?(o) + self == o + end + + # Calculates hash code according to all attributes. + # @return [Integer] Hash code + def hash + [poc_organization, resources, owning_organization, secondary_organization, poc_first_name, poc_last_name, poc_email, poc_phone_number, severity, scheduled_completion_date, completion_date, comments, is_active].hash + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def self.build_from_hash(attributes) + new.build_from_hash(attributes) + end + + # Builds the object from hash + # @param [Hash] attributes Model attributes in the form of hash + # @return [Object] Returns the model itself + def build_from_hash(attributes) + return nil unless attributes.is_a?(Hash) + attributes = attributes.transform_keys(&:to_sym) + self.class.openapi_types.each_pair do |key, type| + if attributes[self.class.attribute_map[key]].nil? && self.class.openapi_nullable.include?(key) + self.send("#{key}=", nil) + elsif type =~ /\AArray<(.*)>/i + # check to ensure the input is an array given that the attribute + # is documented as an array but the input is not + if attributes[self.class.attribute_map[key]].is_a?(Array) + self.send("#{key}=", attributes[self.class.attribute_map[key]].map { |v| _deserialize($1, v) }) + end + elsif !attributes[self.class.attribute_map[key]].nil? + self.send("#{key}=", _deserialize(type, attributes[self.class.attribute_map[key]])) + end + end + + self + end + + # Deserializes the data based on type + # @param string type Data type + # @param string value Value to be deserialized + # @return [Object] Deserialized data + def _deserialize(type, value) + case type.to_sym + when :Time + Time.parse(value) + when :Date + Date.parse(value) + when :String + value.to_s + when :Integer + value.to_i + when :Float + value.to_f + when :Boolean + if value.to_s =~ /\A(true|t|yes|y|1)\z/i + true + else + false + end + when :Object + # generic object (usually a Hash), return directly + value + when /\AArray<(?.+)>\z/ + inner_type = Regexp.last_match[:inner_type] + value.map { |v| _deserialize(inner_type, v) } + when /\AHash<(?.+?), (?.+)>\z/ + k_type = Regexp.last_match[:k_type] + v_type = Regexp.last_match[:v_type] + {}.tap do |hash| + value.each do |k, v| + hash[_deserialize(k_type, k)] = _deserialize(v_type, v) + end + end + else # model + # models (e.g. Pet) or oneOf + klass = EmassClient.const_get(type) + klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value) + end + end + + # Returns the string representation of the object + # @return [String] String presentation of the object + def to_s + to_hash.to_s + end + + # to_body is an alias to to_hash (backward compatibility) + # @return [Hash] Returns the object in the form of hash + def to_body + to_hash + end + + # Returns the object in the form of hash + # @return [Hash] Returns the object in the form of hash + def to_hash + hash = {} + self.class.attribute_map.each_pair do |attr, param| + value = self.send(attr) + if value.nil? + is_nullable = self.class.openapi_nullable.include?(attr) + next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}")) + end + + hash[param] = _to_hash(value) + end + hash + end + + # Outputs non-array value in the form of hash + # For object, use to_hash. Otherwise, just return the value + # @param [Object] value Any valid value + # @return [Hash] Returns the value in the form of hash + def _to_hash(value) + if value.is_a?(Array) + value.compact.map { |v| _to_hash(v) } + elsif value.is_a?(Hash) + {}.tap do |hash| + value.each { |k, v| hash[k] = _to_hash(v) } + end + elsif value.respond_to? :to_hash + value.to_hash + else + value + end + end + + end + +end diff --git a/src/ruby_client/lib/emass_client/models/pac_get.rb b/src/ruby_client/lib/emass_client/models/pac_get.rb index 481f7eb4..96510b96 100644 --- a/src/ruby_client/lib/emass_client/models/pac_get.rb +++ b/src/ruby_client/lib/emass_client/models/pac_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/pac_post.rb b/src/ruby_client/lib/emass_client/models/pac_post.rb index 76e8994f..e7ce5e2d 100644 --- a/src/ruby_client/lib/emass_client/models/pac_post.rb +++ b/src/ruby_client/lib/emass_client/models/pac_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/pac_response_get.rb b/src/ruby_client/lib/emass_client/models/pac_response_get.rb index 1d8a6865..aeb59a4c 100644 --- a/src/ruby_client/lib/emass_client/models/pac_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/pac_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/pac_response_post.rb b/src/ruby_client/lib/emass_client/models/pac_response_post.rb index eba14afa..9d1087c7 100644 --- a/src/ruby_client/lib/emass_client/models/pac_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/pac_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_get.rb b/src/ruby_client/lib/emass_client/models/poam_get.rb index fdfc1208..c56d5aeb 100644 --- a/src/ruby_client/lib/emass_client/models/poam_get.rb +++ b/src/ruby_client/lib/emass_client/models/poam_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb b/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb index 6dd1ac75..f1f25063 100644 --- a/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb +++ b/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb index 4d269c2f..ea8e4037 100644 --- a/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_response_delete.rb b/src/ruby_client/lib/emass_client/models/poam_response_delete.rb index c619fef0..3fe06d14 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_delete.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_delete.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb b/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb index 7f6c901e..0c88af12 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb b/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb index 2a9f2f4e..12b24ead 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_response_post.rb b/src/ruby_client/lib/emass_client/models/poam_response_post.rb index c0f6a2aa..4291aeea 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/poam_response_put.rb b/src/ruby_client/lib/emass_client/models/poam_response_put.rb index bce2ccc3..26c9d4c8 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_put.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/register.rb b/src/ruby_client/lib/emass_client/models/register.rb index 77cdcb5d..e3048787 100644 --- a/src/ruby_client/lib/emass_client/models/register.rb +++ b/src/ruby_client/lib/emass_client/models/register.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/register_data.rb b/src/ruby_client/lib/emass_client/models/register_data.rb index ae98dd29..f2a057f7 100644 --- a/src/ruby_client/lib/emass_client/models/register_data.rb +++ b/src/ruby_client/lib/emass_client/models/register_data.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb b/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb index 58f321ed..8e454448 100644 --- a/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb +++ b/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response200.rb b/src/ruby_client/lib/emass_client/models/response200.rb index 44f2beaa..9edad48c 100644 --- a/src/ruby_client/lib/emass_client/models/response200.rb +++ b/src/ruby_client/lib/emass_client/models/response200.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response201.rb b/src/ruby_client/lib/emass_client/models/response201.rb index aecc9daf..4421092d 100644 --- a/src/ruby_client/lib/emass_client/models/response201.rb +++ b/src/ruby_client/lib/emass_client/models/response201.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response201_meta.rb b/src/ruby_client/lib/emass_client/models/response201_meta.rb index 77125f74..c7d727bd 100644 --- a/src/ruby_client/lib/emass_client/models/response201_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response201_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response400.rb b/src/ruby_client/lib/emass_client/models/response400.rb index 4bb12804..539dc157 100644 --- a/src/ruby_client/lib/emass_client/models/response400.rb +++ b/src/ruby_client/lib/emass_client/models/response400.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response400_meta.rb b/src/ruby_client/lib/emass_client/models/response400_meta.rb index c5f7d921..2ec2a043 100644 --- a/src/ruby_client/lib/emass_client/models/response400_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response400_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response401.rb b/src/ruby_client/lib/emass_client/models/response401.rb index 39ff5ce1..9a569f75 100644 --- a/src/ruby_client/lib/emass_client/models/response401.rb +++ b/src/ruby_client/lib/emass_client/models/response401.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response401_meta.rb b/src/ruby_client/lib/emass_client/models/response401_meta.rb index 0b634fa8..98ed71aa 100644 --- a/src/ruby_client/lib/emass_client/models/response401_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response401_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response403.rb b/src/ruby_client/lib/emass_client/models/response403.rb index 82fab890..d42b646e 100644 --- a/src/ruby_client/lib/emass_client/models/response403.rb +++ b/src/ruby_client/lib/emass_client/models/response403.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response403_meta.rb b/src/ruby_client/lib/emass_client/models/response403_meta.rb index 83b09c34..0e1e4986 100644 --- a/src/ruby_client/lib/emass_client/models/response403_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response403_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response404.rb b/src/ruby_client/lib/emass_client/models/response404.rb index 491ad182..dc60444b 100644 --- a/src/ruby_client/lib/emass_client/models/response404.rb +++ b/src/ruby_client/lib/emass_client/models/response404.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response405.rb b/src/ruby_client/lib/emass_client/models/response405.rb index 7bd3efb3..a63dce1e 100644 --- a/src/ruby_client/lib/emass_client/models/response405.rb +++ b/src/ruby_client/lib/emass_client/models/response405.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response405_meta.rb b/src/ruby_client/lib/emass_client/models/response405_meta.rb index 171b81f0..fae75be0 100644 --- a/src/ruby_client/lib/emass_client/models/response405_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response405_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response411.rb b/src/ruby_client/lib/emass_client/models/response411.rb index 35836938..3db6861c 100644 --- a/src/ruby_client/lib/emass_client/models/response411.rb +++ b/src/ruby_client/lib/emass_client/models/response411.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response411_meta.rb b/src/ruby_client/lib/emass_client/models/response411_meta.rb index de5a0220..9f56851f 100644 --- a/src/ruby_client/lib/emass_client/models/response411_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response411_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response490.rb b/src/ruby_client/lib/emass_client/models/response490.rb index 4ec42af5..474487d7 100644 --- a/src/ruby_client/lib/emass_client/models/response490.rb +++ b/src/ruby_client/lib/emass_client/models/response490.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response490_meta.rb b/src/ruby_client/lib/emass_client/models/response490_meta.rb index 98ed3e79..b329b9f5 100644 --- a/src/ruby_client/lib/emass_client/models/response490_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response490_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response500.rb b/src/ruby_client/lib/emass_client/models/response500.rb index 0b82b2ae..587568a3 100644 --- a/src/ruby_client/lib/emass_client/models/response500.rb +++ b/src/ruby_client/lib/emass_client/models/response500.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/response500_meta.rb b/src/ruby_client/lib/emass_client/models/response500_meta.rb index a3403765..be99ee48 100644 --- a/src/ruby_client/lib/emass_client/models/response500_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response500_meta.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/role_category.rb b/src/ruby_client/lib/emass_client/models/role_category.rb index 9d56ce0c..a8f5027f 100644 --- a/src/ruby_client/lib/emass_client/models/role_category.rb +++ b/src/ruby_client/lib/emass_client/models/role_category.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/roles.rb b/src/ruby_client/lib/emass_client/models/roles.rb index 1e018014..399a0950 100644 --- a/src/ruby_client/lib/emass_client/models/roles.rb +++ b/src/ruby_client/lib/emass_client/models/roles.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/ssps.rb b/src/ruby_client/lib/emass_client/models/ssps.rb index 985aea78..9a2b4f09 100644 --- a/src/ruby_client/lib/emass_client/models/ssps.rb +++ b/src/ruby_client/lib/emass_client/models/ssps.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/stage.rb b/src/ruby_client/lib/emass_client/models/stage.rb index 1c205351..9dd94c60 100644 --- a/src/ruby_client/lib/emass_client/models/stage.rb +++ b/src/ruby_client/lib/emass_client/models/stage.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/static_code_application.rb b/src/ruby_client/lib/emass_client/models/static_code_application.rb index d713174b..18d5820e 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_application.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_application.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/static_code_post.rb b/src/ruby_client/lib/emass_client/models/static_code_post.rb index 916f9976..f2b1eb9c 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_post.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb b/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb index e7cace9b..89645668 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb b/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb index 0b971332..26a85ebc 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/static_code_response_post.rb b/src/ruby_client/lib/emass_client/models/static_code_response_post.rb index 512ba976..7d6f9bf6 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/success200_response.rb b/src/ruby_client/lib/emass_client/models/success200_response.rb index 7dc4ba7c..bb8377ea 100644 --- a/src/ruby_client/lib/emass_client/models/success200_response.rb +++ b/src/ruby_client/lib/emass_client/models/success200_response.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb b/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb index 2dec6246..ca0d9a8a 100644 --- a/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/system_response.rb b/src/ruby_client/lib/emass_client/models/system_response.rb index 08ebe806..b9faada4 100644 --- a/src/ruby_client/lib/emass_client/models/system_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_response.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb b/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb index 5803d5fc..d22fbdfd 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/system_roles_response.rb b/src/ruby_client/lib/emass_client/models/system_roles_response.rb index dd2beec7..76cb631b 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_response.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb b/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb index 70ba76fc..7f982b5f 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/systems.rb b/src/ruby_client/lib/emass_client/models/systems.rb index 210122ae..324e0790 100644 --- a/src/ruby_client/lib/emass_client/models/systems.rb +++ b/src/ruby_client/lib/emass_client/models/systems.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -297,6 +297,12 @@ class Systems # [Read-Only] Is this IS reportable per Federal Information Security Management Act (FISMA) established requirements? VA only attr_accessor :is_fisma_reportable + # [Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only. + attr_accessor :group_tagging + + # [Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only. + attr_accessor :group_tag_descriptions + attr_accessor :package attr_accessor :connectivity_ccsd @@ -420,6 +426,8 @@ def self.attribute_map :'atc_termination_date' => :'atcTerminationDate', :'system_development_life_cycle' => :'systemDevelopmentLifeCycle', :'is_fisma_reportable' => :'isFISMAReportable', + :'group_tagging' => :'groupTagging', + :'group_tag_descriptions' => :'groupTagDescriptions', :'package' => :'package', :'connectivity_ccsd' => :'connectivityCcsd' } @@ -527,6 +535,8 @@ def self.openapi_types :'atc_termination_date' => :'Integer', :'system_development_life_cycle' => :'String', :'is_fisma_reportable' => :'Boolean', + :'group_tagging' => :'String', + :'group_tag_descriptions' => :'String', :'package' => :'Array', :'connectivity_ccsd' => :'Array' } @@ -627,6 +637,8 @@ def self.openapi_nullable :'atc_termination_date', :'system_development_life_cycle', :'is_fisma_reportable', + :'group_tagging', + :'group_tag_descriptions', :'package', :'connectivity_ccsd' ]) @@ -1023,6 +1035,14 @@ def initialize(attributes = {}) self.is_fisma_reportable = attributes[:'is_fisma_reportable'] end + if attributes.key?(:'group_tagging') + self.group_tagging = attributes[:'group_tagging'] + end + + if attributes.key?(:'group_tag_descriptions') + self.group_tag_descriptions = attributes[:'group_tag_descriptions'] + end + if attributes.key?(:'package') if (value = attributes[:'package']).is_a?(Array) self.package = value @@ -1352,6 +1372,8 @@ def ==(o) atc_termination_date == o.atc_termination_date && system_development_life_cycle == o.system_development_life_cycle && is_fisma_reportable == o.is_fisma_reportable && + group_tagging == o.group_tagging && + group_tag_descriptions == o.group_tag_descriptions && package == o.package && connectivity_ccsd == o.connectivity_ccsd end @@ -1365,7 +1387,7 @@ def eql?(o) # Calculates hash code according to all attributes. # @return [Integer] Hash code def hash - [registration_completion_date, system_life_cycle_acquisition_phase, special_type, special_type_description, mission_portfolio, is_nnpi, is_rbc, is_waiver, program_office, vram_id, system_id, policy, registration_type, name, acronym, description, instance, owning_organization, secondary_organization, version_release_no, system_type, is_nss, is_public_facing, coams_id, is_type_authorization, ditpr_id, apms_id, vasi_id, authorization_status, authorization_date, authorization_termination_date, authorization_length, terms_for_auth, security_plan_approval_status, security_plan_approval_date, mission_criticality, geographical_association, system_ownership, governing_mission_area, primary_functional_area, secondary_functional_area, primary_control_set, confidentiality, integrity, availability, applied_overlays, rmf_activity, cross_domain_ticket, ditpr_don_id, mac, dod_confidentiality, contingency_plan_tested, contingency_plan_test_date, security_review_date, has_open_poam_item, has_open_poam_item90to120_past_scheduled_completion_date, has_open_poam_item120_plus_past_scheudled_completion_date, impact, has_cui, has_pii, has_phi, ppsm_registry_number, interconnected_information_system_and_identifiers, is_pia_required, pia_status, pia_date, user_defined_field1, user_defined_field2, user_defined_field3, user_defined_field4, user_defined_field5, current_rmf_lifecycle_step, other_information, reports_for_scorecard, highest_system_data_classification, overall_classification, is_hva, is_financial_management, is_reciprocity, reciprocity_exemption, cloud_computing, cloud_type, atc_status, is_saa_s, is_paa_s, is_iaa_s, other_service_models, need_date, overall_risk_score, is_hrr, atc_date, atc_termination_date, system_development_life_cycle, is_fisma_reportable, package, connectivity_ccsd].hash + [registration_completion_date, system_life_cycle_acquisition_phase, special_type, special_type_description, mission_portfolio, is_nnpi, is_rbc, is_waiver, program_office, vram_id, system_id, policy, registration_type, name, acronym, description, instance, owning_organization, secondary_organization, version_release_no, system_type, is_nss, is_public_facing, coams_id, is_type_authorization, ditpr_id, apms_id, vasi_id, authorization_status, authorization_date, authorization_termination_date, authorization_length, terms_for_auth, security_plan_approval_status, security_plan_approval_date, mission_criticality, geographical_association, system_ownership, governing_mission_area, primary_functional_area, secondary_functional_area, primary_control_set, confidentiality, integrity, availability, applied_overlays, rmf_activity, cross_domain_ticket, ditpr_don_id, mac, dod_confidentiality, contingency_plan_tested, contingency_plan_test_date, security_review_date, has_open_poam_item, has_open_poam_item90to120_past_scheduled_completion_date, has_open_poam_item120_plus_past_scheudled_completion_date, impact, has_cui, has_pii, has_phi, ppsm_registry_number, interconnected_information_system_and_identifiers, is_pia_required, pia_status, pia_date, user_defined_field1, user_defined_field2, user_defined_field3, user_defined_field4, user_defined_field5, current_rmf_lifecycle_step, other_information, reports_for_scorecard, highest_system_data_classification, overall_classification, is_hva, is_financial_management, is_reciprocity, reciprocity_exemption, cloud_computing, cloud_type, atc_status, is_saa_s, is_paa_s, is_iaa_s, other_service_models, need_date, overall_risk_score, is_hrr, atc_date, atc_termination_date, system_development_life_cycle, is_fisma_reportable, group_tagging, group_tag_descriptions, package, connectivity_ccsd].hash end # Builds the object from hash diff --git a/src/ruby_client/lib/emass_client/models/systems_response.rb b/src/ruby_client/lib/emass_client/models/systems_response.rb index 47ce0e6b..32ab6fb2 100644 --- a/src/ruby_client/lib/emass_client/models/systems_response.rb +++ b/src/ruby_client/lib/emass_client/models/systems_response.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test.rb b/src/ruby_client/lib/emass_client/models/test.rb index 7f71fe6c..2a145f9c 100644 --- a/src/ruby_client/lib/emass_client/models/test.rb +++ b/src/ruby_client/lib/emass_client/models/test.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test_data.rb b/src/ruby_client/lib/emass_client/models/test_data.rb index 92641f8c..91c99f48 100644 --- a/src/ruby_client/lib/emass_client/models/test_data.rb +++ b/src/ruby_client/lib/emass_client/models/test_data.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test_results_get.rb b/src/ruby_client/lib/emass_client/models/test_results_get.rb index d65d29e3..3063599d 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_get.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test_results_post.rb b/src/ruby_client/lib/emass_client/models/test_results_post.rb index 0379229f..9ff45b01 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_post.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test_results_response_get.rb b/src/ruby_client/lib/emass_client/models/test_results_response_get.rb index dee6bd0e..56776b9a 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/test_results_response_post.rb b/src/ruby_client/lib/emass_client/models/test_results_response_post.rb index bc2389bb..30b380c0 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_response_post.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/users.rb b/src/ruby_client/lib/emass_client/models/users.rb index 51880426..dabf5ed1 100644 --- a/src/ruby_client/lib/emass_client/models/users.rb +++ b/src/ruby_client/lib/emass_client/models/users.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb b/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb index f4584fdf..27e2ce08 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb index 9ddcd60e..fef65034 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb index 3781cff7..aae7c776 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb index 3d4dbf40..b487b40a 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -36,7 +36,7 @@ def self.acceptable_attributes def self.openapi_types { :'meta' => :'Response200', - :'data' => :'Array' + :'data' => :'WorkflowInstanceGet' } end @@ -66,9 +66,7 @@ def initialize(attributes = {}) end if attributes.key?(:'data') - if (value = attributes[:'data']).is_a?(Array) - self.data = value - end + self.data = attributes[:'data'] end end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb index fa6b1292..b0f26b4b 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb index 046d7813..39274ca8 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb index 4e806686..b0597e17 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/lib/emass_client/version.rb b/src/ruby_client/lib/emass_client/version.rb index c9b34307..a8dd5e36 100644 --- a/src/ruby_client/lib/emass_client/version.rb +++ b/src/ruby_client/lib/emass_client/version.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -11,5 +11,5 @@ =end module EmassClient - VERSION = '3.9.1' + VERSION = '3.9.10' end diff --git a/src/ruby_client/spec/api/artifacts_api_spec.rb b/src/ruby_client/spec/api/artifacts_api_spec.rb index 4d2925f5..ace345f7 100644 --- a/src/ruby_client/spec/api/artifacts_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/artifacts_export_api_spec.rb b/src/ruby_client/spec/api/artifacts_export_api_spec.rb index 143bf930..3888c998 100644 --- a/src/ruby_client/spec/api/artifacts_export_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_export_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/cac_api_spec.rb b/src/ruby_client/spec/api/cac_api_spec.rb index 54e8d1b4..c406a7ac 100644 --- a/src/ruby_client/spec/api/cac_api_spec.rb +++ b/src/ruby_client/spec/api/cac_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb b/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb index 8bd96ca2..d0c9bd70 100644 --- a/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb +++ b/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb b/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb index bbaff1b9..8f6582d7 100644 --- a/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb +++ b/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/container_scan_results_api_spec.rb b/src/ruby_client/spec/api/container_scan_results_api_spec.rb index 41f84e3c..ac86e4f4 100644 --- a/src/ruby_client/spec/api/container_scan_results_api_spec.rb +++ b/src/ruby_client/spec/api/container_scan_results_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/controls_api_spec.rb b/src/ruby_client/spec/api/controls_api_spec.rb index 7538886a..b96ed710 100644 --- a/src/ruby_client/spec/api/controls_api_spec.rb +++ b/src/ruby_client/spec/api/controls_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/dashboards_api_spec.rb b/src/ruby_client/spec/api/dashboards_api_spec.rb index 4e33990c..83be6f58 100644 --- a/src/ruby_client/spec/api/dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/dashboards_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -33,7 +33,7 @@ end # unit tests for get_system_artifacts_details - # Get dashboard information + # System Artifacts Details # Get system Artifacts details information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -48,7 +48,7 @@ end # unit tests for get_system_artifacts_summary - # Get dashboard information + # System Artifacts Summary # Get system Artifacts summary information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -63,7 +63,7 @@ end # unit tests for get_system_assessment_procedures_details - # Get dashboard information + # System Assessment Procedures Details # Get systems assessement procdures details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -78,7 +78,7 @@ end # unit tests for get_system_associations_details - # Get dashboard information + # System Associations Details # Get system associations details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -92,8 +92,23 @@ end end + # unit tests for get_system_common_integration_status_summary + # System CONMON Integration Status + # Get system CONMON integration status dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_common_integration_status_summary test' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + # unit tests for get_system_control_compliance_summary - # Get dashboard information + # System Control Compliance Summary # Get systems control compliance summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -108,7 +123,7 @@ end # unit tests for get_system_hardware_details - # Get dashboard information + # System Hardware Details # Get system hardware details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -123,7 +138,7 @@ end # unit tests for get_system_hardware_summary - # Get dashboard information + # System Hardware Summary # Get system hardware summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -138,7 +153,7 @@ end # unit tests for get_system_poam_details - # Get dashboard information + # System POA&M Details # Get system POA&Ms details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -153,7 +168,7 @@ end # unit tests for get_system_poam_summary - # Get dashboard information + # System POA&M Summary # Get systems POA&Ms summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -168,7 +183,7 @@ end # unit tests for get_system_ports_protocols_details - # Get dashboard information + # System Ports/Protocols Details # Get system ports and protocols details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -183,7 +198,7 @@ end # unit tests for get_system_ports_protocols_summary - # Get dashboard information + # System Ports/Protocols Summary # Get system ports and protocols summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -198,7 +213,7 @@ end # unit tests for get_system_privacy_summary - # Get dashboard information + # System Privacy Summary # Get user system privacy summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -213,7 +228,7 @@ end # unit tests for get_system_security_control_details - # Get dashboard information + # System Control Compliance Details # Get systems security control details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -228,7 +243,7 @@ end # unit tests for get_system_sensor_hardware_details - # Get dashboard information + # System Sensor Hardware Details # Get system sensor hardware details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -243,7 +258,7 @@ end # unit tests for get_system_sensor_hardware_summary - # Get dashboard information + # System Sensor Hardware Summary # Get system sensor hardware summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -257,8 +272,38 @@ end end + # unit tests for get_system_software_details + # System Software Details + # Get system software details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_software_details test' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + # unit tests for get_system_software_summary + # System Software Summary + # Get system software summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Boolean] :excludeinherited **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_software_summary test' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + # unit tests for get_system_status_details - # Get dashboard information + # System Status Details # Get systems status detail dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -273,7 +318,7 @@ end # unit tests for get_user_system_assignments_details - # Get dashboard information + # User System Assignments Details # Get user system assignments details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -288,7 +333,7 @@ end # unit tests for get_va_omb_fsma_saop_summary - # Get dashboard information + # VA OMB FISMA SAOP Summary # Get VA OMB-FISMA SAOP summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -303,7 +348,7 @@ end # unit tests for get_va_system_a2_summary - # Get dashboard information + # VA System A2.0 Summary # Get VA system A2.0 summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -318,7 +363,7 @@ end # unit tests for get_va_system_aa_summary - # Get dashboard information + # VA System A&A Summary # Get VA system A&A summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -333,7 +378,7 @@ end # unit tests for get_va_system_fisma_invetory_crypto_summary - # Get dashboard information + # VA System FISMA Inventory Crypto Summary # Get VA system FISMA inventory crypto summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -348,7 +393,7 @@ end # unit tests for get_va_system_fisma_invetory_summary - # Get dashboard information + # VA System FISMA Inventory Summary # Get VA system FISMA inventory summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -363,7 +408,7 @@ end # unit tests for get_va_system_pl109_reporting_summary - # Get dashboard information + # VA System P.L. 109 Reporting Summary # Get VA system P.L. 109 reporting summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -378,7 +423,7 @@ end # unit tests for get_va_system_threat_architecture_details - # Get dashboard information + # VA System Threat Architecture Details # Get VA system threat architecture details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -393,7 +438,7 @@ end # unit tests for get_va_system_threat_risk_summary - # Get dashboard information + # VA System Threat Risks Summary # Get VA system threat risk summary dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters @@ -408,7 +453,7 @@ end # unit tests for get_va_system_threat_source_details - # Get dashboard information + # VA System Threat Sources Details # Get VA system threat source details dashboard information. # @param org_id **Organization Id**: The unique organization identifier. # @param [Hash] opts the optional parameters diff --git a/src/ruby_client/spec/api/milestones_api_spec.rb b/src/ruby_client/spec/api/milestones_api_spec.rb index 76857328..f58018cc 100644 --- a/src/ruby_client/spec/api/milestones_api_spec.rb +++ b/src/ruby_client/spec/api/milestones_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/pac_api_spec.rb b/src/ruby_client/spec/api/pac_api_spec.rb index 3acf0816..52335cea 100644 --- a/src/ruby_client/spec/api/pac_api_spec.rb +++ b/src/ruby_client/spec/api/pac_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/poam_api_spec.rb b/src/ruby_client/spec/api/poam_api_spec.rb index 23b0e16e..38e4e05a 100644 --- a/src/ruby_client/spec/api/poam_api_spec.rb +++ b/src/ruby_client/spec/api/poam_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/registration_api_spec.rb b/src/ruby_client/spec/api/registration_api_spec.rb index d739a561..1db21ecf 100644 --- a/src/ruby_client/spec/api/registration_api_spec.rb +++ b/src/ruby_client/spec/api/registration_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/static_code_scans_api_spec.rb b/src/ruby_client/spec/api/static_code_scans_api_spec.rb index fa797077..133e81cb 100644 --- a/src/ruby_client/spec/api/static_code_scans_api_spec.rb +++ b/src/ruby_client/spec/api/static_code_scans_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/system_roles_api_spec.rb b/src/ruby_client/spec/api/system_roles_api_spec.rb index 02f30fcc..3c313251 100644 --- a/src/ruby_client/spec/api/system_roles_api_spec.rb +++ b/src/ruby_client/spec/api/system_roles_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/systems_api_spec.rb b/src/ruby_client/spec/api/systems_api_spec.rb index 438e388a..a9d79c7d 100644 --- a/src/ruby_client/spec/api/systems_api_spec.rb +++ b/src/ruby_client/spec/api/systems_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/test_api_spec.rb b/src/ruby_client/spec/api/test_api_spec.rb index 3a506cfb..12190be8 100644 --- a/src/ruby_client/spec/api/test_api_spec.rb +++ b/src/ruby_client/spec/api/test_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/test_results_api_spec.rb b/src/ruby_client/spec/api/test_results_api_spec.rb index f19ba143..2a358762 100644 --- a/src/ruby_client/spec/api/test_results_api_spec.rb +++ b/src/ruby_client/spec/api/test_results_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/workflow_definitions_api_spec.rb b/src/ruby_client/spec/api/workflow_definitions_api_spec.rb index 4f077275..1e0426b2 100644 --- a/src/ruby_client/spec/api/workflow_definitions_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_definitions_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api/workflow_instances_api_spec.rb b/src/ruby_client/spec/api/workflow_instances_api_spec.rb index a16513f3..274af8fd 100644 --- a/src/ruby_client/spec/api/workflow_instances_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_instances_api_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/api_client_spec.rb b/src/ruby_client/spec/api_client_spec.rb index d27f66bc..11b6cf28 100644 --- a/src/ruby_client/spec/api_client_spec.rb +++ b/src/ruby_client/spec/api_client_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/configuration_spec.rb b/src/ruby_client/spec/configuration_spec.rb index 70c11eb9..a065a121 100644 --- a/src/ruby_client/spec/configuration_spec.rb +++ b/src/ruby_client/spec/configuration_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_get_spec.rb b/src/ruby_client/spec/models/artifacts_get_spec.rb index 2173b41e..12921e25 100644 --- a/src/ruby_client/spec/models/artifacts_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb index ae465bc2..345be994 100644 --- a/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb b/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb index 5f4b8097..263469d8 100644 --- a/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_response_del_spec.rb b/src/ruby_client/spec/models/artifacts_response_del_spec.rb index 70ec817f..2ec46198 100644 --- a/src/ruby_client/spec/models/artifacts_response_del_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_del_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_response_get_spec.rb b/src/ruby_client/spec/models/artifacts_response_get_spec.rb index 1a0f62c7..4ceea512 100644 --- a/src/ruby_client/spec/models/artifacts_response_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb b/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb index b3c64f86..2714924f 100644 --- a/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb b/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb index 0c6dfaa8..bc0926ac 100644 --- a/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cac_get_spec.rb b/src/ruby_client/spec/models/cac_get_spec.rb index 6e511607..a6ddd8f9 100644 --- a/src/ruby_client/spec/models/cac_get_spec.rb +++ b/src/ruby_client/spec/models/cac_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cac_response_get_spec.rb b/src/ruby_client/spec/models/cac_response_get_spec.rb index dabf056c..d41bf34d 100644 --- a/src/ruby_client/spec/models/cac_response_get_spec.rb +++ b/src/ruby_client/spec/models/cac_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb b/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb index 10c3a637..30462110 100644 --- a/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb +++ b/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cac_response_post_spec.rb b/src/ruby_client/spec/models/cac_response_post_spec.rb index 7f8e5a14..a4951882 100644 --- a/src/ruby_client/spec/models/cac_response_post_spec.rb +++ b/src/ruby_client/spec/models/cac_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cloud_resources_post_spec.rb b/src/ruby_client/spec/models/cloud_resources_post_spec.rb index 42c171ff..44b41106 100644 --- a/src/ruby_client/spec/models/cloud_resources_post_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb b/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb index b4c339cc..493dbfe2 100644 --- a/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cmmc_get_spec.rb b/src/ruby_client/spec/models/cmmc_get_spec.rb index 8dec044b..7e38680a 100644 --- a/src/ruby_client/spec/models/cmmc_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/cmmc_response_get_spec.rb b/src/ruby_client/spec/models/cmmc_response_get_spec.rb index 4d4e275a..8ec45cac 100644 --- a/src/ruby_client/spec/models/cmmc_response_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb index be3f112b..2c6e6663 100644 --- a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb +++ b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/containers_resources_post_spec.rb b/src/ruby_client/spec/models/containers_resources_post_spec.rb index 37d9acf0..891332dc 100644 --- a/src/ruby_client/spec/models/containers_resources_post_spec.rb +++ b/src/ruby_client/spec/models/containers_resources_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/containers_response_post_spec.rb b/src/ruby_client/spec/models/containers_response_post_spec.rb index c605598f..52f5c7a4 100644 --- a/src/ruby_client/spec/models/containers_response_post_spec.rb +++ b/src/ruby_client/spec/models/containers_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/controls_get_spec.rb b/src/ruby_client/spec/models/controls_get_spec.rb index 166dfda5..f406d0e4 100644 --- a/src/ruby_client/spec/models/controls_get_spec.rb +++ b/src/ruby_client/spec/models/controls_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/controls_put_spec.rb b/src/ruby_client/spec/models/controls_put_spec.rb index 6cf2c7f2..70a34d15 100644 --- a/src/ruby_client/spec/models/controls_put_spec.rb +++ b/src/ruby_client/spec/models/controls_put_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/controls_response_get_spec.rb b/src/ruby_client/spec/models/controls_response_get_spec.rb index 18617206..21931ecf 100644 --- a/src/ruby_client/spec/models/controls_response_get_spec.rb +++ b/src/ruby_client/spec/models/controls_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/controls_response_put_spec.rb b/src/ruby_client/spec/models/controls_response_put_spec.rb index b2a65222..0c0c4d09 100644 --- a/src/ruby_client/spec/models/controls_response_put_spec.rb +++ b/src/ruby_client/spec/models/controls_response_put_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb b/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb new file mode 100644 index 00000000..a6dfae66 --- /dev/null +++ b/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb @@ -0,0 +1,64 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'spec_helper' +require 'json' +require 'date' + +# Unit tests for EmassClient::DashboardMockResponsePagination +# Automatically generated by openapi-generator (https://openapi-generator.tech) +# Please update as you see appropriate +describe EmassClient::DashboardMockResponsePagination do + let(:instance) { EmassClient::DashboardMockResponsePagination.new } + + describe 'test an instance of DashboardMockResponsePagination' do + it 'should create an instance of DashboardMockResponsePagination' do + expect(instance).to be_instance_of(EmassClient::DashboardMockResponsePagination) + end + end + describe 'test attribute "total_count"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "total_pages"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "page_index"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "page_size"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "prev_page_url"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "next_page_url"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + +end diff --git a/src/ruby_client/spec/models/dashboard_mock_response_spec.rb b/src/ruby_client/spec/models/dashboard_mock_response_spec.rb new file mode 100644 index 00000000..53c9482c --- /dev/null +++ b/src/ruby_client/spec/models/dashboard_mock_response_spec.rb @@ -0,0 +1,46 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'spec_helper' +require 'json' +require 'date' + +# Unit tests for EmassClient::DashboardMockResponse +# Automatically generated by openapi-generator (https://openapi-generator.tech) +# Please update as you see appropriate +describe EmassClient::DashboardMockResponse do + let(:instance) { EmassClient::DashboardMockResponse.new } + + describe 'test an instance of DashboardMockResponse' do + it 'should create an instance of DashboardMockResponse' do + expect(instance).to be_instance_of(EmassClient::DashboardMockResponse) + end + end + describe 'test attribute "meta"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "data"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "pagination"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + +end diff --git a/src/ruby_client/spec/models/definition_transitions_spec.rb b/src/ruby_client/spec/models/definition_transitions_spec.rb index 1435a337..7b7a58dc 100644 --- a/src/ruby_client/spec/models/definition_transitions_spec.rb +++ b/src/ruby_client/spec/models/definition_transitions_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/instances_transitions_spec.rb b/src/ruby_client/spec/models/instances_transitions_spec.rb index 3d89b9b0..7303a97f 100644 --- a/src/ruby_client/spec/models/instances_transitions_spec.rb +++ b/src/ruby_client/spec/models/instances_transitions_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb b/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb index 0c79564d..5951e0b9 100644 --- a/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestone_response_get_spec.rb b/src/ruby_client/spec/models/milestone_response_get_spec.rb index 369cc244..975f6481 100644 --- a/src/ruby_client/spec/models/milestone_response_get_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestone_response_post_spec.rb b/src/ruby_client/spec/models/milestone_response_post_spec.rb index 473ed64e..479fef47 100644 --- a/src/ruby_client/spec/models/milestone_response_post_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestone_response_put_spec.rb b/src/ruby_client/spec/models/milestone_response_put_spec.rb index af582311..bb66e66a 100644 --- a/src/ruby_client/spec/models/milestone_response_put_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_put_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestones_get_spec.rb b/src/ruby_client/spec/models/milestones_get_spec.rb index 133148de..1ff615f8 100644 --- a/src/ruby_client/spec/models/milestones_get_spec.rb +++ b/src/ruby_client/spec/models/milestones_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb b/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb index 87db6bd0..302cbf42 100644 --- a/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb +++ b/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb index dbc7c84d..97ace33b 100644 --- a/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestones_required_post_spec.rb b/src/ruby_client/spec/models/milestones_required_post_spec.rb index 00c73cf3..7aeddf5a 100644 --- a/src/ruby_client/spec/models/milestones_required_post_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/milestones_required_put_spec.rb b/src/ruby_client/spec/models/milestones_required_put_spec.rb index 8f019daf..cdae3b98 100644 --- a/src/ruby_client/spec/models/milestones_required_put_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_put_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/mock_object_spec.rb b/src/ruby_client/spec/models/mock_object_spec.rb new file mode 100644 index 00000000..4b277b0a --- /dev/null +++ b/src/ruby_client/spec/models/mock_object_spec.rb @@ -0,0 +1,106 @@ +=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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.10 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 7.0.0-SNAPSHOT + +=end + +require 'spec_helper' +require 'json' +require 'date' + +# Unit tests for EmassClient::MockObject +# Automatically generated by openapi-generator (https://openapi-generator.tech) +# Please update as you see appropriate +describe EmassClient::MockObject do + let(:instance) { EmassClient::MockObject.new } + + describe 'test an instance of MockObject' do + it 'should create an instance of MockObject' do + expect(instance).to be_instance_of(EmassClient::MockObject) + end + end + describe 'test attribute "poc_organization"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "resources"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "owning_organization"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "secondary_organization"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "poc_first_name"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "poc_last_name"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "poc_email"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "poc_phone_number"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "severity"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "scheduled_completion_date"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "completion_date"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "comments"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "is_active"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + +end diff --git a/src/ruby_client/spec/models/pac_get_spec.rb b/src/ruby_client/spec/models/pac_get_spec.rb index af96cee6..9e90234e 100644 --- a/src/ruby_client/spec/models/pac_get_spec.rb +++ b/src/ruby_client/spec/models/pac_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/pac_post_spec.rb b/src/ruby_client/spec/models/pac_post_spec.rb index f3b0bd67..9d4cb4af 100644 --- a/src/ruby_client/spec/models/pac_post_spec.rb +++ b/src/ruby_client/spec/models/pac_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/pac_response_get_spec.rb b/src/ruby_client/spec/models/pac_response_get_spec.rb index d189d2ce..57d1810c 100644 --- a/src/ruby_client/spec/models/pac_response_get_spec.rb +++ b/src/ruby_client/spec/models/pac_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/pac_response_post_spec.rb b/src/ruby_client/spec/models/pac_response_post_spec.rb index 7b03fb36..896325c2 100644 --- a/src/ruby_client/spec/models/pac_response_post_spec.rb +++ b/src/ruby_client/spec/models/pac_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_get_spec.rb b/src/ruby_client/spec/models/poam_get_spec.rb index 1edfabbd..753a0ea2 100644 --- a/src/ruby_client/spec/models/poam_get_spec.rb +++ b/src/ruby_client/spec/models/poam_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_post_put_del_spec.rb b/src/ruby_client/spec/models/poam_post_put_del_spec.rb index f0797dca..a67a9136 100644 --- a/src/ruby_client/spec/models/poam_post_put_del_spec.rb +++ b/src/ruby_client/spec/models/poam_post_put_del_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb index 2bb55e95..6266c868 100644 --- a/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_response_delete_spec.rb b/src/ruby_client/spec/models/poam_response_delete_spec.rb index d1dd0c60..42f14b06 100644 --- a/src/ruby_client/spec/models/poam_response_delete_spec.rb +++ b/src/ruby_client/spec/models/poam_response_delete_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_response_get_poams_spec.rb b/src/ruby_client/spec/models/poam_response_get_poams_spec.rb index a3e351fc..4caea598 100644 --- a/src/ruby_client/spec/models/poam_response_get_poams_spec.rb +++ b/src/ruby_client/spec/models/poam_response_get_poams_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_response_get_systems_spec.rb b/src/ruby_client/spec/models/poam_response_get_systems_spec.rb index 22596d44..6b079b24 100644 --- a/src/ruby_client/spec/models/poam_response_get_systems_spec.rb +++ b/src/ruby_client/spec/models/poam_response_get_systems_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_response_post_spec.rb b/src/ruby_client/spec/models/poam_response_post_spec.rb index 8bd31fbf..a5c31e14 100644 --- a/src/ruby_client/spec/models/poam_response_post_spec.rb +++ b/src/ruby_client/spec/models/poam_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/poam_response_put_spec.rb b/src/ruby_client/spec/models/poam_response_put_spec.rb index 8dbdc339..bc34072c 100644 --- a/src/ruby_client/spec/models/poam_response_put_spec.rb +++ b/src/ruby_client/spec/models/poam_response_put_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/register_data_spec.rb b/src/ruby_client/spec/models/register_data_spec.rb index 4bf17dd0..0d7d65d8 100644 --- a/src/ruby_client/spec/models/register_data_spec.rb +++ b/src/ruby_client/spec/models/register_data_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/register_spec.rb b/src/ruby_client/spec/models/register_spec.rb index ce2c3aa6..16b8d267 100644 --- a/src/ruby_client/spec/models/register_spec.rb +++ b/src/ruby_client/spec/models/register_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/register_user_request_post_body_spec.rb b/src/ruby_client/spec/models/register_user_request_post_body_spec.rb index eea17f36..b7e18efd 100644 --- a/src/ruby_client/spec/models/register_user_request_post_body_spec.rb +++ b/src/ruby_client/spec/models/register_user_request_post_body_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response200_spec.rb b/src/ruby_client/spec/models/response200_spec.rb index 7edd0c54..b96b4b5b 100644 --- a/src/ruby_client/spec/models/response200_spec.rb +++ b/src/ruby_client/spec/models/response200_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response201_meta_spec.rb b/src/ruby_client/spec/models/response201_meta_spec.rb index daa46a6f..d1f73991 100644 --- a/src/ruby_client/spec/models/response201_meta_spec.rb +++ b/src/ruby_client/spec/models/response201_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response201_spec.rb b/src/ruby_client/spec/models/response201_spec.rb index a09ca2d4..fe293772 100644 --- a/src/ruby_client/spec/models/response201_spec.rb +++ b/src/ruby_client/spec/models/response201_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response400_meta_spec.rb b/src/ruby_client/spec/models/response400_meta_spec.rb index f2c4b0c1..b8bbc286 100644 --- a/src/ruby_client/spec/models/response400_meta_spec.rb +++ b/src/ruby_client/spec/models/response400_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response400_spec.rb b/src/ruby_client/spec/models/response400_spec.rb index b77ac8b0..ec4e1a6c 100644 --- a/src/ruby_client/spec/models/response400_spec.rb +++ b/src/ruby_client/spec/models/response400_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response401_meta_spec.rb b/src/ruby_client/spec/models/response401_meta_spec.rb index 76037ff0..bad7bbad 100644 --- a/src/ruby_client/spec/models/response401_meta_spec.rb +++ b/src/ruby_client/spec/models/response401_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response401_spec.rb b/src/ruby_client/spec/models/response401_spec.rb index ce1e617f..031a2c61 100644 --- a/src/ruby_client/spec/models/response401_spec.rb +++ b/src/ruby_client/spec/models/response401_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response403_meta_spec.rb b/src/ruby_client/spec/models/response403_meta_spec.rb index ff91ddfe..412c0666 100644 --- a/src/ruby_client/spec/models/response403_meta_spec.rb +++ b/src/ruby_client/spec/models/response403_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response403_spec.rb b/src/ruby_client/spec/models/response403_spec.rb index fca14aa3..7b6bc037 100644 --- a/src/ruby_client/spec/models/response403_spec.rb +++ b/src/ruby_client/spec/models/response403_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response404_spec.rb b/src/ruby_client/spec/models/response404_spec.rb index e60cd3b8..93607c80 100644 --- a/src/ruby_client/spec/models/response404_spec.rb +++ b/src/ruby_client/spec/models/response404_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response405_meta_spec.rb b/src/ruby_client/spec/models/response405_meta_spec.rb index 3c063fd6..c7f6ce66 100644 --- a/src/ruby_client/spec/models/response405_meta_spec.rb +++ b/src/ruby_client/spec/models/response405_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response405_spec.rb b/src/ruby_client/spec/models/response405_spec.rb index 1511ce1a..8ea5f985 100644 --- a/src/ruby_client/spec/models/response405_spec.rb +++ b/src/ruby_client/spec/models/response405_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response411_meta_spec.rb b/src/ruby_client/spec/models/response411_meta_spec.rb index 4acfaee0..87541106 100644 --- a/src/ruby_client/spec/models/response411_meta_spec.rb +++ b/src/ruby_client/spec/models/response411_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response411_spec.rb b/src/ruby_client/spec/models/response411_spec.rb index dfdcf3e5..ec307e2d 100644 --- a/src/ruby_client/spec/models/response411_spec.rb +++ b/src/ruby_client/spec/models/response411_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response490_meta_spec.rb b/src/ruby_client/spec/models/response490_meta_spec.rb index 47183e28..aed1b7f2 100644 --- a/src/ruby_client/spec/models/response490_meta_spec.rb +++ b/src/ruby_client/spec/models/response490_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response490_spec.rb b/src/ruby_client/spec/models/response490_spec.rb index 902d22b3..086238a0 100644 --- a/src/ruby_client/spec/models/response490_spec.rb +++ b/src/ruby_client/spec/models/response490_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response500_meta_spec.rb b/src/ruby_client/spec/models/response500_meta_spec.rb index 9f567002..feb95cfe 100644 --- a/src/ruby_client/spec/models/response500_meta_spec.rb +++ b/src/ruby_client/spec/models/response500_meta_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/response500_spec.rb b/src/ruby_client/spec/models/response500_spec.rb index 3694540f..e995a9c8 100644 --- a/src/ruby_client/spec/models/response500_spec.rb +++ b/src/ruby_client/spec/models/response500_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/role_category_spec.rb b/src/ruby_client/spec/models/role_category_spec.rb index e6a9556f..57a57164 100644 --- a/src/ruby_client/spec/models/role_category_spec.rb +++ b/src/ruby_client/spec/models/role_category_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/roles_spec.rb b/src/ruby_client/spec/models/roles_spec.rb index 5556bc6a..3c530f0c 100644 --- a/src/ruby_client/spec/models/roles_spec.rb +++ b/src/ruby_client/spec/models/roles_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/ssps_spec.rb b/src/ruby_client/spec/models/ssps_spec.rb index 4d72863d..18f18f26 100644 --- a/src/ruby_client/spec/models/ssps_spec.rb +++ b/src/ruby_client/spec/models/ssps_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/stage_spec.rb b/src/ruby_client/spec/models/stage_spec.rb index 2748b0fc..508d71d9 100644 --- a/src/ruby_client/spec/models/stage_spec.rb +++ b/src/ruby_client/spec/models/stage_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/static_code_application_spec.rb b/src/ruby_client/spec/models/static_code_application_spec.rb index 14f14f2a..695edeee 100644 --- a/src/ruby_client/spec/models/static_code_application_spec.rb +++ b/src/ruby_client/spec/models/static_code_application_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/static_code_post_spec.rb b/src/ruby_client/spec/models/static_code_post_spec.rb index e0a358bc..33fff964 100644 --- a/src/ruby_client/spec/models/static_code_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb b/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb index c6a7e73d..8ba6853d 100644 --- a/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb +++ b/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/static_code_request_post_body_spec.rb b/src/ruby_client/spec/models/static_code_request_post_body_spec.rb index 0af9449d..cb0523b3 100644 --- a/src/ruby_client/spec/models/static_code_request_post_body_spec.rb +++ b/src/ruby_client/spec/models/static_code_request_post_body_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/static_code_response_post_spec.rb b/src/ruby_client/spec/models/static_code_response_post_spec.rb index ed6391cd..430e77dd 100644 --- a/src/ruby_client/spec/models/static_code_response_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/success200_response_data_inner_spec.rb b/src/ruby_client/spec/models/success200_response_data_inner_spec.rb index 73eb5669..f174b571 100644 --- a/src/ruby_client/spec/models/success200_response_data_inner_spec.rb +++ b/src/ruby_client/spec/models/success200_response_data_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/success200_response_spec.rb b/src/ruby_client/spec/models/success200_response_spec.rb index 1ec4107c..8cdaabec 100644 --- a/src/ruby_client/spec/models/success200_response_spec.rb +++ b/src/ruby_client/spec/models/success200_response_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/system_response_spec.rb b/src/ruby_client/spec/models/system_response_spec.rb index ce621e35..8a9bc195 100644 --- a/src/ruby_client/spec/models/system_response_spec.rb +++ b/src/ruby_client/spec/models/system_response_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/system_roles_category_response_spec.rb b/src/ruby_client/spec/models/system_roles_category_response_spec.rb index 516e819c..06c2851b 100644 --- a/src/ruby_client/spec/models/system_roles_category_response_spec.rb +++ b/src/ruby_client/spec/models/system_roles_category_response_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb b/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb index 40b04035..7daedf60 100644 --- a/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb +++ b/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/system_roles_response_spec.rb b/src/ruby_client/spec/models/system_roles_response_spec.rb index 78790217..a5efb851 100644 --- a/src/ruby_client/spec/models/system_roles_response_spec.rb +++ b/src/ruby_client/spec/models/system_roles_response_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/systems_response_spec.rb b/src/ruby_client/spec/models/systems_response_spec.rb index fc3fd051..c469384f 100644 --- a/src/ruby_client/spec/models/systems_response_spec.rb +++ b/src/ruby_client/spec/models/systems_response_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/systems_spec.rb b/src/ruby_client/spec/models/systems_spec.rb index 4aa67692..7bdc69da 100644 --- a/src/ruby_client/spec/models/systems_spec.rb +++ b/src/ruby_client/spec/models/systems_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT @@ -649,6 +649,18 @@ end end + describe 'test attribute "group_tagging"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + + describe 'test attribute "group_tag_descriptions"' do + it 'should work' do + # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ + end + end + describe 'test attribute "package"' do it 'should work' do # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ diff --git a/src/ruby_client/spec/models/test_data_spec.rb b/src/ruby_client/spec/models/test_data_spec.rb index c052283e..b2aaf501 100644 --- a/src/ruby_client/spec/models/test_data_spec.rb +++ b/src/ruby_client/spec/models/test_data_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/test_results_get_spec.rb b/src/ruby_client/spec/models/test_results_get_spec.rb index f8f8dc52..731dfc9d 100644 --- a/src/ruby_client/spec/models/test_results_get_spec.rb +++ b/src/ruby_client/spec/models/test_results_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/test_results_post_spec.rb b/src/ruby_client/spec/models/test_results_post_spec.rb index 75c5331c..9c41a288 100644 --- a/src/ruby_client/spec/models/test_results_post_spec.rb +++ b/src/ruby_client/spec/models/test_results_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/test_results_response_get_spec.rb b/src/ruby_client/spec/models/test_results_response_get_spec.rb index 47c30fff..b7f2377f 100644 --- a/src/ruby_client/spec/models/test_results_response_get_spec.rb +++ b/src/ruby_client/spec/models/test_results_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/test_results_response_post_spec.rb b/src/ruby_client/spec/models/test_results_response_post_spec.rb index a73d5f04..2b0d6fc9 100644 --- a/src/ruby_client/spec/models/test_results_response_post_spec.rb +++ b/src/ruby_client/spec/models/test_results_response_post_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/test_spec.rb b/src/ruby_client/spec/models/test_spec.rb index 874a59fc..0ec91e49 100644 --- a/src/ruby_client/spec/models/test_spec.rb +++ b/src/ruby_client/spec/models/test_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/users_spec.rb b/src/ruby_client/spec/models/users_spec.rb index d1c03a3c..8542f36a 100644 --- a/src/ruby_client/spec/models/users_spec.rb +++ b/src/ruby_client/spec/models/users_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_definition_get_spec.rb b/src/ruby_client/spec/models/workflow_definition_get_spec.rb index 27cb64f4..6833ab29 100644 --- a/src/ruby_client/spec/models/workflow_definition_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_definition_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb b/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb index e798d76e..f73ddf5f 100644 --- a/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_instance_get_spec.rb b/src/ruby_client/spec/models/workflow_instance_get_spec.rb index e19c19f5..8ee4daa4 100644 --- a/src/ruby_client/spec/models/workflow_instance_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instance_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb b/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb index 6abe0e20..10384ca8 100644 --- a/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_instances_get_spec.rb b/src/ruby_client/spec/models/workflow_instances_get_spec.rb index 59885afe..d76069fd 100644 --- a/src/ruby_client/spec/models/workflow_instances_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb b/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb index 21b13310..c9282811 100644 --- a/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb b/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb index 7c666358..abc39444 100644 --- a/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/ruby_client/spec/spec_helper.rb b/src/ruby_client/spec/spec_helper.rb index d84962ee..b08125ab 100644 --- a/src/ruby_client/spec/spec_helper.rb +++ b/src/ruby_client/spec/spec_helper.rb @@ -3,7 +3,7 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.9 +The version of the OpenAPI document: v3.10 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech OpenAPI Generator version: 7.0.0-SNAPSHOT diff --git a/src/typescript_client/README.md b/src/typescript_client/README.md index 4d3d7911..2b17c933 100644 --- a/src/typescript_client/README.md +++ b/src/typescript_client/README.md @@ -1,10 +1,10 @@ -## eMASS API v3.9 Specification +## eMASS API v3.10 Specification -The `@mitre/emass_client@3.9.1` is a TypeScript/JavaScript client that utilizes [axios](https://github.com/axios/axios) +The `@mitre/emass_client@3.10.0` is a TypeScript/JavaScript client that utilizes [axios](https://github.com/axios/axios) that implements the [Enterprise Mission Assurance Support Service (eMASS)](https://disa.mil/~/media/Files/DISA/Fact-Sheets/eMASS.pdf) Representational State Transfer (REST) Application Programming Interface (API) specifications -The `@mitre/emass_client@3.9.1 npm package` can be used in the following environments: +The `@mitre/emass_client@3.10.0 npm package` can be used in the following environments: * Node.js * Webpack * Browserify @@ -61,7 +61,7 @@ navigate to the folder of your consuming project and run one of the following co _published:_ ``` -npm install @mitre/emass_client@3.9.1 --save +npm install @mitre/emass_client@3.10.0 --save ``` _unPublished (not recommended):_ @@ -74,7 +74,7 @@ npm install PATH_TO_GENERATED_PACKAGE --save Before accessing any of the endpoints provided by the @mitre/emass_client, we need to configure common axios settings. ### Axios Configuration -All calls utilizing the @mitre/emass_client@3.9.1 need to initialize axios as follows: +All calls utilizing the @mitre/emass_client@3.10.0 need to initialize axios as follows: ```typescript // Load the necessary modules diff --git a/src/typescript_client/api.ts b/src/typescript_client/api.ts index eebc6584..78fe3ae9 100644 --- a/src/typescript_client/api.ts +++ b/src/typescript_client/api.ts @@ -4,7 +4,7 @@ * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.9 + * The version of the OpenAPI document: v3.10 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -1023,6 +1023,74 @@ export interface ControlsResponsePut { */ 'data'?: Array; } +/** + * + * @export + * @interface DashboardMockResponse + */ +export interface DashboardMockResponse { + /** + * + * @type {Response200} + * @memberof DashboardMockResponse + */ + 'meta'?: Response200; + /** + * + * @type {Array} + * @memberof DashboardMockResponse + */ + 'data'?: Array; + /** + * + * @type {DashboardMockResponsePagination} + * @memberof DashboardMockResponse + */ + 'pagination'?: DashboardMockResponsePagination; +} +/** + * + * @export + * @interface DashboardMockResponsePagination + */ +export interface DashboardMockResponsePagination { + /** + * + * @type {number} + * @memberof DashboardMockResponsePagination + */ + 'totalCount'?: number; + /** + * + * @type {number} + * @memberof DashboardMockResponsePagination + */ + 'totalPages'?: number; + /** + * + * @type {number} + * @memberof DashboardMockResponsePagination + */ + 'pageIndex'?: number; + /** + * + * @type {number} + * @memberof DashboardMockResponsePagination + */ + 'pageSize'?: number; + /** + * + * @type {string} + * @memberof DashboardMockResponsePagination + */ + 'prevPageUrl'?: string; + /** + * + * @type {string} + * @memberof DashboardMockResponsePagination + */ + 'nextPageUrl'?: string; +} /** * * @export @@ -1320,6 +1388,91 @@ export interface MilestonesRequiredPut { */ 'scheduledCompletionDate': number; } +/** + * + * @export + * @interface MockObject + */ +export interface MockObject { + /** + * [Required] Organization/Office represented. 100 Characters. + * @type {string} + * @memberof MockObject + */ + 'pocOrganization'?: string; + /** + * [Required] List of resources used. 250 Characters. + * @type {string} + * @memberof MockObject + */ + 'resources'?: string; + /** + * [Read-Only] Owning organization of the system record. Values match the eMASS instance Organizational Hierarchy. + * @type {string} + * @memberof MockObject + */ + 'owningOrganization'?: string | null; + /** + * [Read-only] Secondary organization that owns the system record (i.e. Sub-Organization-level. + * @type {string} + * @memberof MockObject + */ + 'secondaryOrganization'?: string | null; + /** + * [Conditional] First name of POC. 100 Characters. + * @type {string} + * @memberof MockObject + */ + 'pocFirstName'?: string; + /** + * [Conditional] Last name of POC. 100 Characters. + * @type {string} + * @memberof MockObject + */ + 'pocLastName'?: string; + /** + * [Conditional] Email address of POC. 100 Characters. + * @type {string} + * @memberof MockObject + */ + 'pocEmail'?: string; + /** + * [Conditional] Phone number of POC (area code) ***-**** format. 100 Characters. + * @type {string} + * @memberof MockObject + */ + 'pocPhoneNumber'?: string; + /** + * [Conditional] Required for approved items. Values include the following options: (Very Low, Low, Moderate,High,Very High) + * @type {string} + * @memberof MockObject + */ + 'severity'?: string; + /** + * [Conditional] Required for ongoing and completed POA&M items. Unix time format. + * @type {number} + * @memberof MockObject + */ + 'scheduledCompletionDate'?: number | null; + /** + * [Conditional] Field is required for completed POA&M items. Unix time format. + * @type {number} + * @memberof MockObject + */ + 'completionDate'?: number; + /** + * [Conditional] Field is required for completed and risk accepted POA&M items. 2000 Characters + * @type {string} + * @memberof MockObject + */ + 'comments'?: string; + /** + * [Conditional] Optionally used in PUT to delete milestones when updating a POA&M. + * @type {boolean} + * @memberof MockObject + */ + 'isActive'?: boolean; +} /** * * @export @@ -3158,6 +3311,18 @@ export interface Systems { * @memberof Systems */ 'isFISMAReportable'?: boolean | null; + /** + * [Read-Only] System Tags for enterprise level, to include CIO and CISO, tracking efforts. VA only. + * @type {string} + * @memberof Systems + */ + 'groupTagging'?: string | null; + /** + * [Read-Only] System Tag explanation(s) for enterprise level, to include CIO and CISO, tracking efforts. VA only. + * @type {string} + * @memberof Systems + */ + 'groupTagDescriptions'?: string | null; /** * * @type {Array} @@ -3670,10 +3835,10 @@ export interface WorkflowInstanceResponseGet { 'meta'?: Response200; /** * - * @type {Array} + * @type {WorkflowInstanceGet} * @memberof WorkflowInstanceResponseGet */ - 'data'?: Array; + 'data'?: WorkflowInstanceGet; } /** * @@ -5198,7 +5363,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur return { /** * Get system Artifacts details information. - * @summary Get dashboard information + * @summary System Artifacts Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5259,7 +5424,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system Artifacts summary information. - * @summary Get dashboard information + * @summary System Artifacts Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5320,7 +5485,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get systems assessement procdures details dashboard information. - * @summary Get dashboard information + * @summary System Assessment Procedures Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5381,7 +5546,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system associations details dashboard information. - * @summary Get dashboard information + * @summary System Associations Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5431,6 +5596,67 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system CONMON integration status dashboard information. + * @summary System CONMON Integration Status + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemCommonIntegrationStatusSummary: async (orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemCommonIntegrationStatusSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-conmon-integration-status-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (excludeinherited !== undefined) { + localVarQueryParameter['excludeinherited'] = excludeinherited; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + setSearchParams(localVarUrlObj, localVarQueryParameter); let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; @@ -5442,7 +5668,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get systems control compliance summary dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5503,7 +5729,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system hardware details dashboard information. - * @summary Get dashboard information + * @summary System Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5564,7 +5790,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5625,7 +5851,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system POA&Ms details dashboard information. - * @summary Get dashboard information + * @summary System POA&M Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5686,7 +5912,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get systems POA&Ms summary dashboard information. - * @summary Get dashboard information + * @summary System POA&M Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5747,7 +5973,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system ports and protocols details dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5808,7 +6034,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system ports and protocols summary dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5869,7 +6095,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get user system privacy summary dashboard information. - * @summary Get dashboard information + * @summary System Privacy Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5930,7 +6156,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get systems security control details dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -5991,7 +6217,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system sensor hardware details dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6052,7 +6278,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get system sensor hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6102,6 +6328,128 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system software details dashboard information. + * @summary System Software Details + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSoftwareDetails: async (orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemSoftwareDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-software-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (excludeinherited !== undefined) { + localVarQueryParameter['excludeinherited'] = excludeinherited; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system software summary dashboard information. + * @summary System Software Summary + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSoftwareSummary: async (orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemSoftwareSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-software-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (excludeinherited !== undefined) { + localVarQueryParameter['excludeinherited'] = excludeinherited; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + setSearchParams(localVarUrlObj, localVarQueryParameter); let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; @@ -6113,7 +6461,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get systems status detail dashboard information. - * @summary Get dashboard information + * @summary System Status Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6174,7 +6522,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get user system assignments details dashboard information. - * @summary Get dashboard information + * @summary User System Assignments Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6235,7 +6583,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA OMB-FISMA SAOP summary dashboard information. - * @summary Get dashboard information + * @summary VA OMB FISMA SAOP Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6296,7 +6644,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system A2.0 summary dashboard information. - * @summary Get dashboard information + * @summary VA System A2.0 Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6357,7 +6705,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system A&A summary dashboard information. - * @summary Get dashboard information + * @summary VA System A&A Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6418,7 +6766,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system FISMA inventory crypto summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Crypto Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6479,7 +6827,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system FISMA inventory summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6540,7 +6888,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system P.L. 109 reporting summary dashboard information. - * @summary Get dashboard information + * @summary VA System P.L. 109 Reporting Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6601,7 +6949,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system threat architecture details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Architecture Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6662,7 +7010,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system threat risk summary dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Risks Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6723,7 +7071,7 @@ export const DashboardsApiAxiosParamCreator = function (configuration?: Configur }, /** * Get VA system threat source details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Sources Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6794,7 +7142,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { return { /** * Get system Artifacts details information. - * @summary Get dashboard information + * @summary System Artifacts Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6808,7 +7156,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system Artifacts summary information. - * @summary Get dashboard information + * @summary System Artifacts Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6822,7 +7170,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get systems assessement procdures details dashboard information. - * @summary Get dashboard information + * @summary System Assessment Procedures Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6836,7 +7184,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system associations details dashboard information. - * @summary Get dashboard information + * @summary System Associations Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6848,9 +7196,23 @@ export const DashboardsApiFp = function(configuration?: Configuration) { const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemAssociationsDetails(orgId, excludeinherited, pageIndex, pageSize, options); return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); }, + /** + * Get system CONMON integration status dashboard information. + * @summary System CONMON Integration Status + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemCommonIntegrationStatusSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemCommonIntegrationStatusSummary(orgId, excludeinherited, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, /** * Get systems control compliance summary dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6864,7 +7226,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system hardware details dashboard information. - * @summary Get dashboard information + * @summary System Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6878,7 +7240,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6892,7 +7254,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system POA&Ms details dashboard information. - * @summary Get dashboard information + * @summary System POA&M Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6906,7 +7268,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get systems POA&Ms summary dashboard information. - * @summary Get dashboard information + * @summary System POA&M Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6920,7 +7282,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system ports and protocols details dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6934,7 +7296,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system ports and protocols summary dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6948,7 +7310,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get user system privacy summary dashboard information. - * @summary Get dashboard information + * @summary System Privacy Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6962,7 +7324,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get systems security control details dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6976,7 +7338,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system sensor hardware details dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -6990,7 +7352,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get system sensor hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7002,9 +7364,37 @@ export const DashboardsApiFp = function(configuration?: Configuration) { const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemSensorHardwareSummary(orgId, excludeinherited, pageIndex, pageSize, options); return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); }, + /** + * Get system software details dashboard information. + * @summary System Software Details + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemSoftwareDetails(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemSoftwareDetails(orgId, excludeinherited, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get system software summary dashboard information. + * @summary System Software Summary + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemSoftwareSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemSoftwareSummary(orgId, excludeinherited, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, /** * Get systems status detail dashboard information. - * @summary Get dashboard information + * @summary System Status Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7018,7 +7408,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get user system assignments details dashboard information. - * @summary Get dashboard information + * @summary User System Assignments Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7032,7 +7422,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA OMB-FISMA SAOP summary dashboard information. - * @summary Get dashboard information + * @summary VA OMB FISMA SAOP Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7046,7 +7436,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system A2.0 summary dashboard information. - * @summary Get dashboard information + * @summary VA System A2.0 Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7060,7 +7450,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system A&A summary dashboard information. - * @summary Get dashboard information + * @summary VA System A&A Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7074,7 +7464,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system FISMA inventory crypto summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Crypto Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7088,7 +7478,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system FISMA inventory summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7102,7 +7492,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system P.L. 109 reporting summary dashboard information. - * @summary Get dashboard information + * @summary VA System P.L. 109 Reporting Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7116,7 +7506,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system threat architecture details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Architecture Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7130,7 +7520,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system threat risk summary dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Risks Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7144,7 +7534,7 @@ export const DashboardsApiFp = function(configuration?: Configuration) { }, /** * Get VA system threat source details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Sources Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7168,7 +7558,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas return { /** * Get system Artifacts details information. - * @summary Get dashboard information + * @summary System Artifacts Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7181,7 +7571,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system Artifacts summary information. - * @summary Get dashboard information + * @summary System Artifacts Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7194,7 +7584,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get systems assessement procdures details dashboard information. - * @summary Get dashboard information + * @summary System Assessment Procedures Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7207,7 +7597,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system associations details dashboard information. - * @summary Get dashboard information + * @summary System Associations Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7218,9 +7608,22 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas getSystemAssociationsDetails(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { return localVarFp.getSystemAssociationsDetails(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(axios, basePath)); }, + /** + * Get system CONMON integration status dashboard information. + * @summary System CONMON Integration Status + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemCommonIntegrationStatusSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemCommonIntegrationStatusSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, /** * Get systems control compliance summary dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7233,7 +7636,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system hardware details dashboard information. - * @summary Get dashboard information + * @summary System Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7246,7 +7649,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7259,7 +7662,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system POA&Ms details dashboard information. - * @summary Get dashboard information + * @summary System POA&M Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7272,7 +7675,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get systems POA&Ms summary dashboard information. - * @summary Get dashboard information + * @summary System POA&M Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7285,7 +7688,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system ports and protocols details dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7298,7 +7701,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system ports and protocols summary dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7311,7 +7714,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get user system privacy summary dashboard information. - * @summary Get dashboard information + * @summary System Privacy Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7324,7 +7727,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get systems security control details dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7337,7 +7740,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system sensor hardware details dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7350,7 +7753,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get system sensor hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7361,9 +7764,35 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas getSystemSensorHardwareSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { return localVarFp.getSystemSensorHardwareSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(axios, basePath)); }, + /** + * Get system software details dashboard information. + * @summary System Software Details + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSoftwareDetails(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemSoftwareDetails(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get system software summary dashboard information. + * @summary System Software Summary + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSoftwareSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemSoftwareSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, /** * Get systems status detail dashboard information. - * @summary Get dashboard information + * @summary System Status Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7376,7 +7805,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get user system assignments details dashboard information. - * @summary Get dashboard information + * @summary User System Assignments Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7389,7 +7818,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA OMB-FISMA SAOP summary dashboard information. - * @summary Get dashboard information + * @summary VA OMB FISMA SAOP Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7402,7 +7831,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system A2.0 summary dashboard information. - * @summary Get dashboard information + * @summary VA System A2.0 Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7415,7 +7844,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system A&A summary dashboard information. - * @summary Get dashboard information + * @summary VA System A&A Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7428,7 +7857,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system FISMA inventory crypto summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Crypto Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7441,7 +7870,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system FISMA inventory summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7454,7 +7883,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system P.L. 109 reporting summary dashboard information. - * @summary Get dashboard information + * @summary VA System P.L. 109 Reporting Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7467,7 +7896,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system threat architecture details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Architecture Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7480,7 +7909,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system threat risk summary dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Risks Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7493,7 +7922,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas }, /** * Get VA system threat source details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Sources Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7516,7 +7945,7 @@ export const DashboardsApiFactory = function (configuration?: Configuration, bas export class DashboardsApi extends BaseAPI { /** * Get system Artifacts details information. - * @summary Get dashboard information + * @summary System Artifacts Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7531,7 +7960,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system Artifacts summary information. - * @summary Get dashboard information + * @summary System Artifacts Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7546,7 +7975,7 @@ export class DashboardsApi extends BaseAPI { /** * Get systems assessement procdures details dashboard information. - * @summary Get dashboard information + * @summary System Assessment Procedures Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7561,7 +7990,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system associations details dashboard information. - * @summary Get dashboard information + * @summary System Associations Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7574,9 +8003,24 @@ export class DashboardsApi extends BaseAPI { return DashboardsApiFp(this.configuration).getSystemAssociationsDetails(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); } + /** + * Get system CONMON integration status dashboard information. + * @summary System CONMON Integration Status + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemCommonIntegrationStatusSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemCommonIntegrationStatusSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + /** * Get systems control compliance summary dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7591,7 +8035,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system hardware details dashboard information. - * @summary Get dashboard information + * @summary System Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7606,7 +8050,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7621,7 +8065,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system POA&Ms details dashboard information. - * @summary Get dashboard information + * @summary System POA&M Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7636,7 +8080,7 @@ export class DashboardsApi extends BaseAPI { /** * Get systems POA&Ms summary dashboard information. - * @summary Get dashboard information + * @summary System POA&M Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7651,7 +8095,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system ports and protocols details dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7666,7 +8110,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system ports and protocols summary dashboard information. - * @summary Get dashboard information + * @summary System Ports/Protocols Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7681,7 +8125,7 @@ export class DashboardsApi extends BaseAPI { /** * Get user system privacy summary dashboard information. - * @summary Get dashboard information + * @summary System Privacy Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7696,7 +8140,7 @@ export class DashboardsApi extends BaseAPI { /** * Get systems security control details dashboard information. - * @summary Get dashboard information + * @summary System Control Compliance Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7711,7 +8155,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system sensor hardware details dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7726,7 +8170,7 @@ export class DashboardsApi extends BaseAPI { /** * Get system sensor hardware summary dashboard information. - * @summary Get dashboard information + * @summary System Sensor Hardware Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7739,9 +8183,39 @@ export class DashboardsApi extends BaseAPI { return DashboardsApiFp(this.configuration).getSystemSensorHardwareSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); } + /** + * Get system software details dashboard information. + * @summary System Software Details + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemSoftwareDetails(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemSoftwareDetails(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get system software summary dashboard information. + * @summary System Software Summary + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemSoftwareSummary(orgId: number, excludeinherited?: boolean, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemSoftwareSummary(orgId, excludeinherited, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + /** * Get systems status detail dashboard information. - * @summary Get dashboard information + * @summary System Status Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7756,7 +8230,7 @@ export class DashboardsApi extends BaseAPI { /** * Get user system assignments details dashboard information. - * @summary Get dashboard information + * @summary User System Assignments Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7771,7 +8245,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA OMB-FISMA SAOP summary dashboard information. - * @summary Get dashboard information + * @summary VA OMB FISMA SAOP Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7786,7 +8260,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system A2.0 summary dashboard information. - * @summary Get dashboard information + * @summary VA System A2.0 Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7801,7 +8275,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system A&A summary dashboard information. - * @summary Get dashboard information + * @summary VA System A&A Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7816,7 +8290,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system FISMA inventory crypto summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Crypto Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7831,7 +8305,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system FISMA inventory summary dashboard information. - * @summary Get dashboard information + * @summary VA System FISMA Inventory Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7846,7 +8320,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system P.L. 109 reporting summary dashboard information. - * @summary Get dashboard information + * @summary VA System P.L. 109 Reporting Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7861,7 +8335,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system threat architecture details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Architecture Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7876,7 +8350,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system threat risk summary dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Risks Summary * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. @@ -7891,7 +8365,7 @@ export class DashboardsApi extends BaseAPI { /** * Get VA system threat source details dashboard information. - * @summary Get dashboard information + * @summary VA System Threat Sources Details * @param {number} orgId **Organization Id**: The unique organization identifier. * @param {boolean} [excludeinherited] **Exclude Inherited**: If no value is specified, the default returns false to include inherited data. * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. diff --git a/src/typescript_client/base.ts b/src/typescript_client/base.ts index 0a87fb7b..ed16e6f5 100644 --- a/src/typescript_client/base.ts +++ b/src/typescript_client/base.ts @@ -4,7 +4,7 @@ * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.9 + * The version of the OpenAPI document: v3.10 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/common.ts b/src/typescript_client/common.ts index da33a990..cd162299 100644 --- a/src/typescript_client/common.ts +++ b/src/typescript_client/common.ts @@ -4,7 +4,7 @@ * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.9 + * The version of the OpenAPI document: v3.10 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/configuration.ts b/src/typescript_client/configuration.ts index d03ee7ec..bafe6a36 100644 --- a/src/typescript_client/configuration.ts +++ b/src/typescript_client/configuration.ts @@ -4,7 +4,7 @@ * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.9 + * The version of the OpenAPI document: v3.10 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/index.ts b/src/typescript_client/index.ts index 99e48e22..84265ba1 100644 --- a/src/typescript_client/index.ts +++ b/src/typescript_client/index.ts @@ -4,7 +4,7 @@ * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.9 + * The version of the OpenAPI document: v3.10 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/package.json b/src/typescript_client/package.json index ceda897c..fce02c69 100644 --- a/src/typescript_client/package.json +++ b/src/typescript_client/package.json @@ -1,6 +1,6 @@ { "name": "@mitre/emass_client", - "version": "3.9.1", + "version": "3.10.0", "description": "OpenAPI client for @mitre/emass_client", "repository": { "type": "git",