#50516 Plugin class should be more robust
Opened 11 months ago by vashirov. Modified 4 months ago

Issue Description

Some plugins have their config pre-created in dse.ldif template, some don't. When a Plugin object is created, it doesn't check the presence of the config dn. And we end up writing supporting code for each case. Plugin class should check if the config dn is present, and create it if not.


There is already a stateful "create" option which is "create if not exist, or update to match this definition" as part of DSLdapObject, so you just need to use that function instead of create. It's "ensure_state".

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

11 months ago

Shouldn't we use it by default for plugins then?

Yes we should ... I think that this function was made "after" people started using create, and maybe didn't know it existed.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.1

10 months ago

Metadata Update from @firstyear:
- Issue assigned to firstyear

10 months ago

Metadata Update from @firstyear:
- Assignee reset

10 months ago

Metadata Update from @mreynolds:
- Issue priority set to: minor
- Issue set to the milestone: 1.4.3 (was: 1.4.1)

4 months ago

Login to comment on this ticket.

Metadata