Issue #22652 has been updated by Kylo Ginsberg.
We could experiment with the merged parameters approach. Though, if we're right about rack not returning a query_string for a post, that would break down if we had a post (e.g. a long URI) which included multi-instance query parameters. Another thought is to abandon the multi-instance query parameters introduced in 3.3.0 in favor of a non-yaml encoding of the array of ignores so that ignore could return to being single instance. I hadn't run into multi-instance query parameters before so wondered how common it was. This SO question has some interesting response and links: http://stackoverflow.com/questions/1746507/authoritative-position-of-duplicate-http-get-query-keys ---------------------------------------- Bug #22652: ignore doesn't work if pluginsync enabled https://projects.puppetlabs.com/issues/22652#change-98022 * Author: Daniel Wittenberg * Status: In Topic Branch Pending Review * Priority: Normal * Assignee: Kylo Ginsberg * Category: * Target version: 3.3.1 * Affected Puppet version: 3.3.1-rc1 * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1938 ---------------------------------------- /var/lib/puppet/..../.svn directories are still pushed out even if you have a global ignore File { ignore => '.svn' } Confirmed by downgrading the server to 3.2.4-1 and it all worked as expected, no .svn directories in /var/lib/puppet -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
