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

feat: Implement Security Report endpoint #276

Merged
merged 46 commits into from
Nov 7, 2019
Merged

Conversation

RaduW
Copy link
Contributor

@RaduW RaduW commented Oct 23, 2019

Security report endpoint implementation.

@RaduW RaduW changed the title feat:(document-actors) WIP started implementation of security report feat:(security-report) WIP started implementation of security report Oct 23, 2019
@RaduW RaduW changed the title feat:(security-report) WIP started implementation of security report feat:(security-report) Security Report endpoint Oct 23, 2019
@jan-auer jan-auer changed the title feat:(security-report) Security Report endpoint feat: Implement Security Report endpoint Oct 24, 2019
untitaker and others added 26 commits October 24, 2019 11:54
* master: (26 commits)
  doc: Add documentation about the path of an event through relay (#289)
  release: 0.4.59
  meta: Changelog for 0.4.59
  ref: Set _relay_processed to true (#293)
  feat(protocol): Add valid platforms as constant (#294)
  fix(protocol): Add missing legacy alias for stacktrace (#292)
  release: 0.4.58
  meta: Add changelog for 0.4.58
  feat: Expose globbing code from Semaphore to Python (#288)
  fix: Add code comment
  fix: Normalize before datascrubbing (#290)
  feat(projects): Evict project caches after some time (#287)
  feat: Add mkdocs like in symbolicator
  ref: Add event size metrics (#286)
  test: add panic test
  ref: Selectively log internal errors to stderr (#285)
  fix(cabi): Do not ignore process_value result in scrub_event (#284)
  feat(config): Add a config value for thread counts (#283)
  fix: Refactor outcomes for parity with Sentry (#282)
  feat: Add an error boundary to parsing project states (#281)
  ...
@jan-auer jan-auer marked this pull request as ready for review November 7, 2019 09:14
Copy link
Member

@untitaker untitaker left a comment

Choose a reason for hiding this comment

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

I haven't checked whether the schema matches the rfcs/specs and whether the url normalization is correct

general/src/protocol/security_report.rs Outdated Show resolved Hide resolved
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.

None yet

3 participants