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

PATCH /v2/registrations/<registrationId> #3007

Open
jmcanterafonseca opened this Issue Oct 9, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@jmcanterafonseca
Copy link
Collaborator

jmcanterafonseca commented Oct 9, 2017

Allow to modify a context source registration

@fgalan fgalan changed the title PATH /v2/registrations/<registrationId> PATCH /v2/registrations/<registrationId> Oct 9, 2017

@fgalan

This comment has been minimized.

Copy link
Member

fgalan commented Nov 6, 2017

Let's ignore by the moment the triggering of context availability notifications (AKA "NGSI9 notifications") due to this operation. NGSI9 notifications could be deprectaed soon so it doesn't worth the time to keep them in NGSIv2.

@fgalan

This comment has been minimized.

Copy link
Member

fgalan commented Nov 10, 2017

Have a look to general comment on the registraitons functionality at #3008. Many of them could also apply to this issue.

@fgalan

This comment has been minimized.

Copy link
Member

fgalan commented Nov 10, 2017

All the registration features share the same common base branch: feature/ngsiv2_registrations.

Thus, this issue should be implemented in a branch splited from feature/ngsiv2_regsitrations (instead of master), using the task/ prefix in the new branch name, and the PR done using feature/ngsiv2_registrations as base branch (instead of master).

feature/ngsiv2_registrations will be update regularly with master, to keep it as synced as possible and ease the final feature/ngsiv2_registrations -> master merge once all the NGSIv2 registrations management functionality gets completed.

@fgalan

This comment has been minimized.

Copy link
Member

fgalan commented Feb 13, 2018

Documentation on updating_regs_and_subs.md should be updated accordingly once this issue gets implemented.

@fgalan

This comment has been minimized.

Copy link
Member

fgalan commented Mar 7, 2018

Check "MB-26: mongoRegistrationUpdate" in flowsIndex.md regarding the diagram (and associated documentation) regarding the operation implemented by this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment