Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

run/logging-manual: clarify Artifact Registry setup for deployment

Open Beginner friendly
#14,633 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, gcp

Research direction

Start with the Deploy section of run/logging-manual/README.md, where the build and deploy commands use gcr.io image URLs. Read the official Artifact Registry Docker setup docs to confirm the prerequisites. Done means the README either switches both commands to a REGION-docker.pkg.dev URL with setup steps linked, or keeps gcr.io and states and links the Artifact Registry requirements. Confirm the choice with a maintainer, since the issue offers both options.

Written by the indexing model from the issue text.

Description

api: run samples

The Deploy section in run/logging-manual/README.md uses gcr.io image URLs without explaining the required Artifact Registry setup.

Container Registry no longer accepts image writes. Artifact Registry-backed gcr.io URLs remain supported, but the README does not explain that prerequisite.

Suggested change: use a REGION-docker.pkg.dev image URL in both build and deploy commands, and link instructions for creating the Docker repository and configuring build permissions. Alternatively, keep gcr.io and link its Artifact Registry setup requirements.

This is based on reviewing the README and official documentation; I have not reproduced a deployment failure.

Dominant language
Jupyter Notebook
Stars
8.1k
Forks
6.7k
Avg merge
3d 23h
Merged PRs (30d)
13

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleCloudPlatform/python-docs-samples

All issues in GoogleCloudPlatform/python-docs-samples

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.