[Bps-public-commit] RT-Extension-LDAPImport annotated tag, 0.31_01, created. 0.31_01

Kevin Falcone falcone at bestpractical.com
Tue Dec 14 11:56:09 EST 2010


The annotated tag, 0.31_01 has been created
        at  1eba1c3f49030210eef5b5eef4dd468f33a739ee (tag)
   tagging  eb93fc34a415f67d46cac26240b4cc2763499ae5 (commit)
  replaces  0.20_01
 tagged by  Kevin Falcone
        on  Tue Dec 14 11:54:12 2010 -0500

- Log -----------------------------------------------------------------
Release 0.31_1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEABECAAYFAk0HoTsACgkQ0+gKWp5CJQqWbACfXNMeCQtW/5F8I2bSB4kFuZkC
BQgAoIPJvXVTwPI+Tvmim436WbkBJZsg
=N2pP
-----END PGP SIGNATURE-----

Alex Vandiver (10):
      We don't need newline terminators in our heredoc
      Make case consistent
      Clarify username = bind DN
      Fix case, so it works on case-sensitive databases
      Add a negative cache as well
      Make the cache case-insensitive
      Simplify setting of the dnlist cache
      Merge show and actual import paths for user import
      Unify display and import paths for group import
      Give a progress report while importing

Kevin Falcone (38):
      use autoinstall
      Refactoring for upcoming groups work
      more documentation of skipping the group adding
      fix pod test
      Consider writing tests against a mock LDAP server
      Handle the magic of loading us and the RT::Test framework
      return success so we can test for it
      Rename the file and substitute current paths
      Simple round-trip testing
      We actually have multiple server tests, give this a better name
      snapshot onto a branch
      Convert to the test method that actually runs search
      pass in a mapping, rather than always using the one for Users
      Group creation
      Don't start an RT server
      Add show for groups
      Correctly add users to groups
      Respect LDAPUpdateOnly for groups
      fix missing pod
      Call the right method
      Fix a misleading warning
      actually show the group name
      Since things can go horribly wrong, skip over DNs we can't find, but warn.
      When we have a DN, use it as the base
      Be better about saying these are objects
      regex fail
      Refactoring so I can use this code in calculating the group dry run
      When not importing, show what will happen to group users
      Handle removing dead users who were removed from a group in LDAP
      Talk about group variables
      update skips
      Bump version for lots of new features
      tell people about autosetting description
      here, have a dn->username cache
      Use the cache for shows too
      Don't do a recursive user search
      LDAPUpdateOnly being 0 doesn't stop an update from happening
      Bump version for 0.31_1 and dist signing

-----------------------------------------------------------------------



More information about the Bps-public-commit mailing list