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

• Build
  Getting started with the common build system and containerization.
  • Dockerized builds with a common entry point
  • Kickoff build
  • Storing docker containers
• Unit test
  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
• Deploy
  Dealing with deploying your application into Unity. Terraform scripts, tags and how to run the deployment.
  • Deployment Catalog
  • Preparing terraform scripts for automated deployment
  • Prepare initial terraform metadata (work with U-CS injection tools)
  • Common Entry Points for Deployment
  • Push-button deployment via Github Actions
• 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