aws-connected-device-framework
aws-connected-device-framework copied to clipboard
aws
Asset Library Remove Device to Device Association
Aws Connected Device Framework Affected Module(s):
I'm submitting a ...
- [x] bug report
- [ ] feature request
Description:
Current behavior:
API for deleting association from Device to Device is not working: DELETE /devices/{deviceId}/{relationship}/devices/{otherDeviceId} Expected behavior:
This API should delete existing association between two devices Steps to reproduce:
Create relationship: PUT /devices/{deviceId}/{relationship}/devices/{otherDeviceId} then delete using: DELETE /devices/{deviceId}/{relationship}/devices/{otherDeviceId}Additional Information:
Thanks for the feedback. Supporting the AWS SDK for Go v2 is definitely on our radar, but we do not have a timeline to share at this time.
Unfortunately, AWS Go SDK v2 is currently not on our roadmap since it's still in developer preview stage. Once it's generally available, we will start our plan to support v2.
Sounds like this is getting pretty close: https://aws.amazon.com/blogs/developer/aws-sdk-for-go-version-2-v2-release-candidate/
AWS SDK v2 for Go was GA'd on 2021-01-19 per https://aws.amazon.com/blogs/developer/aws-sdk-for-go-version-2-general-availability
Can we get an update on this?
Hi all,
I've forked the project and created a compatibility layer for go sdk v2. You can check it out here. I've currently only written support for query and putItem. Guaranteed to have some bugs, mainly because I haven't done much testing.
If you want to try it out all you need to do is add a replace line in your go.mod
replace (
github.com/aws/aws-dax-go => github.com/kochie/aws-dax-go master
)
If there's interest in supporting the other API calls let me know. I'm pretty sure that updating the project to support aws-go-sdk-v2 will require a major rewrite. All I've really done so far is map the v2 input/output structs to v1. (Also I haven't added support for optFns to run correctly at the time of writing.)
Enjoy!
Any update on support for AWS Go SDK v2 ?
We have been using the new version of SDK for a while & we wanted to move to DAX in order to improve the overall response times but it requires us to downgrade back to SDK v1 thereby loosing all benefits of SDK v2 & requiring additional effort of migration.
A friendly follow-up to the question and request above. It is quite cumbersome to be maintaining sets of two different libraries depending on whether we are accessing DynamoDB directly (using SDK v2) or via DAX cache (using SDK v1) - it would help us a lot if DAX client was updated to fully support AWS SDK v2 which has been released almost a year ago.
Thank you in advance for your help or at least an indication of when (if ever) we might expect this library to support SDK v2.
Same question here about support. Now that the aws go sdk has an official release, when can we expect to get support in this library?
I have the same question as we developed everything using the V2 SDK and we wouldn't want to go back to V1 just for DAX 👍
same here. Everything is on V2 and we need to use V1 just for DAX. Please plan for it!
@sumitsa-amazon is there any plans to support this? I'd love to use DAX, but going back to v1 for it is not in the cards.
Still no updates on supporting this? Its been open for more than five years.
We've already gone through the painful process of migrating to the v2 SDK and are not keen at all to migrate back to v1 just to use DAX.
https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/
AWS SDK for Go (v1) will enter maintenance mode on July 31, 2024 and reach end-of-support on July 31, 2025.
💀
