A simple dashboard that enables navigation to the tools that have been installed
using the iteration-zero
Terraform asset or configured with igc tool -config
command line.
To add, change or delete cards on the developer dashboard edit the /public/data/links.json
file and update the information in the appropriate section.
To build the project use the following commands.
Build and develop with the server code it will open on port 3000
npm install
npm run build
npm run start
Build and develop with the client code it will open on port 3001
cd client
npm run dev
When running locally you can override default settings by putting environment variables in .env.local
and /client/.env.local
files.
Use PostMan newman
CLI
brew install newman
npm run api:test
This repository uses GitHub actions to automatically create a release whenever a change is pushed to main
. The workflow for changes should follow a typical process:
-
Create a branch (ideally in a fork of the repository)
-
Create a pull-request to merge the changes from the branch into
main
. Add a release label (major
,minor
,patch
) and a change type label (feature
,bug
,chore
) to the pull request to effect the new release tag that is generated and how the change log is generated for the release. -
Merge the pull-request into
main
. This will trigger the workflow to create the release.
This repository is also connected to the Docker Hub build image. The build process has been configured with two rules:
- Any time a change is pushed to
main
, a new image is built with thelatest
tag - Any time a new release is created for the repository, a new image is built with a tag that matches the repository tag (e.g. git tag v1.1.1 -> docker tag 1.1.1)
The terraform-tools-dashboard
module deploys the built image to the cluster. The terraform module uses the developer-dashboard
chart in the Toolkit charts
repository to deploy the image.
Each version of the module refers to a particular version of the image. As part of the release process, a GitHub Action will trigger a notification to the terraform module that a new version is available. This will trigger a process in the terraform module to get the latest version number and create a PR containing the change.