tree e4445c33659d076863b8731165d00a00afe38744
parent 3c22f342cf520b1c5d9911122260088c84a44058
parent f2d2b7a7a60017f142a87a141de12c82e263627b
author Nguyen Tuan Khang Phan <nguyen.tuan.khang.phan@ericsson.com> 1617828100 -0400
committer Nguyen Tuan Khang Phan <phan.khang5@gmail.com> 1617917273 +0000

Merge branch 'stable-3.0' into stable-3.1

* stable-3.0:
  Add Gatling e2e-test for rename-project
  Add REST endpoint to rename operation
  Adapt checks to the new rename replication feature
  Introduce rename replication feature
  RenamePreconditions: check if project state is not null
  Upgrade bazlets to latest stable-3.0 to build with 3.0.15 API
  Upgrade bazlets to latest stable-2.16 to build with 2.16.26 API
  Upgrade bazlets to latest stable-2.16 to build with 2.16.23 API

The resolution for a merge conflict in RenameCommand was to fix import
for Project and Change classes. In stable-3.1, they are under
`entities` instead of `reviewdb`.

The new testRenameReplicationViaSshAdminUser test is adapted to
stable-3.1.

Namekey is no longer instantiated with `new Project.Namekey()` but
with `Project.namekey()`.

Change-Id: I04e68aaa168e410ce08ce555102762f16a5ab57f