Get an ArgoCD login for sbd

Open
#156 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
49/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift

Research direction

Read the deploy poller plan and the secrets CLI's PKCE login implementation, then trace how sbd handles callbacks at /callback. Implement the recommended sbd-owned login without requiring infrastructure changes or the argocd binary. Done when sbd can authenticate with the ArgoCD Cognito client and enable deploy tracking for charts PRs.

Written by the indexing model from the issue text.

Description

enhancement

The stock argocd login --sso fails against the argocd-cli Cognito client, so deploy tracking for charts PRs has no login. sbd can run its own PKCE login at /callback, as the secrets CLI does, or posthog-cloud-infra can add /auth/callback to that client.

The deploy poller plan recommends sbd's own PKCE login, which needs no infrastructure change and no argocd binary.

Dominant language
Swift
Stars
0
Forks
0
Avg merge
6h 15m
Merged PRs (30d)
308

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 haacked/switchboard

All issues in haacked/switchboard

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.