-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
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
Question: How/when to remove NGSI-v1 from the library? #966
Comments
Following on from: telefonicaid/iotagent-ul#460 (comment) and Removing stuff from the Lib will be easy, but there will need to be testing on the various downstream projects. Should there be a release of the IoT Agents before attempting the removal? |
We think removing deprecated NGSI-v1 from IOTAs would be a good idea. Please find feedback below.
We would suggest to add two extra items to the list of checkboxes:
Makes sense. In IOTAs probably we should to the same and move to 2.0.0.
We think they are independent things. I mean, NGSI-v1 removal can be started without waiting for NGSI-LD support being completed.
We think it would be a good idea. Although the PRs can be started now, they will be merged after a new release had been done. However, I think that new release will be done soon. |
Related to #970 - a potential timetable for this is as follows:
|
I'd say that after merging PR #995 and all the related others in IOTAs repos this issue is complete. There are some checkboxes above not marked, but probably they are completed tasks. @jason-fox could you have a look and close this issue if you think everything is completed, please? |
This task is completed. |
I know NGSI-v1 is deprecated, but at some point I assume NGSI-v1 support is to be dropped. Just to ensure things don't get lost here is a reminder for future development:
isCurrentNgsi()
across current IoT Agent codebases - see Mixed mode implementation breaks the code of the IOTAs using iotagent-node-lib #963 - remove NGSI-v1 path of executionQuestions
3.0.0
?The text was updated successfully, but these errors were encountered: