-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
provider/logentries: Implementing logentries provider #7067
Conversation
67d5630
to
1e8aa59
Compare
need to vendor a lib, but so far govendor just hangs on my system. so, figuring out why. |
6f89f4d
to
942723c
Compare
ok, vendoring done and the build passes. still need docs! |
documentation done. A few things to take care of:
|
cdae103
to
38474f1
Compare
OK, all above issues were addressed, removing WIP tags. This is ready to go / formal review. |
can this make it into 0.7? ;) |
38474f1
to
b088a82
Compare
Hi @dabdine-r7 Thanks so much for the patience here. I have had a review of this and it looks good. Nothing out of the ordinary. Test results:
|
thank you @stack72! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Logentries provides log management, alerting and analytics for hosts, applications and more. Accounts are free to create and are free for the terraform acceptance tests.
We use logentries internally to redirect our application logs into a centralized dashboard. This provider allows management of the tokens and log IDs (which are secrets) and allows terraform users to plug log tokens and ids into their applications and infrastructure through mechanisms such as cloud-config, etc.