-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat(alerts): add preset alert logdna_alert
as a data source
#31
Conversation
05cb20e
to
c08e5bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks awesome, I've added a question below.
c08e5bd
to
99867a3
Compare
d1fb1d9
to
665765c
Compare
logdna/resource_view_test.go
Outdated
category1 := "DEMOCATEGORY1" | ||
category2 := "DemoCategory2" | ||
category1 := "category1" | ||
category2 := "category2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changing these will require changes on the integration account in production - is there a reason for switching these?
also iirc these were set up with mixed casing specifically for testing that scenario
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mdeltito nah this was just a byproduct of troubleshooting the tests, I was using the service key for the LogDNA Canary
account in production instead of the MDT-terraform
account which is why the Jenkins builds weren't passing. This took me an unfortunate amount of time to figure out since the local testing didn't 100% align with the build results.
Reverted my changes since the tests were already correct initially.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of the MDT-terraform account
@david-ly the CI account is named:
Terraform Plugin Provider Tests (terraform-provider-logdna)
we should get that into the docs and make sure it's available to everyone (edit: done, opened it up)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Access control is wide open, I've confirmed. Looks like just a doc issue now.
Allow members with an @logdna.com email to join this organization without a request.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, thanks for clarifying. I'll add this to the docs in a future PR
053c1b5
to
ed0cf7a
Compare
Creates a `logdna_alert` data source which provides support for remotely fetching information from existing preset alerts. Added tests, updated the documentation, and included it in the provider. Semver: minor Ref: LOG-10590
ed0cf7a
to
7cfd622
Compare
Outdated and currently blocking merge
Creates a
logdna_alert
data source which provides support forremotely fetching information from existing preset alerts. Added
tests, updated the documentation, and included it in the provider.
Semver: minor
Ref: LOG-10590