We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.0
Other
NGSIv2
None
In the README.md file, there is a section that says there is a file to help with testing the IoT agent in bin/iotaJsonTester.js.
no such a file exists in the repository. I cant find it anywhere.
No response
environment: - "IOTA_CB_HOST=orion" - "IOTA_CB_PORT=1026" - "IOTA_NORTH_PORT=4041" - "IOTA_REGISTRY_TYPE=mongodb" - "IOTA_MONGO_HOST=mongodb" - "IOTA_MONGO_PORT=27017" - "IOTA_MONGO_DB=iotagent-json" - "IOTA_HTTP_PORT=7896" - "IOTA_PROVIDER_URL=http://iot-agent:4041"
The text was updated successfully, but these errors were encountered:
bin/iotaJsonTester.js
Thank for your feedback!
PR #775 removes that reference.
Please close issue if you find this is ok.
Sorry, something went wrong.
The actual file would be verry usefull to me. has it been depreciated? can I find it anywhere
edit: also it is still listed in the readme's contents links at the top of the page, "command line client" now links to nohwere
You can find the script in previous commits/versions. I.E: https://github.com/telefonicaid/iotagent-json/blob/aef8f204e97e7052afbb1c4bc2eb08adada7fc7a/bin/iotaJsonTester.js
Successfully merging a pull request may close this issue.
IoT Agent JSON version the issue has been seen with
2.2.0
Bound or port used (API interaction)
Other
NGSI version
NGSIv2
Are you running a container?
None
Image type
None
Expected behaviour you didn't see
In the README.md file, there is a section that says there is a file to help with testing the IoT agent in bin/iotaJsonTester.js.
no such a file exists in the repository. I cant find it anywhere.
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Configs
Log output
No response
The text was updated successfully, but these errors were encountered: