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.

Sign up for GitHub

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

Jump to bottom

Provide a way to automatically remove the old execution logs, set a TTL and document the good practice #22

Open
odupuy opened this issue Oct 17, 2017 · 0 comments
Open

Provide a way to automatically remove the old execution logs, set a TTL and document the good practice #22

odupuy opened this issue Oct 17, 2017 · 0 comments

Comments

@odupuy
Copy link

odupuy commented Oct 17, 2017

We use this plug-in and we accumulate a lot of execution logs in S3 (400K 1.6 GB in our dev environment).

I could set an expiration policy on the S3 bucket itself taking care of that, e.g. a one-week retention. The question is about any possible side effect for RunDeck. There is a database too (MySQL for us), is it possible that removing the files in S3 w/o updating could have an impact?

Can you document in the README the good practice in this regard?
Thanks
@odupuy odupuy changed the title Provide a way to automatically remove the old execution logs or document the good practice Provide a way to automatically remove the old execution logs, set a TTL and document the good practice Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@odupuy