User story #3427
closed
User story #3426: Add to possibility to write the promises generation timestamp in the generated promises
Add a variable that contains the promises generation timestamp
Added by Nicolas CHARLES over 11 years ago.
Updated over 9 years ago.
Category:
Web - Config management
Description
we need a variable that stores the promises generation timestamp, but caution, we mustn't check if it changed to regenerate promises, otherwise we will always regenerate promises
The best way it probably to have an "always there" variable, handled directly at promises generation
- Status changed from In progress to 10
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/cf-clerk/pull/16
The variable name is GENERATIONTIMESTAMP
- Status changed from 10 to Pending release
- % Done changed from 0 to 100
Applied in changeset clerk:commit:c5772476ec90a167f4ecb80d0231d54706c28536.
Applied in changeset clerk:commit:b624fdb66e6405ac248c978eba9aa46117260480.
Applied in changeset clerk:commit:511ca5e9ca94ee4b7d22cc8e9bf861680b95cd30.
- Target version changed from 2.6.0~beta1 to 2.5.2
Actually, this as been done in 2.5 !
- Target version changed from 2.5.2 to 2.5.1
- Status changed from Pending release to Released
- Category changed from 14 to Web - Config management
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF