Skip to content
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

DEV: TRAJ: Determine Code Impact to client PUT API Change #680

Open
niaalex opened this issue Aug 20, 2019 · 1 comment
Open

DEV: TRAJ: Determine Code Impact to client PUT API Change #680

niaalex opened this issue Aug 20, 2019 · 1 comment
Assignees

Comments

@niaalex
Copy link
Contributor

niaalex commented Aug 20, 2019

#619 - DEV: Determine Code Impact to client PUT API Change

DEV: Analysis: small (search codebase for usage & determine code change)
DEV: Code & Test: TBD

Per client, the current PUT API of some DoT services provides partial update behavior, which is wrong (The correct PUT behavior is to create a new resource or replace whole existing resource). This is DoT technical debt and we’re going to correct them. Below PUT APIs behavior needs correction:

PUT /witsml/wells/{uid}
PUT /witsml/wellbores/{uid}
PUT /witsml/trajectories/{uid}

Before any code change on DoT side, could you please confirm whether Drillflow relies on above APIs partial update? If yes, please adjust code accordingly. After that, we will update DoT code.

Thanks,
Xiaobin

@Mike-d-s
Copy link

@TessForGithub2 Theresa, same notes as well. Please add your comments on whether we use the PUT API as part of the Update in Store flow and then we can move this card back to the Trajectory backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants