Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / kurago-dev/node-red-contrib-azure issues and pull requests
#30 - Bumped version to 1.0.7
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#29 - Bump version to 1.0.7
Issue -
State: closed - Opened by unaipme over 1 year ago
#28 - Already existing proxy agent functions now in common module
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#27 - Proxy settings are being ignored in reconnect function
Issue -
State: closed - Opened by unaipme over 1 year ago
#26 - Version bump
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#25 - Deleted nodes are correctly stopped now
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#24 - DP IoTHub Node weird reconnect behaviour
Issue -
State: closed - Opened by unaipme over 1 year ago
#23 - Fixed status mismatch
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#22 - DP BlobStorage node wrong status report
Issue -
State: closed - Opened by unaipme over 1 year ago
#21 - Implemented sensitive data as credentials
Pull Request -
State: closed - Opened by unaipme over 1 year ago
- 3 comments
#20 - Encrypt credentials in our Azure nodes
Issue -
State: closed - Opened by unaipme over 1 year ago
#19 - Bump version
Pull Request -
State: closed - Opened by aitor-gamarra over 1 year ago
#18 - log->trace for msg payloads
Pull Request -
State: closed - Opened by aitor-gamarra over 1 year ago
#17 - Fixed issue with noproxy checking
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#16 - Fixed packing issue, new version added
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#15 - readme.md > README.md
Pull Request -
State: closed - Opened by aitor-gamarra over 1 year ago
#14 - Revert "Added readme"
Pull Request -
State: closed - Opened by aitor-gamarra over 1 year ago
#13 - Added readme
Pull Request -
State: closed - Opened by unaipme over 1 year ago
#12 - Implemented lifecycle status in the nodes
Pull Request -
State: closed - Opened by unaipme over 1 year ago
- 3 comments
#11 - Fixed issue with empty proxy URL
Pull Request -
State: closed - Opened by unaipme almost 2 years ago
- 2 comments
#10 - Add support for empty proxy configuration
Issue -
State: closed - Opened by kurago-dev almost 2 years ago
#9 - Implement lifecycle status in the nodes
Issue -
State: closed - Opened by unaipme almost 2 years ago
- 3 comments
#8 - 6 modifiy the azure blob nodes implementation to forward messages upon sending failure
Pull Request -
State: closed - Opened by unaipme almost 2 years ago
#7 - 5 modifiy the azure iot nodes implementation to forward messages upon sending failure
Pull Request -
State: closed - Opened by unaipme almost 2 years ago
#6 - Modifiy the azure-blob node's implementation to forward messages upon sending failure
Issue -
State: closed - Opened by unaipme almost 2 years ago
#5 - Modifiy the azure-iot node's implementation to forward messages upon sending failure
Issue -
State: closed - Opened by unaipme almost 2 years ago
#4 - 2 implement blob storage node
Pull Request -
State: closed - Opened by aitor-gamarra almost 2 years ago
- 1 comment
#3 - 1 add support for proxy configurations when using websockets in both amqp and mqtt
Pull Request -
State: closed - Opened by unaipme almost 2 years ago
#2 - Implement blob storage node
Issue -
State: closed - Opened by unaipme almost 2 years ago
#1 - Add support for Proxy configurations when using Websockets in both AMQP and MQTT.
Issue -
State: closed - Opened by unaipme almost 2 years ago