Activity
From 2012-06-26 to 2012-06-26
2012-06-26
- 23:46 Bug #2606 (Pending technical review): apacheServer technique uses illegal log level log_error
- Applied in changeset commit:e14a27bb25f130876e31106c7693cb65ae820cdb.
- 23:45 Bug #2606 (Released): apacheServer technique uses illegal log level log_error
- This should be "result_error" instead, log_error doesn't exist
- 23:46 Revision 3734316c (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
s/log_error/result_error/ in apacheServer. Fixes #2606 - 23:46 Revision aa7c16c9 (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
s/log_error/result_error/ in apacheServer. Fixes #2606 - 23:45 Revision e14a27bb (rudder-techniques): s/log_error/result_error/ in apacheServer. Fixes #2606
- 23:42 Architecture #2605 (Pending technical review): rudder-techniques check script should detect illegal log level "log_error"
- Applied in changeset commit:a0b1c4c889da1646103f388c2f311b5acc8230a8.
- 23:33 Architecture #2605 (Released): rudder-techniques check script should detect illegal log level "log_error"
- Sometimes in Techniques it's tempting to use log level "log_error", when we should be using "result_error".
This s... - 23:33 Revision a2215c9f (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Add test for log level log_error. Fixes #2605 - 23:33 Revision 6ce97b68 (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Add test for log level log_error. Fixes #2605 - 23:33 Revision a0b1c4c8 (rudder-techniques): Add test for log level log_error. Fixes #2605
- 23:18 Revision 3a40dd18 (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Refs #2600 Remove colon in section's description in Directive Management - 23:18 Revision c5d65d3a (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Refs #2600 Remove colon in section's description in Directive Management - 23:00 User story #2255 (Discussion): PT distributePolicy: apacheCheck: The WebDAV access for the inventories on the rudder should only give access to the Rudder allowed networks
- I am bothered by several things in this change:
* log_error is not a valid log level, only result_error exists (any ... - 22:43 User story #2255 (Pending technical review): PT distributePolicy: apacheCheck: The WebDAV access for the inventories on the rudder should only give access to the Rudder allowed networks
- Applied in changeset commit:dcac738a247455d55680b5192cc0ff944980cc73.
- 22:47 Bug #2568 (Released): rudder-webapp and rudder-inventory-endpoint use "settings-internal.xml" by default causing the build to fail outside of Normation
- 22:44 Bug #2600 (Released): Description problem in Directive Management
- 12:04 Bug #2600 (Pending technical review): Description problem in Directive Management
- 11:53 Bug #2600 (Released): Description problem in Directive Management
- The word "optional" appear twice and the first one is a typo:
!capture_description_bug.png! - 22:43 Bug #2552 (Pending technical review): (ex PT/ Technique) User Management: If a user is defined to be checked and with password defined too, the password of this user will be redefined
- Applied in changeset commit:bc53667495e66c049c6d4ea099599cd486a54c2a.
- 22:43 Architecture #2555 (Pending technical review): (ex PT/ Technique) Group Management: Enhance comments , varaiables relevance and classes for reporting
- Applied in changeset commit:ebe61d7021a3a39944339fe3062d35fbcd31ab8e.
- 22:43 Bug #2554 (Pending technical review): (ex PT/ Technique) User Management: Users on Windows can't be removed
- Applied in changeset commit:f11c33df27ad61704d36d3bf6d9ade9994110f78.
- 22:43 Architecture #2553 (Pending technical review): (ex PT/ Technique) User Management: Add comments and more standard variable names
- Applied in changeset commit:1e072460ad6e6fa6ee43197e335f82295270909d.
- 21:11 Bug #2582: When using a \ in a report key, the value is not correctly inserted in the database
- One last attempt :
Alter database Rudder set standard_conforming_strings=false;
$$ $$ string
with an SQL encodin... - 20:47 Bug #2582: When using a \ in a report key, the value is not correctly inserted in the database
- Several attempt to correct this issue.
On the scala side, 'base becomes 'base in the SQL, and \base becomes \\base
... - 20:18 User story #2604 (Released): Be able to NOT historize inventories
- Today, each time we get an inventory through the inventory-web webapplication, an archive of the LDIF for that invent...
- 18:41 Architecture #2603 (Released): Add new table for archived reports when migrating to Rudder 2.4
- On Rudder 2.4, If I try to go to database management (Administration -> Database Management) , the page only show thi...
- 18:12 User story #2132: Improve process for upgrading techniques
- The first first step is to cleanup the property file to be able to know what are the relevant properties for the git ...
- 18:12 Architecture #2602 (Released): Clean-up Rudder configuration.properties
- The main Rudder configuration.properties is full of non documented, out-of-date crap that limits a lot the possibilit...
- 16:54 Revision 26fc5b05 (rudder): Ref #2581 Json research fixed + Json research with regex + display fixing
- 16:54 Revision f75fd9f2 (rudder): Ref #2581 Json research fixed + Json research with regex + display fixing
- 16:10 Revision f7fbbe22 (rudder-techniques): Refs #2600 Remove colon in section's description in Directive Management
- 15:41 Revision 267c4b22 (rudder): Ref #2581 removes json class hints, corrects spelling
- 15:41 Revision 267c4b22 (ldap-inventory): Ref #2581 removes json class hints, corrects spelling
- 13:47 Architecture #2601 (Backlog): Show form errors in a appropriate place in Directive Management
- Errors are shown in the top of the form, not near the input that cause the problem.
For example, if the user creat... - 13:26 Revision 48397015 (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Followup to previous merge, rename policy.xml to metadata.xml and contents too - 13:26 Revision 96aa62ed (rudder-techniques): Followup to previous merge, rename policy.xml to metadata.xml and contents too
- 13:21 Revision 2c2ee4ec (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Followup to previous merge: move policies to techniques
Fixes #2600 Correct description pr... - 13:20 Revision 38c54c92 (rudder-techniques): Followup to previous merge: move policies to techniques
- 13:18 Revision 13d3b915 (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Fixes #2600 Correct description problem in Directive Management
Fixes #2488: Enabled the u... - 11:53 Revision 3c4481e1 (rudder-techniques): Fixes #2600 Correct description problem in Directive Management
- If we want to know if a section in a Technique is optional or not we
can check the value in <MAYBEEMPTY></MAYBEMPTY> - 10:50 Revision 87e63649 (rudder): Ref #1769 Correct tooltips in Technique Management and improve CSS
- 10:50 Revision cb01cff4 (rudder): Ref #1769 Correct tooltips in Technique Management and improve CSS
Also available in: Atom