Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

API Guidelines blueprint#4536

Merged
mattjackson220 merged 7 commits intoapache:masterfrom
ocket8888:api-guidelines
Apr 8, 2020
Merged

API Guidelines blueprint#4536
mattjackson220 merged 7 commits intoapache:masterfrom
ocket8888:api-guidelines

Conversation

@ocket8888
Copy link
Copy Markdown
Contributor

What does this PR (Pull Request) do?

  • This PR is not related to any Issue

Adds a blueprint for some API guidelines.

Which Traffic Control components are affected by this PR?

  • Documentation

What is the best way to verify this PR?

Read the blueprint. Maybe pass it through a Markdown parser/validator/renderer if you want.

The following criteria are ALL met by this PR

  • Tests are unnecessary
  • This PR includes documentation
  • An update to CHANGELOG.md is not necessary
  • This PR includes any and all required license headers
  • This PR does not include a database migration
  • This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

@ocket8888 ocket8888 added documentation related to documentation Traffic Ops API Next Improvements to Traffic Ops API - particularly breaking changes blueprint feature requirements / implementation details labels Mar 24, 2020
@ocket8888 ocket8888 changed the title Added API Guidelines blueprint API Guidelines blueprint Mar 24, 2020
Copy link
Copy Markdown
Member

@mitchell852 mitchell852 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks really good. You covered everything very well. One thing I think you could elaborate on is that all api endpoints that modify data need to insert a legible/sensible "change log" entry to the log table with the user that made the change and when the change occurred.

Otherwise, looks really good. Thanks for putting this together.

Also, once merged. The contributing.MD file should be updated to link to this and the wiki page of the old TO guidelines should probably be deleted/archived.

Comment thread blueprints/api.guidelines.md Outdated
Comment thread blueprints/api.guidelines.md
Comment thread blueprints/api.guidelines.md
Comment thread blueprints/api.guidelines.md
Comment thread blueprints/api.guidelines.md
Comment thread blueprints/api.guidelines.md Outdated
Comment thread blueprints/api.guidelines.md
Comment thread blueprints/api.guidelines.md Outdated
@mattjackson220 mattjackson220 merged commit afe6a13 into apache:master Apr 8, 2020
@ocket8888 ocket8888 deleted the api-guidelines branch April 8, 2020 22:53
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

blueprint feature requirements / implementation details documentation related to documentation Traffic Ops API Next Improvements to Traffic Ops API - particularly breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants