step.yml

#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/

title: |-
  Q Prepare build filename
summary: |
  Change file names to include version and build numbers. Example: AppNameStaging-v1.1.0-b53
description: |
  This step will change build filename name to x_vx.x.x_bxbXX
website: https://github.com/Q-Agency/bitrise-step-change--aab-name
source_code_url: https://github.com/Q-Agency/bitrise-step-change--aab-name
support_url: https://github.com/Q-Agency/bitrise-step-change--aab-name/issues
host_os_tags:
  - osx-10.10
  - ubuntu-16.04

# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
# project_type_tags:
#   - ios
#   - macos
#   - android
#   - xamarin
#   - react-native
#   - cordova
#   - ionic

# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
  - deploy

is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ""

deps:
  brew:
  - name: git
  - name: wget
  apt_get:
  - name: git
  - name: wget


toolkit:
  bash:
    entry_file: step.sh

inputs:
  - change_filename_build_name: $BUILD_NAME
    opts:
      title: "Build name"
      summary: "Name should contain environment. Example: AppNameStaging"
      description: |
        Name of the build. This value should be set inside Env Vars section.
      is_required: true
  - change_filename_version_number: $ANDROID_VERSION_NAME
    opts:
      title: "Version"
      summary: "Build version"
      description: |
      is_required: true
  - change_filename_build_number: $ANDROID_VERSION_CODE
    opts:
      title: "Build number"
      summary: "Build number"
      description: |
      is_required: true
  - change_filename_aab_path: $BITRISE_AAB_PATH
    opts:
      title: "Android App Bundle path"
      summary: "Android App Bundle file (`.aab`) path"
      description: |
        The **Android App Bundle path** input field is automatically filled out by the output of the previous build Step
      is_expand: true
      is_required: true
  - change_filename_apk_path: $BITRISE_APK_PATH
    opts:
      title: "Android APK path"
      summary: "Android APK file (`.apk`) path"
      description: |
        The **Android APK path** input field is automatically filled out by the output of the previous build Step
      is_expand: true
      is_required: true

outputs:
  - BITRISE_SIGNED_AAB_PATH:
    opts:
      title: "Path to .AAB file"
      summary: Path to .AAB file
      description: |
        Path to .AAB file
  - BITRISE_APK_PATH:
    opts:
      title: "Path to .APK file"
      summary: Path to .APK file
      description: |
        Path to .APK file
  - BITRISE_APP_FINAL_NAME_AAB:
    opts:
      title: "AAB filename"
      summary: AAB filename
      description: |
        AAB filename
  - BITRISE_APP_FINAL_NAME_APK:
    opts:
      title: "APK filename"
      summary: APK filename
      description: |
        APK filename
  - BITRISE_APP_FINAL_NAME:
    opts:
      title: "Build name."
      summary: Build name.
      description: |
        Build name.