Changes in 1.3.0 Tech Preview

Summary

• Bugfix - Purposely delay accounts service startup: #1734
• Bugfix - Add missing gateway config: #1716
• Bugfix - Fix accounts initialization: #1696
• Bugfix - Fix the ttl of the authentication middleware cache: #1699
• Change - Update ownCloud Web to v2.0.1: #1683
• Change - Update ownCloud Web to v2.0.2: #1776
• Enhancement - Remove the JWT from the log: #1758
• Enhancement - Update go-micro to v3.5.1-0.20210217182006-0f0ace1a44a9: #1670
• Enhancement - Update reva to v1.6.1-0.20210223065028-53f39499762e: #1683
• Enhancement - Add initial nats and kubernetes registry support: #1697

Details

• Bugfix - Purposely delay accounts service startup: #1734

  As it turns out the race condition between accounts <-> storage-metadata still remains.
  This PR is a hotfix, and it should be followed up with a proper fix. Either:

  • block the accounts' initialization until the storage metadata is ready (using the registry)
    or - allow the accounts service to initialize and use a message broker to signal the accounts the
    metadata storage is ready to receive requests.

  #1734

• Bugfix - Add missing gateway config: #1716

  The auth provider ldap and oidc drivers now need to be able talk to the reva gateway. We added
  the gatewayscv to the config that is passed to reva.

  #1716

• Bugfix - Fix accounts initialization: #1696

  Originally the accounts service relies on both the settings and storage-metadata to be up
  and running at the moment it starts. This is an antipattern as it will cause the entire service to
  panic if the dependants are not present.

  We inverted this dependency and moved the default initialization data (i.e: creating roles,
  permissions, settings bundles) and instead of notifying the settings service that the
  account has to provide with such options, the settings is instead initialized with the options
  the accounts rely on. Essentially saving bandwith as there is no longer a gRPC call to the
  settings service.

  For the storage-metadata a retry mechanism was added that retries by default 20 times to
  fetch the com.owncloud.storage.metadata from the service registry every 500
  miliseconds. If this retry expires the accounts panics, as its dependency on the
  storage-metadata service cannot be resolved.

  We also introduced a client wrapper that acts as middleware between a client and a server. For
  more information on how it works further read here

  #1696

• Bugfix - Fix the ttl of the authentication middleware cache: #1699

  The authentication cache ttl was multiplied with time.Second multiple times. This
  resulted in a ttl that was not intended.

  #1699

• Change - Update ownCloud Web to v2.0.1: #1683

  Tags: web

  We updated ownCloud Web to v2.0.1. Please refer to the changelog (linked) for details on the web
  release.

  #1683
  https://github.com/owncloud/web/releases/tag/v2.0.1

• Change - Update ownCloud Web to v2.0.2: #1776

  Tags: web

  We updated ownCloud Web to v2.0.2. Please refer to the changelog (linked) for details on the web
  release.

  #1776
  https://github.com/owncloud/web/releases/tag/v2.0.2

• Enhancement - Remove the JWT from the log: #1758

  We were logging the JWT in some places. Secrets should not be exposed in logs so it got removed.

  #1758

• Enhancement - Update go-micro to v3.5.1-0.20210217182006-0f0ace1a44a9: #1670

  • We updated from go micro v2 (v2.9.1) go-micro v3 (v3.5.1 edge). - oCIS runtime is now aware of
    MICRO_LOG_LEVEL and is set to error by default. This decision was made because ownCloud,
    as framework builders, want to log everything oCIS related and hide everything unrelated by
    default. It can be re-enabled by setting it to a log level other than error. i.e:
    MICRO_LOG_LEVEL=info. - Updated protoc-gen-micro to the latest
    version. -
    We're using Prometheus wrappers from go-micro.

  #1670
  asim/go-micro#2126

• Enhancement - Update reva to v1.6.1-0.20210223065028-53f39499762e: #1683

  • quota querying and tree accounting cs3org/reva#1405

  #1683
  cs3org/reva#1405

• Enhancement - Add initial nats and kubernetes registry support: #1697

  We added initial support to use nats and kubernetes as a service registry using
  MICRO_REGISTRY=nats and MICRO_REGISTRY=kubernetes respectively. Multiple nodes can
  be given with MICRO_REGISTRY_ADDRESS=1.2.3.4,5.6.7.8,9.10.11.12.

  #1697