Activity
From 2012-02-01 to 2012-02-01
2012-02-01
- 23:35 Bug #2230 (Pending technical review): Packages rudder-webapp and rudder-inventory-endpoint download maven on each build
- Applied in changeset commit:b618de07b982e3b2e427e07d4456b8fed80a6dcf.
- 23:29 Bug #2230 (Released): Packages rudder-webapp and rudder-inventory-endpoint download maven on each build
- The SOURCES/Makefile doesn't seem to realize that Maven doesn't need to be redownloaded every single time from the in...
- 23:35 Bug #2225: PT fileManagement: missing report for component "File" when cleaning files
- Applied in changeset commit:9f8004e2c4b8422ef191ba65f8ac882446276eeb.
- 18:09 Bug #2225 (Pending technical review): PT fileManagement: missing report for component "File" when cleaning files
- Applied in changeset commit:edee3c046fa6643bdde8968d40ba4b61b40681ad.
- 23:29 Revision b618de07 (rudder-packages): Avoid downloading Maven on each and every run. Fixes #2230
- 23:28 Revision 9f8004e2 (rudder-techniques): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Fixes #2225: The reporting on fileManagement is now handling correctly a clean only operation - 23:13 Bug #2056 (Released): Remove warnings due to pom error
- I guess this is valid
- 23:11 Bug #2193 (Released): When a non modified CR is saved, that leads to a git archiver error
- I guess this is correct, thank you Francois
- 23:09 Architecture #2097: Remove cf-clerk parent, only keep cf-clerk core
- This looks ok, thank you francois
- 23:08 User story #1978: We should be able to reload the dynamic groups manually
- This looks valid, thank you
- 22:39 User story #2213: PT distributePolicy: LDAP password synchronization
- Matthieu CERDA wrote:
> Well, I do not see where an interference might be possible, I am only injecting the same var... - 18:39 User story #2213 (Discussion): PT distributePolicy: LDAP password synchronization
- Well, I do not see where an interference might be possible, I am only injecting the same variables the restart bundle...
- 19:56 User story #2228 (Pending technical review): Add a rest API to archive/restore items
- Applied in changeset commit:3b08a9bc8e2fa26b469d71babdeb5e508ada8147.
- 19:56 User story #2228: Add a rest API to archive/restore items
- Update the list of available action, taking into account the remark by Jon.
- 17:26 User story #2228: Add a rest API to archive/restore items
- We really need a simple shortcut aswell, like : /api/archives/restore/all/latest
- 17:21 User story #2228 (Released): Add a rest API to archive/restore items
- We want a rest API to import and export items:
Archiving:
* */api/archives/archive/groups*
** export node groups... - 19:56 Bug #2229 (Pending technical review): The tagger name of archive is not the good one
- Applied in changeset commit:5fdca26d4ddf16baf8efc0dd762c2ba74258f865.
- 18:53 Bug #2229 (Released): The tagger name of archive is not the good one
- The tagger name is the system one, not the actual user archiving an item.
- 19:49 Revision 3b08a9bc (rudder): Fixes #2228: add a rest API of archiving/restoring archives
- 18:54 Revision 5fdca26d (rudder): Fixes #2229: add the good tagger name when items are archived
- 18:44 User story #1972: Packaging : provide tarball
- In fact the initial question should have been better phrased as :
Could you provide a tarball with everything in ord... - 18:22 User story #2207 (Pending technical review): PT distributePolicy : Implement the SuSE postgresql configuration hack in the distributePolicy
- Applied in changeset commit:47e42328db5c6d269bd06ed415fd91cc7d01277f.
- 18:12 User story #2207 (In progress): PT distributePolicy : Implement the SuSE postgresql configuration hack in the distributePolicy
- Indeed. I'll fix it right away.
- 18:22 Revision 47e42328 (rudder-techniques): Fixes #2207: The reports on distributePolicy now outputs some details when PostgreSQL has been restarted or failed to
- 18:09 Revision edee3c04 (rudder-techniques): Fixes #2225: The reporting on fileManagement is now handling correctly a clean only operation
- 18:05 Bug #2218: PT checkGenericFileContent version 2.1 is completely broken!
- The CFEngine template now looks fine, thanks Matthieu.
However I'm not so sure about the policy.xml file. Comparin... - 17:36 Bug #2218: PT checkGenericFileContent version 2.1 is completely broken!
- Applied in changeset commit:ad0e3e490d1492598c45821e772ab5cdc4b64362.
- 17:34 Bug #2218: PT checkGenericFileContent version 2.1 is completely broken!
- Applied in changeset commit:d9fdf12891620c4dde6c91c705cd2741e687f3d2.
- 16:56 Bug #2218: PT checkGenericFileContent version 2.1 is completely broken!
- Applied in changeset commit:fe8590b6eb6d7dc1e0418115b1ea9a0218289b55.
- 16:55 Bug #2218 (Pending technical review): PT checkGenericFileContent version 2.1 is completely broken!
- Applied in changeset commit:5564abd8d5a546e8a1ba121f15aff147cf7696fd.
- 17:50 User story #2209 (Released): PT distributePolicy : Copy the logrotate configuration if not present
- 17:50 User story #2209: PT distributePolicy : Copy the logrotate configuration if not present
- 17:49 Revision 22c55c05 (rudder-packages): logrotate file is now kept in the PT repo. Get it from there to avoid duplication. Refs #2209
- 17:36 Revision ad0e3e49 (rudder-techniques): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Refs #2218: TRIVIAL, cosmetic refactoring (indentation)
Fixes #2218: The PT checkGenericFi... - 17:34 Revision 2bd03526 (rudder-techniques): Refs #2218: TRIVIAL, cosmetic refactoring (indentation)
- 17:27 Revision d9fdf128 (rudder-techniques): Fixes #2218: The PT checkGenericFileContent has been repaired (version 2.1)
- 17:19 Revision e3b62b24 (rudder-techniques): Revert "Fixes #2218: The PT checkGenericFileContent has been repaired (version 2.1)"
- This reverts commit 5564abd8d5a546e8a1ba121f15aff147cf7696fd.
Reason: ugly diff - 17:11 User story #2227 (Pending technical review): On PI management screen, only open root node of tree by default
- Applied in changeset commit:f6e212962fba0c8251e9093ad798a61120b66239.
- 17:10 User story #2227 (Released): On PI management screen, only open root node of tree by default
- When we load Policy management screen, we don't want to have the tree of Category/PT/PI open, it's huge and overwhelm...
- 17:10 Revision f6e21296 (rudder): Fixes #2227: only open root node of policy instance tree
- 16:56 Revision fe8590b6 (rudder-techniques): Merge branch 'branches/rudder/2.3'
- * branches/rudder/2.3:
Fixes #2218: The PT checkGenericFileContent has been repaired (version 2.1) - 16:55 User story #2019 (Released): Add the proxy related options to the rug/ZMD Policy Template
- 16:53 User story #2019: Add the proxy related options to the rug/ZMD Policy Template
- 16:55 Revision 5564abd8 (rudder-techniques): Fixes #2218: The PT checkGenericFileContent has been repaired (version 2.1)
- 16:34 User story #2030 (Released): Extend rpmPackageInstallation PT to check that ZMD is running
- 16:34 User story #2030: Extend rpmPackageInstallation PT to check that ZMD is running
- 16:34 Revision e7557855 (rudder-techniques): PT rpmPackageInstallation: Clarify some reports. Refs #2030
- 16:31 Bug #2065 (Released): cloned url in packaging for github are wrong
- 15:51 User story #2226 (Backlog): Allow eventlog to go to syslog or audit log systems
- For now, event log[1] are only stored in the database.
It would be cool to allow plugins to output them into other ...
Also available in: Atom