Skip to content

Version 0.9.1.50.2

Compare
Choose a tag to compare
@davidpofo davidpofo released this 27 Jan 02:37
v0.9.1.50.2
427495f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

v0.9.1.50.2 (January 26, 2021)

Adds support for OSCAL component and statement input for Compliance Apps.
(Currently only supports OSCAL JSON inputs.)
Adds statements to project upon project creation.
Keeps track of app inputs by relating them to the app version.

Includes the following schema update to the app.yaml file of Compliance Apps.
Inputs are supported in the app.yaml file with the following format:

input:
- id: <input_id> (string)
  name: <Input Name> (string)
  type: oscal (Only oscal currently supported) 
  path: <dir/filename.json> (relative file path)
  group: (optional string)

Add deployments to capture system deployments and the inventory items in each deployment.
One system has multiple deployments (e.g., dev, stage, prod) and each deployment contains an inventory of the actual endpoints/items in a deployment of the system. Systems start with several common default (empty) deployments.
The "design" deployment by convention is a special deployment to represent the system architecture.
Deployments maintain a complete version history.
Deployment inventory-items are represented as JSON data object following a scheme that is similar to OSCAL inventory-item section.
Data for deployment inventory-items is assumed to be generated outside of GovReady. It is critical that the inventory items have UUIDs prior to import. Inventory item UUIDs for the life of the instantiated inventory item.
Inventory items in an deployment can be associated with an inventory item in the "design" deployment by referencing the "design" inventory item's UUID. This enablea a virtual persistence of an inventory-item across different instances of the "same" assest, such as a virtual database server.

Feature changes

  • Add system deployments with inventory items to track instantiations of the system in real assets.
  • Add lightweight-ato to default apps so users can get started easier.
  • Add the Django admin documentation generator to provide useful documentation for developers.

UI changes

  • Add deployment index page for listing deployments associated with a system.
  • Add deployment form page for creating/editing deployments.
  • Add deployment history page.

Developer changes

  • Add .coveragerc configuration file to ensure we cover and run only tests in locally and in Circleci.
  • Add pyup.yml configuration file to have pyup.io pull requests go against develop branch.
  • Add controls.Deployment object, related routes, views, templates, and admin to track system deployments and deployment inventory items.
  • Add DeploymentForm for Deployment model.
  • New '%dict' operator for JSON/YAML output templates
  • Pass OSCAL context to JSON/YAML output templates
  • New '%dict' operator for JSON/YAML output templates
  • Pass OSCAL context to JSON/YAML output templates
  • Created a recursive method wait_for_sleep_after that wraps around other functions allowing for drastically shorter wait times necessary compared to peppering var_sleeps.
  • Update install scripts.
  • Update default and recommended local/environment.json file from first_run and install-govready-q.sh.
  • By default, set organization name to "main".
  • Add optional PIPUSER parameter to install-govready-q.sh to avoid error of running pip install with --user flag in virtual environments.
  • Comment out starting GovReady-Q server automatically because too many edge cases exist to execute that well.
  • Update install scripts.
  • Update default and recommended local/environment.json file from first_run and install-govready-q.sh.
  • By default, set organization name to "main".
  • Add optional PIPUSER parameter to install-govready-q.sh to avoid error of running pip install with --user flag in virtual environments.
  • Comment out starting GovReady-Q server automatically because too many edge cases exist to execute that well.
  • Add method get_answer guidedmodules.models.Task to easily return answers from a project tasks answers.

Data changes

  • Add lightweight-ato to default apps so users can get started easier.
  • Populate every new system with default deployments design, dev, stage, prod.
Assets 2
Loading