Skip to content

Conversation

@dsegurakaliop
Copy link

@dsegurakaliop dsegurakaliop commented Apr 17, 2025

If someone can test the integration of these new features, it will be really GREAT !

I have done all I can from my little experience in GO world.

Please be free to add your stone !

}

return nil, nil
} else if response.StatusCode == Http.StatusTooManyRequests {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a maintainer or anything but I'm interested in the addition of the missing UptimeRobot features, thanks for the PR!
I'm just wondering, why did you remove the code to handle HTTP 429 response status?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad I think

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have rollback the missing parts in the last commit.

Thanks @eneiss for your review !

I hope someone can help these features be part of the project asap.

Best regads,

Didier

@dsegurakaliop
Copy link
Author

Up !

Is someone available to review this ?

@MuneebAijaz MuneebAijaz added the ok-to-test Run tests in PR workflows label May 21, 2025
@dsegurakaliop
Copy link
Author

Up ?

@dguihal
Copy link

dguihal commented Jun 25, 2025

@dsegurakaliop I'm trying to use your PRs (but unfortunatly I'm not a maintainer so I can't help that much on merging this)

  • Launch a make fmt your code doesn't seem to be 100% compliant with golang format standards
  • Launch a make manifests, this updates implies some changes in CRDs to allow new fields. Although those aren't breaking changes (because it's addition of new, non mandatory fields), I don't know about Stakater's policy about CRDs versionning
  • This implies also a bump in chart version make bump-chart VERSION=2.2.4, althought maybe it's part of another workflow some unsure it's relevant to push updated chart versions in this PR

Eager to see this PR merged @MuneebAijaz ?

Comment on lines +330 to +334
// Alert Contacts (Optional)
if providerConfig != nil && len(providerConfig.AlertContacts) != 0 {
body += "&alert_contacts=" + url.QueryEscape(providerConfig.AlertContacts)
} else {
body += "&alert_contacts=" + url.QueryEscape(monitor.alertContacts)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be removed (duplicates of lines 231-235), generates an error: "Error: "alert_contacts" must be a string"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Comment on lines +289 to +294
// Interval (Optional, in seconds)
if providerConfig != nil && providerConfig.Interval > 0 {
body += "&interval=" + strconv.Itoa(providerConfig.Interval)
} else {
body += "&interval=" + strconv.Itoa(DefaultInterval)
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be removed (duplicates of lines 237-242), generates an error: "Error: "interval" must be a string"

@MuneebAijaz
Copy link
Contributor

Hi, will hopefully take a look at the PR this week. Thanks for the contribution

Copy link
Contributor

@Felix-Stakater Felix-Stakater left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of small changes are required before we can merge this, thanks for your contribution! :)

}

// Interval (Optional, in seconds)
if providerConfig != nil && providerConfig.Interval > 0 {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @dguihal commented we need to remove this block

Comment on lines +330 to +334
// Alert Contacts (Optional)
if providerConfig != nil && len(providerConfig.AlertContacts) != 0 {
body += "&alert_contacts=" + url.QueryEscape(providerConfig.AlertContacts)
} else {
body += "&alert_contacts=" + url.QueryEscape(monitor.alertContacts)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@dsegurakaliop
Copy link
Author

Big thanks for this active review and fixes.

Sorry if I have done some mistakes, I really want these features appears one day, and I think we are now very close !

Thanks everyone.

@dguihal
Copy link

dguihal commented Jul 16, 2025

Hi @dsegurakaliop I created a PR on your fork dsegurakaliop#1

I've managed to make this code run properly on a dev env

@mahmadmujtaba
Copy link

Hey @dguihal thanks for effort. Can you do us a favor and open pull request towards us so it can be reviewed, tested and possibly merged as enhancement?

@dguihal
Copy link

dguihal commented Oct 1, 2025

Hi @mahmadmujtaba I created #655

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Run tests in PR workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants