payload: {"action":"created","issue":{"url":"https://api.github.com/repos/cloudposse/geodesic/issues/457","repository_url":"https://api.github.com/repos/cloudposse/geodesic","labels_url":"https://api.github.com/repos/cloudposse/geodesic/issues/457/labels{/name}","comments_url":"https://api.github.com/repos/cloudposse/geodesic/issues/457/comments","events_url":"https://api.github.com/repos/cloudposse/geodesic/issues/457/events","html_url":"https://github.com/cloudposse/geodesic/issues/457","id":437606638,"node_id":"MDU6SXNzdWU0Mzc2MDY2Mzg=","number":457,"title":"Geodesic shell wrongly treats $KUBECONFIG as a file","user":{"login":"raehik","id":3764592,"node_id":"MDQ6VXNlcjM3NjQ1OTI=","avatar_url":"https://avatars0.githubusercontent.com/u/3764592?v=4","gravatar_id":"","url":"https://api.github.com/users/raehik","html_url":"https://github.com/raehik","followers_url":"https://api.github.com/users/raehik/followers","following_url":"https://api.github.com/users/raehik/following{/other_user}","gists_url":"https://api.github.com/users/raehik/gists{/gist_id}","starred_url":"https://api.github.com/users/raehik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raehik/subscriptions","organizations_url":"https://api.github.com/users/raehik/orgs","repos_url":"https://api.github.com/users/raehik/repos","events_url":"https://api.github.com/users/raehik/events{/privacy}","received_events_url":"https://api.github.com/users/raehik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-04-26T10:25:24Z","updated_at":"2019-04-26T16:28:29Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"## what\r\n* [`geodesic.kube-ps1.sh`](https://github.com/cloudposse/geodesic/blob/master/rootfs/etc/profile.d/geodesic.kube-ps1.sh) turns kube-ps1 on and off automatically depending on kubecfg existence\r\n* but $KUBECONFIG isn't a file, it's a $PATH-like envvar (see [K8s docs](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable))\r\n\r\n## why\r\n* Geodesic shouldn't turn kube-ps1 off if $KUBECONFIG or the cached envvar isn't an existing file\r\n\r\n---\r\n\r\nNot sure exactly how to fix this - should probably use `kubectl config` instead though, that parses $KUBECONFIG and merges configs and such.\r\n\r\nThis came up because I was extending the $KUBECONFIG var to enable aws-iam-authenticator integration - writing to a file in `/dev` while building the container doesn't work because it's temporary."},"comment":{"url":"https://api.github.com/repos/cloudposse/geodesic/issues/comments/487118634","html_url":"https://github.com/cloudposse/geodesic/issues/457#issuecomment-487118634","issue_url":"https://api.github.com/repos/cloudposse/geodesic/issues/457","id":487118634,"node_id":"MDEyOklzc3VlQ29tbWVudDQ4NzExODYzNA==","user":{"login":"osterman","id":52489,"node_id":"MDQ6VXNlcjUyNDg5","avatar_url":"https://avatars3.githubusercontent.com/u/52489?v=4","gravatar_id":"","url":"https://api.github.com/users/osterman","html_url":"https://github.com/osterman","followers_url":"https://api.github.com/users/osterman/followers","following_url":"https://api.github.com/users/osterman/following{/other_user}","gists_url":"https://api.github.com/users/osterman/gists{/gist_id}","starred_url":"https://api.github.com/users/osterman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/osterman/subscriptions","organizations_url":"https://api.github.com/users/osterman/orgs","repos_url":"https://api.github.com/users/osterman/repos","events_url":"https://api.github.com/users/osterman/events{/privacy}","received_events_url":"https://api.github.com/users/osterman/received_events","type":"User","site_admin":false},"created_at":"2019-04-26T16:28:29Z","updated_at":"2019-04-26T16:28:29Z","author_association":"MEMBER","body":"@raehik looks like you're correct about `KUBECONFIG` being a path-like env var, which should get fixed. However, we do already support `aws-iam-authenticator` and do not have this problem, so I think you're taking an alternative approach. "}}
other: {"actor":{"display_login":"osterman"}}