Skip to content

feat: add auth:tokens namespace help and auth:tokens:list command#2615

Open
harshitha-cstk wants to merge 1 commit into
v2-devfrom
enh/dx-3812-tokens-enh
Open

feat: add auth:tokens namespace help and auth:tokens:list command#2615
harshitha-cstk wants to merge 1 commit into
v2-devfrom
enh/dx-3812-tokens-enh

Conversation

@harshitha-cstk

@harshitha-cstk harshitha-cstk commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Add auth:tokens:list Command and update auth:tokens

Summary

Introduces auth:tokens as a help command and adds auth:tokens:list as an explicit subcommand for listing saved tokens.

Previously, auth:tokens directly listed tokens, which mixed namespace behavior with token listing functionality. This update separates responsibilities by making auth:tokens a namespace entry point that displays contextual help and guiding users to the appropriate token management subcommands.

Changes

Updated Commands

Command Description
csdx auth:tokens Displays namespace help with available token commands
csdx auth:tokens:list Lists all saved tokens in table format
csdx auth:tokens:add Adds a token (unchanged behavior)
csdx auth:tokens:remove Removes a token (unchanged behavior)

Namespace Help

csdx auth:tokens now displays:

  • Description
  • Usage
  • Available flags
  • Examples
  • Token management subcommands:
    • auth:tokens:list
    • auth:tokens:add
    • auth:tokens:remove

Help Flag Handling

The following commands now show the same namespace help output without errors:

csdx auth:tokens

csdx auth:tokens --help

@harshitha-cstk harshitha-cstk requested a review from a team as a code owner June 25, 2026 09:32
@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 0
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant