New to Unity CS

Understanding how Unity CS works can be a little overwhelming and knowing where to start can be tricky. So we have written this step by step guide to help you through onboarding your app with Unity CS.

If, after working through this guide, you are still stuck, please create a discussion topic or email: unitycsdev@jplnasagov

Security

If you application requires authentication services please read the following section as they contain import information about the operation of security services within the Unity platform

• Authorization and Authentication
  • Security Guidelines
  • API Authentication
  • UI Authentication

Application Integration

Building

Getting started with the common build system and containerization.

• Dockerized builds with a common entry point
• Kickoff build
• Storing docker containers

Unit Tests

Unit(y) testing your application prior to acceptance and deployment with Unity CS

• Common entry point for unit tests
• Kickoff unit tests
• Dockerized environment for unit testing
• Publishing test results

Publish

Information relating to central repositories and sensitive information, secrets and other items that need keeping away from prying eyes.

• Storing sensitive credentials for publishing artifacts
• Specifying a repository to house artifacts/containers

Deployment

The Unity CS deployment framework can facilitate the deployment of Unity service area components to the cloud.

The main things that service areas need to do, to integrate with the Unity CS deployment framework are as follows:

• Identify what components you need to deploy, and create terraform scripts for them
• Create an initial terraform metadata file, that identifies basic information about your deployment
• Invoke the push-button deployment via Github Actions.

Behind the scenes, the Unity CS deployment framework will:

• merge your terraform scripts with other core "supporting" terraform scripts
• perform necessary terraform transformations and required tagging
• deploy all resources (core supporting resources + your resources) to AWS.

Other related documentation:

• Deployment Catalog
• Common Entry Points for Deployment

Smoke Test

Testing your application once its deployed. Ensure that the endpoints are accessible and functioning as expected. Also, what to do if it all goes wrong.

• Common entry point for smoke tests
• Kickoff smoke tests
• Initiate rollback in case of failure

Management and Monitoring

How to keep track of your costs and resources within Unity CS.

• Cost monitoring
• Resource monitoring (aws tag based queries)
• Logging (kubernetes, system logs, application monitoring)

Teardown

Removing or rolling back your application within the Unity CS environment.

• Re-deploy previous version OR
• Terraform destroy via push-button