[CFX-4964] Create/Edit drconfig.yaml only after valid API key received

[taras-pokornyy]

RATIONALE

Don't touch ~/.config/datarobot/drconfig.yaml until both valid endpoint AND token are ready when running dr auth login. So unfinished auth flow won't break anything.

Actual:

When running dr auth login, the CLI will write to ~/.config/datarobot/drconfig.yaml a set of credentials before the auth flow is complete.

Expected:

When running dr auth login, the CLI will write to ~/.config/datarobot/drconfig.yaml the set of credentials ONLY once auth flow is complete and successful.

CHANGES

• Created SetURLToConfig function in internal/config/api.go
• Updated following files to use new SetURLToConfig function instead of SaveURLToConfig:
  -- cmd/auth/login/cmd.go
  -- cmd/auth/seturl/cmd.go
  -- internal/auth/auth.go

IMPORTANT

SaveURLToConfig function still exists as it is used in cmd/templates/setup/model.go

PR Automation

Comment-Commands: Trigger CI by commenting on the PR:

• /trigger-smoke-test or /trigger-test-smoke - Run smoke tests
• /trigger-install-test or /trigger-test-install - Run installation tests

Labels: Apply labels to trigger workflows:

• run-smoke-tests or go - Run smoke tests on demand (only works for non-forked PRs)

Important

For Forked PRs: If you're an external contributor, the run-smoke-tests label won't work. A maintainer must manually trigger the "Fork PR Smoke Tests" workflow from the Actions tab, providing your PR number. Please comment requesting a maintainer review if you need smoke tests to run.

---

Note

Medium Risk
Changes when the CLI mutates and writes drconfig.yaml during authentication, which can affect users’ ability to log in and persist credentials if there are edge-case failures. The scope is contained to URL-setting and config-write helpers, with added tests to reduce regression risk.

Overview
Defers config-file writes during auth URL setup. dr auth login and dr auth set-url now call the new config.SetURLToConfig helper, which updates the in-memory Viper config with a normalized endpoint (/api/v2) without writing drconfig.yaml until the auth flow completes successfully.

auth.WriteConfigFileSilent now ensures the config directory/file exists before writing, and the interactive URL prompt messaging is updated to reflect that validation/API-key retrieval happens next. Adds a new internal/config/api_test.go suite covering URL normalization (including shortcuts) and asserting SetURLToConfig does not write to disk.

^{Reviewed by Cursor Bugbot for commit 6903596. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[ajalon1]

Requesting changes to make sure that we handle all scenarios where we write to config. Good first pass.

I'd also suggest writing unit tests for SetUrlToConfig(), and ensure that the config file is NOT written to.

[ajalon1]

🚢