Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Implement CA certificate renewal #242

Merged
merged 27 commits into from
Sep 24, 2024
Merged

feat: Implement CA certificate renewal #242

merged 27 commits into from
Sep 24, 2024

Conversation

saltiyazan
Copy link
Contributor

@saltiyazan saltiyazan commented Sep 12, 2024

Description

Fixes #238, #239 and #241

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that validate the behaviour of the software
  • I validated that new and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have bumped the version of the library

@saltiyazan saltiyazan changed the title Tlseng 343 feat: Implement CA certificate renewal Sep 12, 2024
charmcraft.yaml Outdated Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@gruyaume gruyaume left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this pr is still in draft, sorry if you already planned to tackle some of those.

charmcraft.yaml Outdated Show resolved Hide resolved
charmcraft.yaml Outdated Show resolved Hide resolved
charmcraft.yaml Outdated Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
src/charm.py Show resolved Hide resolved
@saltiyazan saltiyazan force-pushed the TLSENG-343 branch 2 times, most recently from 35cb466 to 4ee5f7b Compare September 17, 2024 10:14
@saltiyazan saltiyazan marked this pull request as ready for review September 17, 2024 11:16
@saltiyazan saltiyazan requested a review from a team as a code owner September 17, 2024 11:16
@saltiyazan saltiyazan requested review from gruyaume and removed request for a team September 17, 2024 11:20
src/constants.py Outdated Show resolved Hide resolved
src/charm.py Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
src/charm.py Outdated Show resolved Hide resolved
charmcraft.yaml Outdated Show resolved Hide resolved
@saltiyazan saltiyazan force-pushed the TLSENG-343 branch 3 times, most recently from 0615c69 to d9fd25f Compare September 20, 2024 09:40
Comment on lines +132 to +142
type: string
default: 90d
description: >
Signed certificate validity.
The given value must be followed by one of: "m" for minutes, "h" for hours, "d" for days and "w" for weeks.
For example, "1m" for 1 minute, "10w" for 10 weeks.
If no units are given, the unit will be assumed as days.
Defaults to 90 days.
This value should be equal to or shorter than half the root-ca-validity.
Changing this value will trigger generation of a new CA certificate,
revoking all previously issued certificates.
Copy link
Contributor

@kayra1 kayra1 Sep 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we ever talk with Judit Novak to make sure that a minimum value of 1 minute is OK for integration tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that's good enough for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CA certificate validity configuration changed not taken into account
3 participants