adding support to pass git token directly to github-release step' (#560)

* adding support to pass git token directly to `github-release` step'

Author: roi-codefresh

incubating/github-release/run.sh

@@ -2,6 +2,8 @@
 
 set -o pipefail
 
+FORBID_DECRYPT_MSG="Decrypting contexts is not allowed because 'forbidDecrypt' feature is enabled"
+
 bold() { echo -e "\e[1m$@\e[0m" ; }
 red() { echo -e "\e[31m$@\e[0m" ; }
 green() { echo -e "\e[32m$@\e[0m" ; }
@@ -29,7 +31,15 @@ ALL_VARS=(`echo "${REQUIRED_VARS[@]}"` `echo "${OPTIONAL_VARS[@]}"`)
 
 function getTokenFromContext() {
     bold "Getting a git token from the context \"${GIT_CONTEXT}\"..."
-    GITHUB_TOKEN=$(codefresh get contexts --type git.github $1 --decrypt -o json | jq -r '.spec.data.auth.password') || return 1
+    GITHUB_TOKEN_RESPONSE=$(codefresh get contexts --type git.github $1 --decrypt -o json 2>&1)
+    if [ $? != 0 ]; then
+        red "Failed to get the git token from context \"${GIT_CONTEXT}\" with error: ${GITHUB_TOKEN_RESPONSE}"
+        if [ -z "${GITHUB_TOKEN_RESPONSE##*$FORBID_DECRYPT_MSG*}" ]; then
+            yellow "You should use the 'git_token' argument to pass a github token"
+        fi
+        return 1
+    fi
+    GITHUB_TOKEN=$(echo ${GITHUB_TOKEN_RESPONSE} | jq -r '.spec.data.auth.password')
     export GITHUB_TOKEN
     ok
 }
@@ -49,6 +59,9 @@ function checkTrigger() {
 }
 
 function setDefaultVarValues() {
+    if [ ! -z "$GITHUB_TOKEN" ]; then
+        GIT_CONTEXT="_" # This is irrelevant, we are using GITHUB_TOKEN
+    fi
 
     if [ -z "$GIT_CONTEXT" ]; then
         yellow "GIT_CONTEXT var is not set explicitly. Trying to get it from the trigger by default..."
@@ -117,7 +130,10 @@ function main() {
     setDefaultVarValues
     [ $? != 0 ] && red "Failed to set default value for one of the required variables, exiting..." && return 1
 
-    getTokenFromContext $GIT_CONTEXT
+    if [ -z "$GITHUB_TOKEN" ]; then
+        getTokenFromContext $GIT_CONTEXT
+        [ $? != 0 ] && return 1
+    fi
 
     validateReqVars
 

incubating/github-release/step.yaml

@@ -3,7 +3,7 @@ version: '1.0'
 metadata:
   name: github-release
   title: Create a GitHub release
-  version: 1.1.5
+  version: 1.1.6
   isPublic: true
   description: Create a GitHub release.
   sources:
@@ -38,6 +38,19 @@ metadata:
             files:
             - ${{CF_VOLUME_PATH}}/${{CF_REPO_NAME}}/my-file1
             - ${{CF_VOLUME_PATH}}/${{CF_REPO_NAME}}/my-file2
+    - description: git-token
+      workflow:
+        github_release:
+          type: github-release
+          title: Using git token example
+          description: |-
+            You can also pass a git token explicitly using the git_token
+            argument. This is useful when you don't want to use a git-context
+            or when the 'forbidDecrypt' feature turned on.
+          arguments:
+            git_token: ${{GITHUB_TOKEN}}
+            release_name: my-release
+            release_tag: my-tag-0.1.0
     - description: full
       workflow:
         github_release:
@@ -95,6 +108,11 @@ spec:
                 "type": "string",
                 "description": "Codefresh Git Context to be used by the plugin. Must be a github git context. If empty, it will try to get the context from the pipeline trigger"
             },
+            "git_token": {
+                "name": "git token",
+                "type": "string",
+                "description": "Git token to use for authentication to github. If empty, we will try to get the token from your Codefresh Git Context specified in `git_context_name`"
+            },
             "release_tag": {
                 "type": "string",
                 "description": "Git tag to create a release"
@@ -142,6 +160,7 @@ spec:
       image: codefresh/github-release
       environment:
         - 'GIT_CONTEXT=${{git_context_name}}'
+        - 'GITHUB_TOKEN=${{git_token}}'
         - 'CF_BRANCH_TAG_NORMALIZED=${{CF_BRANCH_TAG_NORMALIZED}}'
         - 'CF_REPO_OWNER=${{CF_REPO_OWNER}}'
         - 'CF_REPO_NAME=${{CF_REPO_NAME}}'