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.

Sign up for GitHub

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

Jump to bottom

HPCC-30409 Support HashiCorp vault auth using client certificates #17850

Merged
merged 1 commit into from Oct 5, 2023
Merged

HPCC-30409 Support HashiCorp vault auth using client certificates #17850

merged 1 commit into from Oct 5, 2023

Conversation

afishbeck
Copy link
Member

@afishbeck afishbeck commented Oct 1, 2023 •
edited

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

@afishbeck
HPCC-30409 Support HashiCorp vault auth using client certificates
c53a237 
Signed-off-by: Anthony Fishbeck <anthony.fishbeck@lexisnexis.com>
@github-actions
Copy link

github-actions bot commented Oct 1, 2023

https://track.hpccsystems.com/browse/HPCC-30409
Jira updated

@afishbeck
Copy link
Member Author

@ghalliday this will get the optional new feature out there for integration testing with the corporate HCP vault so that we can work on the opinionated terraform support. This will make managing HCP Vault auth far easier than when using approle auth.

ghalliday
ghalliday approved these changes Oct 2, 2023
View reviewed changes
Copy link
Member

@ghalliday ghalliday left a comment

Choose a reason for hiding this comment

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

As far as I understand it it looks good. Talking tomorrow will help clarify some details.

@ghalliday ghalliday merged commit 1dd6f81 into hpcc-systems:candidate-9.4.x Oct 5, 2023
49 of 51 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ghalliday ghalliday ghalliday approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@afishbeck @ghalliday