Remove deprecation handling from custom roles
authorJames Slagle <jslagle@redhat.com>
Mon, 16 Oct 2017 16:06:02 +0000 (12:06 -0400)
committerEmilien Macchi <emilien@redhat.com>
Mon, 23 Oct 2017 15:45:04 +0000 (15:45 +0000)
commit09dbd6733cba19939a51fe61e94a1162ee7883e7
tree42b9c1aed86160e77a7ffcb5aa2f61e2b6813c75
parent8da5e1f7006d8128e83fe151da930dc5a670180d
Remove deprecation handling from custom roles

For deployed-server custom roles, the deprecation handlings are removed.
As these have always been custom roles with definitions generated from
role.role.j2.yaml, these original (now deprecated) param names were
never present for anyone using this deployed-server roles data file.

Specifically, deprecated_server_resource_name is quite troublesome as it
will cause the server resources to get replaced on upgrade as the
resource name changes.

These were all introduced in If4a8388634fb1dcbb47beeabbd3db005abc80d4e,
and this commit removes them.

Change-Id: I1c1267f19db972b55466f4649eda62dd7814b94a
Closes-Bug: #1723177
(cherry picked from commit 6e7a431df0b7790512eb1920500b8878701c691a)
deployed-server/deployed-server-roles-data.yaml