added sensitive input options (#43)

* added sensitive input options

* release setup

* Update README.md

* Update step.yml

README.md

@@ -90,3 +90,8 @@ You can share your Step or step version with the [bitrise CLI](https://github.co
 1. Send the Pull Request, as described in the logs of `bitrise run share-this-step`
 
 That's all ;)
+
+## Trigger a new release
+
+- __merge every code changes__ to the `master` branch
+- __push the new version tag__ to the `master` branch

bitrise.yml

@@ -3,8 +3,6 @@ default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
 
 app:
   envs:
-  - RELEASE_VERSION: 1.4.3
-
   - SAMPLE_APP_URL: https://github.com/bitrise-samples/sample-apps-android-realmtasks.git
   - BRANCH: master
 
@@ -165,20 +163,6 @@ workflows:
             go get -u -v github.com/golang/dep/cmd/dep
             dep ensure -update -v
 
-  # ----------------------------------------------------------------
-  # --- workflow to create Release version
-  create-release:
-    steps:
-    - script:
-        title:
-        inputs:
-        - content: |
-            #!/bin/bash
-            set -ex
-            go get -u github.com/bitrise-tools/releaseman
-            export CI=true
-            releaseman create --version "$RELEASE_VERSION"
-
   # ----------------------------------------------------------------
   # --- workflow to Share this step into a Step Library
   audit-this-step:
@@ -189,38 +173,3 @@ workflows:
             #!/bin/bash
             set -ex
             stepman audit --step-yml ./step.yml
-
-  share-this-step:
-    envs:
-      # if you want to share this step into a StepLib
-      - MY_STEPLIB_REPO_FORK_GIT_URL: $MY_STEPLIB_REPO_FORK_GIT_URL
-      - STEP_ID_IN_STEPLIB: google-play-deploy
-      - STEP_GIT_VERION_TAG_TO_SHARE: $RELEASE_VERSION
-      - STEP_GIT_CLONE_URL: https://github.com/bitrise-steplib/steps-google-play-deploy.git
-    description: |-
-      If this is the first time you try to share a Step you should
-      first call: $ bitrise share
-      This will print you a guide, and information about how Step sharing
-      works. Please read it at least once!
-      As noted in the Step sharing guide you'll have to fork the
-      StepLib you want to share this step into. Once you're done with forking
-      the repository you should set your own fork's git clone URL
-      in the `.bitrise.secrets.yml` file, or here in the `envs` section,
-      as the value of the `MY_STEPLIB_REPO_FORK_GIT_URL` environment.
-      You're now ready to share this Step, just make sure that
-      the `STEP_ID_IN_STEPLIB` and `STEP_GIT_VERION_TAG_TO_SHARE`
-      environments are set to the desired values!
-      To share this Step into a StepLib you can just run: $ bitrise run share-this-step
-      Once it finishes the only thing left is to actually create a Pull Request,
-      the way described in the guide printed at the end of the process.
-    before_run:
-    - audit-this-step
-    steps:
-    - script:
-        inputs:
-        - content: |-
-            #!/bin/bash
-            set -ex
-            bitrise share start -c ${MY_STEPLIB_REPO_FORK_GIT_URL}
-            bitrise share create --stepid ${STEP_ID_IN_STEPLIB} --tag ${STEP_GIT_VERION_TAG_TO_SHARE} --git ${STEP_GIT_CLONE_URL}
-            bitrise share finish

step.yml

@@ -60,6 +60,7 @@ inputs:
         For remote JSON key file you can provide any download location (ex: `https://URL/TO/key.json`).
         For local JSON key file provide file path url. (ex: `file://PATH/TO/key.json`).
       is_required: true
+      is_sensitive: true
   - package_name:
     opts:
       title: Package name