Update deprecated ghcr.io image reference to public.ecr.aws - #152
Update deprecated ghcr.io image reference to public.ecr.aws#152luisina-santos wants to merge 1 commit into
Conversation
README.md referenced this connector's image via ghcr.io/conductorone; container images are now published to public.ecr.aws/conductorone instead. Only this connector's own image reference was updated. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
| ``` | ||
| docker run --rm -v $(pwd):/out -e BATON_GLOBAL_SECRET_ACCESS_KEY=awsSecretAccessKey -e BATON_GLOBAL_ACCESS_KEY_ID=awsAccessKey ghcr.io/conductorone/baton-aws:latest -f "/out/sync.c1z" | ||
| docker run --rm -v $(pwd):/out -e BATON_GLOBAL_SECRET_ACCESS_KEY=awsSecretAccessKey -e BATON_GLOBAL_ACCESS_KEY_ID=awsAccessKey public.ecr.aws/conductorone/baton-aws:latest -f "/out/sync.c1z" | ||
| docker run --rm -v $(pwd):/out ghcr.io/conductorone/baton:latest -f "/out/sync.c1z" resources |
There was a problem hiding this comment.
🟡 Suggestion: The adjacent baton CLI image on this line still points at ghcr.io/conductorone/baton:latest. If the same registry deprecation applies to the CLI image, updating it here too would keep the docker snippet internally consistent; otherwise the mixed registries in back-to-back commands may read as an oversight. Non-blocking — I can't verify from this repo whether the CLI image is published to public.ecr.aws.
Connector PR Review: Update deprecated ghcr.io image reference to public.ecr.awsBlocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0 Review SummaryThis PR changes a single documentation line, swapping the docker image reference for this connector in Security IssuesNone found. Correctness IssuesNone found. Suggestions
Prompt for AI agents |
Summary
ghcr.io/conductorone/baton-aws:latest; container images are now published topublic.ecr.aws/conductorone/baton-aws:latestinstead.Test plan
public.ecr.aws/conductorone/baton-aws:latestresolves (manifest exists) before opening this PR.🤖 Generated with Claude Code