Go to file

Alternative way to handle 2-level calendars hierarchy (#2397 )

## Description

All calendars except the default are nested under a "Other Calendars" folder. Having a non-default calendar named the same as the default calendar does not cause problems when fetching the default calendar by name. Only the default calendar will be returned in that situation.

This fixes the bug where we had multiple collections for the same path but representing different folders.

Also updates the restore execution path to handle the new nested folder structure.

Backup, incremental backup, and restore flows tested manually

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

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

## Type of change

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

## Issue(s)

* #2388

## Test Plan

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

2023-02-03 23:29:55 +00:00

.github

GC: Beta Client Package (#2205 )

2023-01-31 16:38:28 +00:00

build

Update to go1.19 for corso (#1632 )

2022-12-13 21:01:55 +00:00

design

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

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

docker

Update to go1.19 for corso (#1632 )

2022-12-13 21:01:55 +00:00

src

Alternative way to handle 2-level calendars hierarchy (#2397 )

2023-02-03 23:29:55 +00:00

website

new blog post on storage options for corso (#2362 )

2023-02-03 01:12:18 +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

Issue 2329 logfile 1 (#2344 )

2023-02-02 20:34:53 +00:00

CHANGELOG.md

Alternative way to handle 2-level calendars hierarchy (#2397 )

2023-02-03 23:29:55 +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

link directly to getting started directions (#2232 )

2023-01-23 16:02:55 +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 ALPHA and should NOT be used in production.

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.