You mentioned you want to replace deprecated snippets with a new snippet. I'm assuming that this is the new one and you're going to then replace the snippets in docs to include the new one, then post another PR deleting the old ones?

@m-strzelczyk

My understanding is that to ensure that the docs remain viable, there is sometimes a multi-phase process to update the docs. I don't yet have a full handle on all the parts and pieces of that process and when they apply. But in essence, this Draft PR has the new content that I want to add to the docs (and most importantly want feedback on).

I will either remove the deprecated snippet in this same PR or in another PR according to best practice as soon as I understand it.

Yes, that is correct :)

This sample looks good, we can do this in steps - first add this, then a new PR to continue.

Also, it would be nice to have some automated tests - can you add them?

Here is the summary of changes.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment

@m-strzelczyk
I added a test that is similar to the test used to assess the deprecated snippet.
All tests/checks pass.