ocis init with diff mode

[dragonchaser]

It would be nice add an additional diff flag to ocis init (ocis init --diff) which would, instead of creating a new ocis.yaml, output a patch that represents the changes that would be made to the config file upon re-run. This would give us the opportunity to represent breaking changes and new config variables to admins without requiring to do a deep dive into the documentation upon each major release to search for changes.

/cc @mmattel

[mmattel]

Not only on restarting with the init flag, but this could also be used like a dry-run flag on first start as the file does not extist and therefore all is in the diff ! 😄

[micbar]

Slightly related to #3917

@pmaier1 needs clarification for GA

It needs the clean deprecation of variable names in the code as a prerequisite.

[pmaier1]

After GA.

[dragonchaser]

This would also be a nice feature for L1/L2 support to run against the customers/users config and see potential errors.

[mmattel]

This would be a very helpful change with regards to the upgrading documentation and eases the upgrade process a lot.

[kobergj]

I would rather go for an automated approach: Have new command ocis upgrade (naming tbd) that does the update automatically. To be safe about breaking change this should only print out the changes it wants to do, but don't execute them. After you checked them you can then add them to your ocis config by running ocis upgrade --execute (naming tbd)

[dragonchaser]

@micbar can we move that into the next planning and talk about it?

[dragonchaser]

Closing here for now, the upgrade is more complex and we should create a separate ticket for that.