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

Add ability to pass Serial Number and Common Name #15

Merged
merged 2 commits into from
Sep 26, 2024

Conversation

ellgreen
Copy link
Contributor

@ellgreen ellgreen commented Sep 19, 2024

Thanks for this library, we're finding it useful! 😄

Just wanted to add the ability to set a serial number and common name when creating new key pairs.

Currently we have some tests that need distinct values for these which is making it a little bit harder to test what we need.

Summary by CodeRabbit

  • New Features
    • Added support for SerialNumber and CommonName in certificate generation, enhancing configurability.
  • Bug Fixes
    • Improved handling of serial numbers and common names in the certificate generation process.
  • Tests
    • Expanded test coverage for KeyPairConfig to validate new features and ensure correct functionality, including new test scenarios for serial numbers and common names.

Copy link

coderabbitai bot commented Sep 19, 2024

Walkthrough

The changes introduce new fields to the KeyPairConfig struct in the testcerts package, specifically SerialNumber and CommonName, enhancing its ability to manage certificate attributes. The NewKeyPairFromConfig method in the CertificateAuthority struct is modified to utilize these new fields, allowing for better configurability in certificate generation. Additionally, new test cases are added to validate the handling of these fields, improving the overall test coverage for the functionality related to key pair configuration.

Changes

Files Change Summary
kpconfig.go, testcerts.go Added SerialNumber *big.Int and CommonName string to KeyPairConfig. Modified NewKeyPairFromConfig to set CommonName and use big.NewInt(42) for SerialNumber if not provided.
testcerts_test.go Added test cases in TestKeyPairConfig for serial number and common name. Added TestFullFlow for comprehensive attribute validation.

Poem

In the meadow where bunnies play,
New fields sprout in a bright array.
Serial numbers and names so grand,
Certificates crafted by gentle hand.
Hopping with joy, we celebrate,
For key pairs now can truly relate! 🐰✨


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 22dbdc6 and 129213a.

Files selected for processing (1)
  • testcerts.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • testcerts.go

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Outside diff range and nitpick comments (1)
testcerts.go (1)

Line range hint 166-175: Return the error if there is an error converting the private key to a PEM block.

The NewKeyPairFromConfig method does not return an error if there is an error converting the private key to a PEM block. Instead, it returns the error as part of the KeyPair struct. This could lead to unexpected behavior if the error is not checked by the caller.

Consider returning the error if there is an error converting the private key to a PEM block:

kp.privateKey, err = keyToPemBlock(privateKey)
if err != nil {
    return nil, fmt.Errorf("could not convert private key to pem block: %w", err)
}
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0fbb387 and 22dbdc6.

Files selected for processing (3)
  • kpconfig.go (2 hunks)
  • testcerts.go (2 hunks)
  • testcerts_test.go (4 hunks)
Additional comments not posted (5)
kpconfig.go (2)

5-5: LGTM!

The "math/big" import is necessary to support the SerialNumber field of type *big.Int. The import statement is correct.


27-28: LGTM!

The addition of the SerialNumber and CommonName fields to the KeyPairConfig struct is well-implemented:

  • The field names are clear and descriptive.
  • The field types are appropriate: *big.Int for SerialNumber allows for optional values, and string is suitable for CommonName.
  • The fields are correctly exported (capitalized) for access from outside the package.
  • The field comments provide sufficient documentation about their purpose.

These changes enhance the functionality of the KeyPairConfig struct without altering existing logic or control flow, making them a safe and valuable addition to the codebase.

Also applies to: 30-31

testcerts.go (1)

166-166: LGTM!

The changes to the NewKeyPairFromConfig method improve the functionality of the certificate generation process by allowing for more dynamic input while maintaining sensible defaults. The changes are backwards compatible and do not introduce any breaking changes.

Also applies to: 170-170

testcerts_test.go (2)

Line range hint 277-337: LGTM!

The new test cases for serial number and common name look good. They cover the scenarios where these values are provided in the KeyPairConfig and verify that the generated certificate contains the correct values.

The test cases follow the existing patterns and best practices in the file.


375-385: Looks good!

The new test case in TestFullFlow covers the scenario where multiple attributes are provided in the KeyPairConfig. It follows the existing patterns and does not introduce any new logic or assertions.

The addition of this test case improves the coverage of the end-to-end flow and ensures that the system behaves as expected when all relevant fields are populated.

testcerts.go Outdated Show resolved Hide resolved
Copy link
Owner

@madflojo madflojo left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! Sorry I didn’t notice this PR earlier.

@madflojo madflojo merged commit 5cf4d0f into madflojo:main Sep 26, 2024
3 checks passed
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.

2 participants