This is based on the CCE config dev template, outfitted with a sample GitHub Actions workflow.
Notes:
- This codebase is the canonical repo for tenant(s).
- The actual artifact uploaded to a tenant is produced as part of the build step.
- It's easy to generate a local copy of the artifact to be deployed by running the
archive.sh
script. - It's easy to manually deploy that artifact with the
deploy.sh
script. archive.sh
anddeploy.sh
are used by the GitHub Actions workflow.- The GitHub Actions workflow posts a copy of the deployed config.zip on every build.
Once you have a target tenant and created a GitHub repo with this codebase (see detailed steps below), you can update your Java code as needed, run tests, modify your canonical JSON config, etc.; then commit your changes and push them up, triggering a build and deploy to your target tenant. You can pull down what's on the tenant for reference purposes, which by default is placed in the (non-committed) socotra-config
directory.