Create schema of same name when user is created about ldap2pg HOT 6 CLOSED

I'm thinking of extending ldap2pg to help managing this case. Here is an idea:

- role:
    name: '{cn}'
    on_create: |
      CREATE SCHEMA {role};
    on_alter: |
      ALTER SCHEMA {old} RENAME TO {new};
    on_drop: |
      DROP SCHEMA {role} CASCADE;

@bersace, is it still considered ? This looks quite interesting. Would definitely be useful for me !

from ldap2pg.

Hi @joshlk actually, you can already do this by hacking the ACL mechanism :-) Just think grant as create and revoke as drop. This should look like:

acls:
  user_schema:
    type: datacl
    inspect: |
      SELECT NULL as "schema", rolname
      FROM pg_namespace n
      JOIN pg_authid ON rolname = nspname
    grant: |
      CREATE SCHEMA {role};
      ALTER USER {role} SET search_path {role},public;

sync_map:
- role: myuser
  grant:
    acl: user_schema
    database: mydb
    role: myuser

YMMV

from ldap2pg.

I'm thinking of extending ldap2pg to help managing this case. Here is an idea:

- role:
    name: '{cn}'
    on_create: |
      CREATE SCHEMA {role};
    on_alter: |
      ALTER SCHEMA {old} RENAME TO {new};
    on_drop: |
      DROP SCHEMA {role} CASCADE;

What do you think of it ? Would you prefer global on_create, on_drop ? Thanks for the feedback.

from ldap2pg.

Another solution would be the allows override of queries :

postgres:
  queries:
    role_create: |
      CREATE ROLE "{role}" WITH {options};
      COMMENT ON ROLE "{role}" IS '{comment}';
      CREATE SCHEMA "{role}";
      ALTER ROLE "{role}" SET search_path = "{role}",public;

from ldap2pg.

Would you prefer global on_create, on_drop ? Thanks for the feedback.

I would like to see both. Some queries might be useful on a global level, others just for specific roles.

from ldap2pg.

Closing in favor of #565.

from ldap2pg.