Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to ingest files restored from Glacier #199

Closed
magical-travvo opened this issue Mar 6, 2020 · 3 comments
Closed

Unable to ingest files restored from Glacier #199

magical-travvo opened this issue Mar 6, 2020 · 3 comments

Comments

@magical-travvo
Copy link
Contributor

When trying to ingest files from S3 that have been temporarily restored from Glacier, they are ignored by this input, as files are excluded based on being in the "Glacier" storage class.

Restored files still remain in a "Glacier" storage class, but include additional metadata indicating that they are temporarily available. We regularly archive data processed by Logstash to S3 using the logstash-s3-output plugin, and it would be helpful to be able to easily reingest that data once a restore has been completed.

  • Version: 6.8.3
  • Operating System: CentOS 7
  • Steps to Reproduce: Restore file from Glacier, try to restore
@magical-travvo
Copy link
Contributor Author

I've raised #197 to address the issue.
I'm not sure why the builds are failing. The tests all pass locally.

@kares
Copy link
Contributor

kares commented Mar 6, 2020

failures are failing due a new major (2.0) of the devutils gem.
we'll be addressing the issue shortly (on master) ... you should be able to rebase afterwards.

@kares kares closed this as completed Mar 17, 2020
@kares
Copy link
Contributor

kares commented Mar 17, 2020

fix delivered at #197 and available since 3.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants