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 update to member cities #2

Merged
merged 57 commits into from
Jun 22, 2020

Conversation

schnuerle
Copy link
Owner

No description provided.

Retzoh and others added 30 commits March 6, 2020 17:47
According to the RFC : https://tools.ietf.org/html/rfc7231#section-6.3.1
the HTTP response for an update (that does not create any object) can
either be 200 (OK) or 202 (ACCEPTED)
The later "indicates that the request has been
accepted for processing, but the processing has not been completed."

Since updating the vehicle_id should be quite fast, we should use a 200
response code.
Update the README with a link to the Mobility Data Management State of Practice wiki, managed by the Privacy, Security, and Transparency Committee.
Update `README.md` to reflect the City of Austin's latest MDS ETL library.
…ch-1

Release 0.4.1 patch 1 - beta, vehicles, doc clarification
Add link to State of Practice Wiki
Move Code of Conduct to External Repo
Move Release Guidelines to External Repo
Update References to Austin's MDS Repos
Agency: Add missing link in table of content
Agency: vehicle register: add optional provider_id field
Agency: clarify vehicle endpoint requirements (required vs optional)
…te_response_status_code

agency: Vehicle Update response code should be 200
@schnuerle schnuerle merged commit 6a6ff42 into schnuerle:ms-member-cities Jun 22, 2020
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

Successfully merging this pull request may close these issues.

5 participants