Jira (PUP-6770) Method #uniqueness_key computes different results for the same resource.

[Thomas Hallgren (JIRA)]

Thomas Hallgren created an issue

Puppet / PUP-6770 Method #uniqueness_key computes different results for the same resource. Issue Type: Bug Assignee: Unassigned Created: 2016/10/04 5:38 AM Priority: Normal Reporter: Thomas Hallgren A resource defined as File['/tmp/test/'] will yield different results for the #uniqueness_key when the resource is added to the catalog as a result of a compilation and added to a catalog as the result of a call to Catalog#to_ral. The former case will retain the trailing slash in the key whereas the latter will remove it. This is a problem because a compile might add two resource to the catalog (same path, but with and without trailing slash) and a subsequent apply will then crash on an alias conflict. The solution probably involves a rewrite of the logic dealing with namevar and parameters. Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Maggie Dreyer (JIRA)]

Maggie Dreyer updated an issue

Puppet / PUP-6770 Method #uniqueness_key computes different results for the same resource.

Change By: Maggie Dreyer Labels: triaged

Add Comment

[Lindsey Smith (JIRA)]

Lindsey Smith updated an issue

Puppet / PUP-6770 Method #uniqueness_key computes different results for the same resource.

Change By: Lindsey Smith Team: Puppet Developer Experience Platform Core

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-6770 Method #uniqueness_key computes different results for the same resource.

Change By: Josh Cooper Epic Link: PUP-7548

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)