Skip to content

Conversation

kingphil
Copy link

@kingphil kingphil commented Nov 30, 2022

More explanation here. #15

This is a suggested fix with a hard-coded filename. If a dynamic filename is needed, other info could be added (e.g. repo namespace and repo name, build number, or maybe just DRONE_COMMIT_SHA).

Copy link

@Neferpitooou Neferpitooou left a comment

Choose a reason for hiding this comment

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

but I guess, this variable helps to create a unique value filename on the target directory. for example, if this will create something like artifacts... It is very relevant to have. But if these configurations create such loops in exporting this file, then yet yes, it is worth re-configuring but not REMOVING.

@@ -14,7 +14,7 @@ steps:
image: bitnami/kubectl:1.22.2
user: root # the bitnami/kubectl image has a non-root user set by default, which does not work with the shared docker volume which is owned by root
commands:
- export KUBECONFIG=kubeconfig-$${DRONE_BUILD_STARTED}.yaml

Choose a reason for hiding this comment

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

but I guess, this variable helps to create a unique value filename on the target directory. for example, if this will create something like artifacts... It is very relevant to have. But if these configurations create such loops in exporting this file, then yet yes, it is worth re-configuring but not REMOVING.

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