Skip to content

docs(auth): improve signer docs#4180

Merged
alvarowolfx merged 6 commits intogoogleapis:mainfrom
alvarowolfx:docs-signer
Jan 8, 2026
Merged

docs(auth): improve signer docs#4180
alvarowolfx merged 6 commits intogoogleapis:mainfrom
alvarowolfx:docs-signer

Conversation

@alvarowolfx
Copy link
Copy Markdown
Collaborator

Towards #3645

@alvarowolfx alvarowolfx marked this pull request as ready for review January 7, 2026 17:18
@alvarowolfx alvarowolfx requested review from a team January 7, 2026 17:18
@codecov
Copy link
Copy Markdown

codecov bot commented Jan 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.75%. Comparing base (807266b) to head (901c0cb).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4180      +/-   ##
==========================================
- Coverage   94.76%   94.75%   -0.02%     
==========================================
  Files         186      186              
  Lines        7068     7068              
==========================================
- Hits         6698     6697       -1     
- Misses        370      371       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Member

@dbolduc dbolduc left a comment

Choose a reason for hiding this comment

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

Feel free to overrule me on showing how to create signers from service account key json directly.

I just thought Google Cloud did not like people downloading those. But if it is the way to do performant signing in practice, your example would be relevant to the top-level doc.

//! # }
//! ```
//!
//! ## Example: Creating a Signer using a Service Account Key File
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I thought we want to discourage people from downloading these

//!
//! ## Example: Creating a Signer using Application Default Credentials (ADC)
//!
//! This is the recommended way for most applications. It automatically finds credentials from the environment.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Maybe add that "If your ADC are [service account credentials], the signing will be local and not make any network requests. This can be useful in environments where network access is restricted and performance is critical."

Then we might not need the next section?

Maybe. Your call.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

If you remove the other section, this could just be:

Applications can use their Application Default Credentials (ADC) to create a signer.

If your ADC are [service account credentials], the signing will be local and not
make any network requests. This can be useful in environments where network access
is restricted and performance is critical.

# Example
// blah blah blah
// let signer = Builder::default().build_signer()?;
// blah blah blah

dbolduc
dbolduc previously approved these changes Jan 8, 2026
Copy link
Copy Markdown
Member

@dbolduc dbolduc left a comment

Choose a reason for hiding this comment

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

This PR is an obvious improvement to the docs. Feel free to merge and address any of my nits in a follow up

@alvarowolfx alvarowolfx merged commit fbb8e70 into googleapis:main Jan 8, 2026
30 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