bearerToken vs. splunkToken
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with python/utils.py, where load() raises the shown NameError, then compare the documented option in python/README.md and python/.env with the accepted splunkToken spelling. Confirm whether bearerToken can be accepted as an alias without breaking splunkToken users; done means the documented configuration no longer raises this error.
Written by the indexing model from the issue text.
Description
The resolution of splunk/splunk-sdk-python#388 advises using the verb bearerToken to use the token-based authentication instead of the username/password credentials.
Both the python/README.md and the python/.env show the same verb -- although the line is commented-out in both examples. Unfortunately, trying to use it results in an error:
Traceback (most recent call last):
File "submit.py", line 82, in <module>
main(sys.argv[1:])
File "submit.py", line 43, in main
opts = parse(argv, RULES, ".env", usage=usage)
File "/home/xx/splunk-app-examples/python/utils.py", line 226, in parse
parser_.loadenv(config)
File "/home/xx/splunk-app-examples/python/utils.py", line 172, in loadenv
self.loadif(filepath)
File "/home/xx/splunk-app-examples/python/utils.py", line 166, in loadif
self.load(filepath)
File "/home/xx/splunk-app-examples/python/utils.py", line 159, in load
raise NameError("No such option --" + key)
NameError: No such option --bearerToken
Closer examination of the python/utils.py reveals, that the expected verb is splunkToken! At this time, the documented spelling should, probably, be added as an alias -- if possible -- to avoid breaking things for people already using the incorrect verb...
- Dominant language
- JavaScript
- Stars
- 155
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from splunk/splunk-app-examples
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
splunk/splunk-app-examples#67 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
splunk/splunk-app-examples#65 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
splunk/splunk-app-examples#48 · 2 comments ·
All issues in splunk/splunk-app-examples
Similar issues
-
area: bazaar bug complexity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
accensa/x402-facilitator-stellar#779 ·
Maintainers usually reply within 1 day
-
could-have reliability
Difficulty 1/5 Under an hour Newbie friendliness 88/100