Go to file

Shuffle around logic for details merging (#4087 )

Shuffle around some logic for details merging so that
we always attempt to extract a LocationRef from the
backup base entry that's currently being examined.

A LocationRef should always be available from either
the LocationRef field in the details entry (newer
backups) or by extracting it from the RepoRef (older
backups)

Manually tested incremental backups for exchange in
the following scenarios:
1. v0.3.0 backup (calendars use IDs in RepoRef) ->
   incremental with this patch -> incremental with
   this patch
1. v0.2.0 backup (exchange uses folder names in
   RepoRef) -> incremental with this patch ->
   incremental with this patch

The above tests should cover the cases where:
* base backup details don't have LocationRef for
  exchange items
* base backup details have LocationRef for exchange
  items

---

#### Does this PR need a docs update or release note?

- [ ] ✅ Yes, it's included
- [ ] 🕐 Yes, but in a later PR
- [x] ⛔ No

#### Type of change

- [ ] 🌻 Feature
- [ ] 🐛 Bugfix
- [ ] 🗺️ Documentation
- [ ] 🤖 Supportability/Tests
- [ ] 💻 CI/Deployment
- [x] 🧹 Tech Debt/Cleanup

#### Issue(s)

* closes #3716

#### Test Plan

- [x] 💪 Manual
- [x] ⚡ Unit test
- [ ] 💚 E2E

2023-08-23 19:16:42 +00:00

.github

Fix log output and don't fail fast (#4076 )

2023-08-21 16:58:48 +00:00

build

[Snyk] Security upgrade alpine from 3.17 to 3 (#3402 )

2023-05-16 18:16:15 +00:00

design

remove design/cli.md; conflicts with docs (#2097 )

2023-01-11 06:28:10 +00:00

docker

[Snyk] Security upgrade ubuntu from latest to 22.10 (#3159 )

2023-04-21 04:32:57 +00:00

src

Shuffle around logic for details merging (#4087 )

2023-08-23 19:16:42 +00:00

website

⬆️ Bump sass from 1.65.1 to 1.66.1 in /website (#4072 )

2023-08-21 05:54:57 +00:00

.dockerignore

introduce docker container production (#660 )

2022-09-01 15:06:57 +00:00

.gitattributes

Add vector images for "Why Everyone Loves Corso" (#781 )

2022-09-06 22:15:15 +00:00

.gitignore

updating gitignore to catch log files (#3549 )

2023-06-01 06:06:44 +00:00

CHANGELOG.md

Export data from SharePoint (#3824 )

2023-07-28 08:40:35 +00:00

CODE_OF_CONDUCT.md

Update README and upgrade COC (#1068 )

2022-10-06 11:10:12 +00:00

LICENSE

Remove some license boilerplate (#1071 )

2022-10-06 16:43:52 +00:00

README.md

Move Corso to beta (#2566 )

2023-02-18 15:35:59 +00:00

SECURITY.md

Create a security policy (#1879 )

2022-12-20 19:58:11 +00:00

README.md

Corso Logo

Corso

Corso is the first open-source tool that aims to assist IT admins with the critical task of protecting their Microsoft 365 data. It provides a reliable, secure, and efficient data protection engine. Admins decide where to store the backup data and have the flexibility to perform backups of their desired service through an intuitive interface. As Corso evolves, it can become a great building block for more complex data protection workflows.

Corso is currently in Beta.

Corso supports M365 Exchange and OneDrive with SharePoint and Teams support in active development. Coverage for more services, possibly beyond M365, will expand based on the interest and needs of the community.

Getting Started

See the Corso Quickstart on our docs page.

Building Corso

To learn more about working with the project source core and building Corso, see the Developer section of the Corso Documentation.

Roadmap

You can learn more about the Corso roadmap and how to interpret it here.

If you have feature requests, please file a GitHub issue and attach the enhancement label to the issue.

Contribution Guidelines

Code of Conduct

It's important that our community is inclusive and respectful of everyone. We ask that all Corso users and contributors take a few minutes to review our Code of Conduct.

License

Corso is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.