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.

Sign up for GitHub

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

Jump to bottom

MAPEX-180: Set Mapping File's last_update Field on Edit #25

Merged
merged 3 commits into from
Feb 16, 2024
Merged

MAPEX-180: Set Mapping File's last_update Field on Edit #25

merged 3 commits into from
Feb 16, 2024

Conversation

mikecarenzo
Copy link
Contributor

@mikecarenzo mikecarenzo commented Feb 15, 2024 •
edited
Loading

Fixes #180

What Changed

This PR introduces two changes:

  • A Mapping File’s last_update field is now updated after each edit.
  • A new Mapping File now only requires:
    • mapping_version
    • attack_version
    • technology_domain
    • mapping_framework
    • mapping_framework_version
    • mapping_types
    • capability_groups

Known Limitations

None

@github-actions GitHub Actions
Copy link
Contributor

This PR has been published to https://mappingseditor.z13.web.core.windows.net/MAPEX-180_set_last_update_on_edit/

@mikecarenzo mikecarenzo requested a review from emeth1 February 15, 2024 16:01
@mikecarenzo mikecarenzo merged commit 0ca0e75 into main Feb 16, 2024
2 checks passed
@mikecarenzo mikecarenzo deleted the MAPEX-180_set_last_update_on_edit branch February 16, 2024 03:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@emeth1 emeth1 emeth1 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mikecarenzo @emeth1