Use number for KeystoneCronTokenFlushMaxDelay instead of string
authorJuan Antonio Osorio Robles <jaosorior@redhat.com>
Fri, 4 Aug 2017 05:36:42 +0000 (08:36 +0300)
committerJuan Antonio Osorio Robles <jaosorior@redhat.com>
Mon, 7 Aug 2017 08:28:23 +0000 (08:28 +0000)
commit79aca264fff6126edd98d480c2233cbddac64432
tree9dd2f1a4d01582f49142473db4b2f2f9d1393fd1
parent5bf7d6582b2346a9c1671430ebead6c358508863
Use number for KeystoneCronTokenFlushMaxDelay instead of string

Using a string results in an erroneous check in puppet-keystone, which
sets up a zero where it shouldn't. So we change it to number to avoid
that. Note that there will also be a puppet-keystone fix for this.
Changing the value here assures that deployers only give valid values to
this parameter.

Change-Id: I00823e23358df91ce54f421c12636f05d4196e15
Closes-Bug: #1708584
puppet/services/keystone.yaml