Releases: VatsalJagani/splunk-app-action
v4
v4
-
Run the user-defined commands in the context of your App's root directory instead of Repo's root directory. Refer to
Running User Defined Commands Before Generating the final App Build
for more details. -
to_make_permission_changes
parameter's default value has been changed tofalse
. Refer toAvoid File and Folder Permission Issue on Your App Build
for more details.- Automatic file permission changes now also add executable permissions to the following file extensions,
.msi
,.exe
,.cmd
,.bat
, along with.sh
.
- Automatic file permission changes now also add executable permissions to the following file extensions,
-
The input parameters
is_generate_build
andapp_build_path
has been removed.
Upgrade Guide from v3 to v4
-
From
v4
of thesplunk-app-action
, your user-defined custom command (Refer toRunning User Defined Commands Before Generating the final App Build
section) would run in the context of your App's folder instead of the root folder.- So you need to change the code from this:
- uses: VatsalJagani/splunk-app-action@v3 env: SPLUNK_APP_ACTION_1: "rm -rf my_app/extra_test_folder" SPLUNK_APP_ACTION_2: "cat 'abc,123' >> my_app/lookups/my_custom_lookup.csv" with: app_dir: "my_app"
- to
- uses: VatsalJagani/splunk-app-action@v3 env: SPLUNK_APP_ACTION_1: "rm -rf extra_test_folder" SPLUNK_APP_ACTION_2: "cat 'abc,123' >> lookups/my_custom_lookup.csv" with: app_dir: "my_app"
- Because this command would now run in context of your App's directory.
- So you need to change the code from this:
-
to_make_permission_changes
- default value has been changed tofalse
fromtrue
. This means if you were to apply file and folder permission changes automatically, you have to explicitly add this parameter to your workflow. Refer toAvoid File and Folder Permission Issue on Your App Build
for more details. -
The input parameters
is_generate_build
andapp_build_path
have been removed from GitHub action fromv4
onwards, hence if you are using them then migrate the action config properly before the version update.
v3
What's Changed
- use_ucc_gen parameter added to support UCC build Add-on support. (It uses
ucc-gen build
command to generate the build dynamically on the GitHub action directly.) - Added new utility
ucc_additional_packaging
for better way to generate proper Python Input handler file structure. - Better way to Auto detect App package id, App version number and App build number.
- Better naming convention for App and Add-on build names.
- Run App utilities on current branch instead of on default branch for better support and easier to deal with in codebase.
- Automatically delete unwanted files from the build to avoid App inspect check issues.
Version 2
Version 2 of splunk-app-action
It now includes the capability to add many common Splunk utilities.
Fixed multiple issues including running custom user-defined commands and others.
Version 1
Version 1 of splunk-app-action