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
(cherry picked from commit 79aca264ff)
This commit is contained in:
Juan Antonio Osorio Robles 2017-08-04 08:36:42 +03:00
parent eeaa235111
commit 564e3feeb9
1 changed files with 2 additions and 2 deletions

View File

@ -144,10 +144,10 @@ parameters:
Cron to purge expired tokens - Week Day Cron to purge expired tokens - Week Day
default: '*' default: '*'
KeystoneCronTokenFlushMaxDelay: KeystoneCronTokenFlushMaxDelay:
type: string type: number
description: > description: >
Cron to purge expired tokens - Max Delay Cron to purge expired tokens - Max Delay
default: '0' default: 0
KeystoneCronTokenFlushDestination: KeystoneCronTokenFlushDestination:
type: string type: string
description: > description: >