Update deprecated ghcr.io image reference to public.ecr.aws - #29
Update deprecated ghcr.io image reference to public.ecr.aws#29luisina-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_USERNAME=jamfUsername BATON_PASSWORD=jamfPassword BATON_INSTANCE_URL=https://jamfProServerUrl.example.com ghcr.io/conductorone/baton-jamf:latest -f "/out/sync.c1z" | ||
| docker run --rm -v $(pwd):/out -e BATON_USERNAME=jamfUsername BATON_PASSWORD=jamfPassword BATON_INSTANCE_URL=https://jamfProServerUrl.example.com public.ecr.aws/conductorone/baton-jamf: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 very next line still pulls the baton CLI from ghcr.io/conductorone/baton:latest. The PR description scopes this change to this connector's own image, so this may be intentional — but if the baton CLI image has also moved to public.ecr.aws, updating both here keeps the copy-paste docker block working end to end.
Connector PR Review: Update deprecated ghcr.io image reference to public.ecr.awsBlocking Issues: 0 | Suggestions: 1 | Threads Resolved: 0 Review SummaryThe full PR diff was scanned for security and correctness: it is a single-line README change swapping this connector's image reference from Security IssuesNone found. Correctness IssuesNone found. Suggestions
Prompt for AI agents |
Summary
ghcr.io/conductorone/baton-jamf:latest; container images are now published topublic.ecr.aws/conductorone/baton-jamf:latestinstead.Test plan
public.ecr.aws/conductorone/baton-jamf:latestresolves (manifest exists) before opening this PR.🤖 Generated with Claude Code