Skip to content
This repository has been archived by the owner on Mar 19, 2022. It is now read-only.

An example of utilizing JupiterOne for change management.

Notifications You must be signed in to change notification settings

JupiterOne-Archives/change-management-example

Repository files navigation

JupiterOne Change Management Example

This project exemplifies usage of the JupiterOne change management client in a CICD pipeline by regulating changes to itself.

For more information on how JupiterOne can protect your production environment from malicious, vulnerable, or unreviewed code, please check out the JupiterOne documentation.

Prerequisites

To obtain a JupiterOne API token, you'll first need a JupiterOne account. Start your free trial at jupiterone.com!

Utilizing the code review features of JupiterOne requires a version control integration that supports the feature. Currently, JupiterOne has integrations with Bitbucket and GitHub. To set up one of these integrations, follow the integration "Getting Started" instructions on the support site.

Once you have an account, you can create an API token. The JupiterOne support site has detailed instructions.

You obviously don't want to commit this key to your repository, so you'll need to encrypt it. Travis makes this easy with its encrypt-file command. Read more about it in the Travis documentation.

About

An example of utilizing JupiterOne for change management.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published