Wrong updated/created date for sensu-influxdb-handler versions about bonsai HOT 7 CLOSED

Thanks @ccressent - we'll take a look. CC @pzupan

from bonsai.

All of the versions for sensu-influxdb-handler have a created and updated date of Feb. 25, so it appears the view is working properly.

from bonsai.

@pzupan can you clarify what those dates are or where they are coming from then? They don't seem to correspond to anything related to the git/github/release activities, be it for sensu-influxdb-handler or sensu-pagerduty-handler.

from bonsai.

It sounds like those dates are generated at the time the asset is added to bonsai, which is the native behavior of rails. Is this limited to Enterprise hosted assets? Perhaps the file importn(as opposed to the github import) is not capturing a relevant date.

from bonsai.

I'm not sure what the original intent was with those 2 dates on the right hand side, but here are a few notes as a (new) Bonsai user:

• Created on can either be:

  1. the date when the asset page was created on Bonsai
  2. the date when that particular version was released on github
  3. the date when that particular release was added to Bonsai
     That should be the same as ii. anyway.

• Updated can either be:

  1. the date when the asset page was updated on Bonsai
  2. the date when that particular version was updated on github
     That shouldn't happen since we would just make a new release, bumping the patch version up.
  3. the date when that particular version was updated on Bonsai
     That should be the same as ii. anyway.

Right now I don't know which combination of the above is being used because not all the pages appear to be working the same way: take sensu-influxdb-handler and sensu-pagerduty-handler; the former keeps the same "updated" date across all the versions one picks while the later changes the "updated" date depending on the version one picks.

Also, even if the dates change like on the page for sensu-pagerduty-handler, last time I checked those dates did not necessarily correspond to anything in git/github anyway.

from bonsai.

@ccressent I think you are correct. The only comment I can add is that Bonsai is changing the updated date anytime the asset is re-compiled, so that is why you're seeing some assets with an updated date different than the created date (note I have not confirmed this, but this is the standard configuration in rails).

from bonsai.

It's unclear if this has been resolved, however we should revisit what metadata is even displayed on the asset pages and address any issues at that time.

from bonsai.