Skip to content

Conversation

@ikogan
Copy link
Contributor

@ikogan ikogan commented Nov 4, 2025

No description provided.

Copilot AI review requested due to automatic review settings November 4, 2025 18:36
@ikogan ikogan merged commit 7744639 into main Nov 4, 2025
7 of 8 checks passed
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a debug log message to provide better visibility when fetching kubeconfig files for Rancher clusters.

  • Adds a debug message before the gum spin command to log cluster and server information during kubeconfig fetching

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

for CLUSTER in $(rancher cluster list | grep -v CURRENT | sed 's/^*//g' | awk '{ print $1 }'); do
if [[ -z "${SKIP_KUBECONFIG}" ]]; then
TEMP_KUBE_CONFIG=$(echo "${SERVER}-${CLUSTER}" | base64)
debug "Fetching kubeconfig for cluster ${CLUSTER} on server ${SERVER}..."
Copy link

Copilot AI Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The debug message on line 807 duplicates information already shown by the gum spin title on line 808. When HAVE_GUM is true and ENABLE_DEBUG is set, users will see both messages simultaneously, which is redundant. The debug message should either provide additional context (like the full file path where the config will be saved) or be removed to avoid duplication.

Suggested change
debug "Fetching kubeconfig for cluster ${CLUSTER} on server ${SERVER}..."
debug "Fetching kubeconfig for cluster ${CLUSTER} on server ${SERVER} (saving to ${TEMP_DIR}/${TEMP_KUBE_CONFIG}.yaml)..."

Copilot uses AI. Check for mistakes.
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.

2 participants