StackStorm / StackStorm/st2

two equals == is being interpreted as a key/value pair by the StackStorm API.

Open
#5,274 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API bug
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

SUMMARY

Provide a quick summary of your bug report.

Reference: https://github.com/nzlosh/err-stackstorm/issues/37

STACKSTORM VERSION

latest using docker tag

OS, environment, install method

docker

Steps to reproduce the problem

Show how to reproduce the problem, using a minimal test-case. Make sure to include any content
(pack content - workflows, actions, etc.) which are needed to reproduce the problem.

Expected Results

input string two or more equals not to be parsed as key/value, just string

Actual Results

It seems the == is being interpreted as a key/value pair by the StackStorm API.

12:38 PM
!st2 licensing request json data 111==

12:38 PM
storm-trooper-bot-devAPP Additional properties are not allowed ('111' was unexpected)
Failed validating 'additionalProperties' in schema:
{'additionalProperties': False,
'description': 'Execute Composer Licensing actions chained flow',
'properties': {'display_published': {'default': True,
'description': 'Intermediate '
'published '
'variables will '
'be stored and '
'displayed.',
'type': 'boolean'},
'request': {'description': 'Composer Licensing request',
'required': True,
'type': 'string'},
'skip_notify': {'default': ['get_user',
'failure_get_user_msg',
'composer_licensing_failure_msg',
'composer_licensing_action_process'],
'description': 'List of tasks to skip '
'notifications for.',
'type': 'array'}},
'title': 'composer_licensing',
'type': 'object'}
On instance:
{'111': '=',
'display_published': True,
'request': 'request json data',
'skip_notify': ['get_user',
'failure_get_user_msg',
'composer_licensing_failure_msg',
'composer_licensing_action_process']}

Making sure to follow these steps will guarantee the quickest resolution possible.

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Docker-based StackStorm request shown in the report: !st2 licensing request json data 111==. Trace how that input reaches the API and schema validation; done means 111== remains part of the request string rather than becoming a {'111': '='} key/value pair.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.