Some scripts have been created to ease the development workflow when deploying things in your own development environment. These aren't used in pathfinder as we typically import json
template files directly.
This document assumes that you already have minishift setup and running.
Sets up the entire tools, dev, test projects and populates them with the appropriate builds and deployments. This script will effectively get you up and running with the entire backend stack. It will also generate
.env
files on behalf of thedev
andtest
environments. You will just need to fill in the database secrets, which it gives links to in the command line output.
An interactive scripts has been written to assist in extracting audit data from the running instances in any of the environments. This can be done by using the following script and following the prompts:
This will place all of the exported/extracted data into a folder called EXTRACTED-DATA
and will be prefixed by the openshift project that it was exported from.
The data is in csv
format for easier consumption by other analysis applications.
Importable collection of useful shell functions for setting up development environments.
These scripts are still useful, however you should be able to get up and running with the script described above.
Creates the builds / pipelines for the api (Should be run in tools project)
Deploys the api components into an environment (Should be run in dev, test, prod projects)
In order to be able to pull images from a different project you will need to run the
policy
command to grant authority eg:
oc policy add-role-to-user system:image-puller system:serviceaccount:test:default -n tools
would grant the
test
projectimage-puller
abilities on thetools
project
Exposes an ingress port into the postgres service within the given project. This is now covered within the
functions.sh
script.