powerdns/PowerDNS Push Documentation Custom Github Action
Build mkdocs-style documentation and push to AWS S3 Bucket
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Feb 3, 2026
- License
- None
Pinned Snippet
uses: powerdns/pdns-publish-docs-action@ff79e0f327a1aa0d14781da6ff031ca66cdecccf # v1.1.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| aws_access_key_id | The AWS S3 access key id | yes | — |
| aws_secret_access_key | The AWS S3 secret access key | yes | — |
| aws_region | The AWS region where the bucket is located | yes | — |
| aws_s3_bucket | The name of the S3 bucket used for documentation | yes | — |
| aws_cloudfront_distribution_id | The CloudFront distribution ID (used to invalidate the cache so that the new content is immediately available) | yes | — |
| version_string | The version of the docs. Should be a semver-style version string. Required if version_control is true | no | — |
| mkdocs_file | The location of the mkdocs.yml file - required if build_docs is true | no | — |
| bucket_subdir | The sub directory (under bucket_dir) of the documentation bucket to copy the documentation to. Only allowed if bucket_dir is not empty. | no | — |
| bucket_dir | The directory of the documentation bucket to copy the documentation to | no | docs.powerdns.com |
| build_docs | Whether to build the docs using mkdocs, or just use an existing directory with the built docs in. If false, you must provide docs_dir input | no | true |
| docs_dir | The location of an existing directory containing the built docs to be copied to S3 - required if build_docs is false | no | — |
| version_control | Whether to create multiple versions of the documentation in subdirectories and a versions.json file at the root. Cannot be true if build_docs is false | no | true |
Outputs
no outputs