cloudfoundry / cloudfoundry/cli

cf login ran through CliCommand() doesn't update LogCacheEndPoint

Open
#3,632 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.9k
Forks
990
Avg merge
1d 7h
Merged PRs (30d)
8

Description

Please fill out the issue checklist below and provide ALL the requested information.

  • I reviewed open and closed github issues that may be related to my problem.
  • I tried updating to the latest version of the CF CLI to see if it fixed my problem.
  • I attempted to run the command with CF_TRACE=1 to help debug the issue.
  • I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
When calling the cf login command through the plugin.CliConnection.CliCommand() the LogCacheEndPoint in the ~/.cf/config.json file is never updated.
https://github.com/the8tre/cf-cli-login-issue/blob/4d086d0c6fa0ab8f1b439824ab6633700b7ba730/cf_cli_login_issue.go#L28-L31

What happened
As the LogCacheEndPoint is not properly updated, calls to cf logs my-app fail with a Failed to retrieve logs from Log Cache: unexpected status code 404 error.

Expected behavior
The LogCacheEndPoint field of ~/.cf/config.json should be properly updated with the right url using the right CF API domain.

Exact Steps To Reproduce
Here is a GitHub repository with a sample cf cli plugin that reproduces the issue:
https://github.com/the8tre/cf-cli-login-issue#

  • Run cf login your-own-parameters
  • Check that LogCacheEndPoint in ~/.cf/config.json is properly updated
  • Install the sample plugin linked above
  • Run cf loginissue some-other-parameters on another CF API endpoint
  • Check that LogCacheEndPoint in ~/.cf/config.json is not updated

Provide more context

  • platform and shell details:
    • MacOS Tahoe 26.1, any terminal (MacOS Terminal, iTerm, Ghostty)
    • Windows 11 Enterprise - 24H2 - 26100.7092
  • version of the CLI you are running:
    • MacOS: cf version 8.16.0+4b92b73.2025-09-18
    • Windows: cf version 8.16.0+4b92b73e4.2025-09-18
  • version of the CC API Release you are on

Notes regarding V6 and V7 CLI support:

  • V6:
    • Minimum supported version of CF Deployment: v7.0.0 (CAPI Release: 1.74.0 (APIs 2.128.0 and 3.63.0))
    • Maximum supported version of CF Deployment: v13.4.0 (CAPI Release: 1.94.0 (APIs 2.149.0 and 3.84.0))
  • V7:
    • Minimum supported version of CF Deployment: v13.5.0 (CAPI Release: 1.95.0 (APIs 2.150.0 and 3.85.0))

Contributor guide

Open the contributing guide

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.

Research direction

Start with the reproduction entry point in cf_cli_login_issue.go, lines 28-31, and trace plugin.CliConnection.CliCommand() while switching between the two CF API endpoints. Compare ~/.cf/config.json after each login, then verify that cf logs my-app uses the updated LogCacheEndPoint and no longer returns the 404 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.