Issue #7934 has been updated by Nigel Kersten.
Part of the problem here is that we're using terms like "most" and "some". Luke, how often do you change file content _to_ a state that was previously a _from_ state for a file resource that changed? I really think this is a tiny proportion of the time for most people, and so the first case really is "almost all the time" rather than "most". ---------------------------------------- Bug #7934: Dashboard shouldn't link to the current file in the filebucket, as it won't be available. https://projects.puppetlabs.com/issues/7934 Author: Peter Meier Status: In Topic Branch Pending Merge Priority: High Assignee: Category: Target version: 1.x Keywords: Branch: https://github.com/jhelwig/puppet-dashboard/tree/ticket/1.2rc/7934-hide-file-bucket-link-for-new-files Affected URL: Affected Dashboard version: Within the report for each file-content-md5sum dashboard is showing a link to retrieve the content from the filebucket. However, as puppet is (imho) only uploading the old (changed) file to the filebucket, you are never able to view the latest (currently active) file. You also get a ups something went wrong screen on that link, which is not that nice -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
