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

Feature/add metadata credentials provider #12

Merged

Conversation

shmel1k
Copy link
Member

@shmel1k shmel1k commented Jul 5, 2024

Implemented authentication via IAM Metadata and IAM ServiceAccount file

@shmel1k shmel1k force-pushed the feature/add_metadata_credentials_provider branch 2 times, most recently from 223097e to 6deb722 Compare July 6, 2024 13:37
@shmel1k shmel1k force-pushed the feature/add_metadata_credentials_provider branch from da2e19a to d56fdf7 Compare July 6, 2024 13:47
Copy link
Contributor

@Jorres Jorres left a comment

Choose a reason for hiding this comment

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

No tests makes Egor sad. But oh well.

I would expect an e2e test:

  1. prepare a local process answering on metadata endpoint (the similar idea as in YDB CMS mock, in this repo, but much simpler, only have to answer to one type of request)
  2. add DEBUG level log that will print received IAM token (of course masked)
  3. build a binary, launch a binary with IAM flags and check app logs for mocked token

pkg/client/auth/credentials/metadata.go Show resolved Hide resolved
@shmel1k shmel1k merged commit c1efc1d into ydb-platform:master Jul 8, 2024
5 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.

3 participants