Jira (PDB-4346) Update sync deduplication to account for configure-expiration commands

Zachary Kent (JIRA)

unread,

Apr 17, 2019, 12:18:03 PM4/17/19

to puppe...@googlegroups.com

Zachary Kent updated an issue

PuppetDB /

PDB-4346

Update sync deduplication to account for configure-expiration commands

Change By:	Zachary Kent

When merging up the sync deduplication work we forgot to add an entry for configure-expiration commands to the lookup map used to populate the atom that tracks the contents of the queue. We'll need to fix this so configure-expiration commands are properly tracked. As a result configure-expiration commands will be duplicated across sync restarts.

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Zachary Kent (JIRA)

unread,

Apr 17, 2019, 12:18:11 PM4/17/19

to puppe...@googlegroups.com

Zachary Kent assigned an issue to Zachary Kent

PuppetDB /

PDB-4346

Update sync deduplication to account for configure-expiration commands

Change By:	Zachary Kent
Assignee:	Zachary Kent

Add Comment

Zachary Kent (JIRA)

unread,

Apr 17, 2019, 12:53:25 PM4/17/19

to puppe...@googlegroups.com

Zachary Kent created an issue

PuppetDB /

PDB-4346

Update sync deduplication to account for configure-expiration commands

Issue Type:	Bug
Assignee:	Unassigned
Created:	2019/04/17 9:12 AM
Priority:	Normal
Reporter:	Zachary Kent

When merging up the sync deduplication work we forgot to add an entry for configure-expiration commands to the lookup map used to populate the atom that tracks the contents of the queue. We'll need to fix this so configure-expiration commands are properly tracked.