-
Notifications
You must be signed in to change notification settings - Fork 21
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
⭐️ Add GCP monitoring alert policies #805
Conversation
imilchev
commented
Jan 19, 2023
•
edited
Loading
edited
Signed-off-by: Ivan Milchev <[email protected]>
edf2f3d
to
b97b279
Compare
Signed-off-by: Ivan Milchev <[email protected]>
b97b279
to
b2ef934
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.
Really good docs, @imilchev!
} | ||
|
||
func (g *mqlGcpProject) GetMonitoring() (interface{}, error) { | ||
projectId, err := g.Id() |
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.
Is this correct?
L18 uses another function to get the projectID:
g.Id()
vs. g.ProjectId()
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.
Those are 2 different resources. On L18 we are working with mqlGcpProjectMonitoringService
that has a property projectId
. Here we are working with a mqlGcpProject
that has id
.
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.
LGTM. Thanks for the new resources