Skip to content
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
This repository was archived by the owner on Feb 6, 2026. It is now read-only.

Add ATLASSIAN_* env var fallbacks for shared credentials #99

@rianjs

Description

@rianjs

Problem

Users who use both cfl (Confluence) and jtk (Jira) CLIs need to set duplicate environment variables:

export CFL_URL=https://mycompany.atlassian.net
export CFL_EMAIL=user@example.com
export CFL_API_TOKEN=token123

export JIRA_URL=https://mycompany.atlassian.net
export JIRA_EMAIL=user@example.com
export JIRA_API_TOKEN=token123

Since both tools authenticate against the same Atlassian account with the same credentials, this duplication is unnecessary.

Proposed Solution

Add ATLASSIAN_* env vars as a fallback layer. Lookup order (most to least specific):

CFL_URL → ATLASSIAN_URL
CFL_EMAIL → ATLASSIAN_EMAIL
CFL_API_TOKEN → ATLASSIAN_API_TOKEN

This allows users to set shared credentials once:

export ATLASSIAN_URL=https://mycompany.atlassian.net
export ATLASSIAN_EMAIL=user@example.com
export ATLASSIAN_API_TOKEN=token123

And override per-tool when needed (e.g., self-hosted instances at different URLs):

export ATLASSIAN_EMAIL=user@example.com
export ATLASSIAN_API_TOKEN=token123
export JIRA_URL=https://jira.corp.com
export CFL_URL=https://confluence.corp.com

Changes Required

Update internal/config/config.go:

  • LoadFromEnv(): Check CFL_* first, then fall back to ATLASSIAN_*

Update documentation (README.md, CLAUDE.md) with new env vars.

Related

See corresponding issue in jira-ticket-cli for the JIRA_*ATLASSIAN_* fallback.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions