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

support for db schedule-based static role rotations #367

Closed
wants to merge 1 commit into from

Conversation

fairclothjm
Copy link
Contributor

@fairclothjm fairclothjm requested a review from a team as a code owner September 20, 2023 21:14
@fairclothjm fairclothjm added this to the v0.3.0 milestone Sep 20, 2023
@benashz benashz added dynamic Dynamic secrets enhancement New feature or request labels Sep 20, 2023
@@ -104,6 +104,11 @@ type VaultStaticCredsMetaData struct {
// "time to live". This value is compared to the LastVaultRotation to
// determine if a password needs to be rotated
RotationPeriod int64 `json:"rotationPeriod"`
// RotationSchedule is a "chron style" string representing the allowed
Copy link

Choose a reason for hiding this comment

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

Suggested change
// RotationSchedule is a "chron style" string representing the allowed
// RotationSchedule is a "cron style" string representing the allowed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ha, woops!

@@ -226,13 +226,19 @@ spec:
be rotated
format: int64
type: integer
rotationSchedule:
description: RotationSchedule is a "chron style" string representing
Copy link

Choose a reason for hiding this comment

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

Suggested change
description: RotationSchedule is a "chron style" string representing
description: RotationSchedule is a "cron style" string representing

@@ -226,13 +226,19 @@ spec:
be rotated
format: int64
type: integer
rotationSchedule:
description: RotationSchedule is a "chron style" string representing
Copy link

Choose a reason for hiding this comment

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

Suggested change
description: RotationSchedule is a "chron style" string representing
description: RotationSchedule is a "cron style" string representing

@@ -543,6 +543,7 @@ _Appears in:_
| --- | --- |
| `lastVaultRotation` _integer_ | LastVaultRotation represents the last time Vault rotated the password |
| `rotationPeriod` _integer_ | RotationPeriod is number in seconds between each rotation, effectively a "time to live". This value is compared to the LastVaultRotation to determine if a password needs to be rotated |
| `rotationSchedule` _string_ | RotationSchedule is a "chron style" string representing the allowed schedule for each rotation. e.g. "1 0 * * *" would rotate at one minute past midnight (00:01) every day. |
Copy link

Choose a reason for hiding this comment

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

Suggested change
| `rotationSchedule` _string_ | RotationSchedule is a "chron style" string representing the allowed schedule for each rotation. e.g. "1 0 * * *" would rotate at one minute past midnight (00:01) every day. |
| `rotationSchedule` _string_ | RotationSchedule is a "cron style" string representing the allowed schedule for each rotation. e.g. "1 0 * * *" would rotate at one minute past midnight (00:01) every day. |

@fairclothjm
Copy link
Contributor Author

Closing in favor of #369 so that we can use a Jira-named branch and revert the integration test changes until we have TFVP support. We will incorporate the suggestions by @swenson in the new PR. Thanks!

@fairclothjm fairclothjm deleted the database-static-role-rotation-schedule branch September 21, 2023 20:47
@benashz benashz removed this from the v0.3.0 milestone Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dynamic Dynamic secrets enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants