The Kubernetes Job consists of two containers: a git-sync container and a TechDocs container. The git-sync container is an initContainer that pulls a git repository to a shared volume so the TechDocs container has a copy of all markdown files. The TechDocs container then uses the TechDocs-cli to generate and publish your documentation to the Lighthouse S3 bucket.
-name:Create TechDocs Jobuses:department-of-veterans-affairs/lighthouse-github-actions/.github/actions/techdocs-webhook@latestwith:# Owner and repository where the documentation lives (e.g. department-of-veterans-affairs/lighthouse-developer-portal)# Default: ${{ github.repository }}repository:''# Repo branch to validate/publish documentation; use ${{ github.ref_name }} to specify the branch used for the workflow dispatch# Defaults to repository's default branchbranch:''# Name of Entity descriptor file; used to create Entity path (i.e. namespace/kind/name)# Default: 'catalog-info.yaml'descriptor-file:''# Personal Access Token used for TechDocs Webhook# Scopes: Repotoken:''# Deploy to gh-pages; only include if you want to publish docs externally to GitHub (github.io)# Default: falsegh-pages:true|false# Flag for enabling/disabling TechDocs for production# Default: trueenable-production:true|false
# Example workflowname:Publish Documentationon:push:branches:[main]paths:['**/docs/*','**/mkdocs.yaml']# Additionally, using '**/*.md' will check all '.md' files for changes including in /docsjobs:create-techdocs:runs-on:ubuntu-lateststeps:-uses:actions/checkout@v2-name:Techdocs webhookuses:department-of-veterans-affairs/lighthouse-github-actions/.github/actions/techdocs-webhook@mainwith:repository:${{ github.repository }}token:${{ secrets.PAT }}branch:${{ github.ref_name }}