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

Enhance USS get file content to also return E-Tag #88

Closed
jordanCain opened this issue Mar 27, 2019 · 1 comment

Comments

@jordanCain
Copy link
Contributor

commented Mar 27, 2019

Currently the endpoint only returns the content of the file but in order to support modification of that data via an update API an E-Tag is required to ensure unwanted overwrites do not occur

The response of get requests should include an E-Tag header with a hash representing the files contents.

To support #83

As a USS endpoint user wanting to update a file
I want to have access to an E-Tag
so that I don't accidentaly overwrite changes to a file

Acceptance Criteria

*Scenario 1: get file contents with E-Tag
Given a Unix file with some contents
When I get the contents of the file
Then an E-Tag header should be included in the response

@jordanCain

This comment has been minimized.

Copy link
Contributor Author

commented Apr 8, 2019

completed in #89

@jordanCain jordanCain closed this Apr 8, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.