Issue #7934 has been updated by Nigel Kersten.
Status changed from Unreviewed to Needs More Information
Oh that's crap.
What's the most desirable behavior here?
We always upload the current file to the bucket?
or we look at the setting used for inspect:
<pre>
# During an inspect run, whether to archive files whose contents are
audited to a file bucket.
# archive_files = false
</pre>
and if that's on, we upload the current file?
In any case, we shouldn't be linking to the bucket for files that probably
aren't uploaded there (unless a previous run uploaded something with the same
checksum :( )
----------------------------------------
Bug #7934: Filebucket view does not work with the current file
https://projects.puppetlabs.com/issues/7934
Author: Peter Meier
Status: Needs More Information
Priority: Normal
Assignee:
Category:
Target version:
Keywords:
Branch:
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.
