You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation and action.yaml describe the output value kubeconfig_path that is supposed to point to the generated kubeconfig file, but it is empty after authenticating to a cluster.
This feature is helpful in my case since I am coordinating actions across multiple GKE clusters. Being able to auth to each cluster once and then act on all of them based on kubeconfig as needed is useful; Relying on solely the env vars output by the action makes this difficult, or multiple auths necessary.
You can of course work around this issue by capturing the KUBE_CONFIG_PATH env var to a GitHub output:
TL;DR
The documentation and
action.yaml
describe the output valuekubeconfig_path
that is supposed to point to the generated kubeconfig file, but it is empty after authenticating to a cluster.Expected behavior
The output should be set.
Observed behavior
The output is not set.
Action YAML
Log output
No response
Additional information
This feature is helpful in my case since I am coordinating actions across multiple GKE clusters. Being able to auth to each cluster once and then act on all of them based on kubeconfig as needed is useful; Relying on solely the env vars output by the action makes this difficult, or multiple auths necessary.
You can of course work around this issue by capturing the
KUBE_CONFIG_PATH
env var to a GitHub output:You can refer to this in later steps as
steps.capture-config.outputs.kubeconfig_path
.PR incoming with the fix...
The text was updated successfully, but these errors were encountered: