Skip to content

chore: rename analyst1 app in registry mappings - #256

Merged
athreya-splunk merged 1 commit into
phantomcyber:mainfrom
mvforgione:rename-analyst1-app-name
Aug 11, 2026
Merged

athreya-splunk merged 1 commit into
phantomcyber:mainfrom
mvforgione:rename-analyst1-app-name

Conversation

@mvforgione

Copy link
Copy Markdown
Contributor

Renames the Analyst1 SOAR connector to "Analyst1 for Splunk SOAR" in local_hooks/data/appid_to_name.json. The app id 8ee822f1-a285-44f4-b8e7-303245811a32 is unchanged.

Splunkbase already lists an app named "Analyst1", which is the Analyst1 add-on for Splunk Enterprise and a separate product. The SOAR connector is being renamed to avoid the collision, following the convention other connectors use. Context is in splunk-soar-connectors/analyst1#3, where @athreya-splunk asked for this change.

appid_to_package_name.json needs no change. The package name is derived from the pyproject project name rather than the app display name, so it stays phantom_analyst1.

This should merge before the rename lands in the app repo, since check_valid_app_name_and_guid reads this file from main and would otherwise fail the app PR.

The Analyst1 SOAR connector is being renamed to "Analyst1 for Splunk SOAR" to distinguish it from the existing Analyst1 app for Splunk Enterprise on Splunkbase. The app id is unchanged.
@athreya-splunk
athreya-splunk merged commit 821df52 into phantomcyber:main Aug 11, 2026
4 checks passed
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