Skip to content

Tags: bcgov/certbot

Tags

v1.0.2

Toggle v1.0.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #29 from jujaga/release/patch

Version bump Certbot to 1.0.2 and chart to 0.1.3

certbot-0.1.3

Toggle certbot-0.1.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #29 from jujaga/release/patch

Version bump Certbot to 1.0.2 and chart to 0.1.3

v1.0.1

Toggle v1.0.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #27 from BCDevOps/release/patch-bump

Version bump Certbot to 1.0.1 and chart to 0.1.2

certbot-0.1.2

Toggle certbot-0.1.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #27 from BCDevOps/release/patch-bump

Version bump Certbot to 1.0.1 and chart to 0.1.2

certbot-0.1.1

Toggle certbot-0.1.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #21 from matthieu-foucault/feat/helm-custom-role

feat(helm-chart): certbot uses least-privilege role

certbot-0.1.0

Toggle certbot-0.1.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #20 from matthieu-foucault/fix/chart-releaser-work…

…flow

Chart releaser workflow should use `azure/setup-helm@v1`

v1.0.0

Toggle v1.0.0's commit message

Verified

This commit was signed with the committer’s verified signature.
jujaga Jeremy Ho
Mass update readme documentation

This commit focuses on updating, standardizing and ordering all parameters
related to deploying and managing Certbot. By ensuring that all parameters
use the same naming scheme, it will reduce confusion on intent. As well,
we have changed the default cronjob schedule to run bi-weekly on Monday
and Thursday as opposed to running every 12 hours. Since certificates tend
to last a while, running it more frequently than twice a week is a waste
of cluster resources.

Signed-off-by: Jeremy Ho <[email protected]>