tree 7f97ea4701184e8c3c80ca7f5b8a27fadb09da4b
parent 33bc8b6464b4a35deff7678b77ec0f6a243dc244
author Antonio Barone <syntonyze@gmail.com> 1609252419 +0100
committer Antonio Barone <syntonyze@gmail.com> 1609324649 +0000

single-master: define volume names in mappings

Volume names were defined as parameters even though they were never set
in the Makefile. Cloudformation was barely relying on the default value.

The name of the volumes is hardly a parameter and changing it would
break the deployment since the ec2 instance's userdata (defined in the
cluster stack) is using static names for them, such as 'gerrit-cache',
'gerrit-data'.

Using Mappings is a more appropriate way to define the name of the
volumes, it avoids repetition, without consuming precious space in
the parameter list (only 65 parameters are allowed in cloudformation)
and risking misconfigurations.

Change-Id: Iaf1b801187f6bd51085b621e0a330156cc7fc0c4