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.

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

Looking for another maintainer #500

Open
jantman opened this issue Oct 25, 2020 · 13 comments
Open

Looking for another maintainer #500

jantman opened this issue Oct 25, 2020 · 13 comments

Comments

@jantman
Copy link
Owner

jantman commented Oct 25, 2020

I've been going through some personal difficulties lately, and it's clear from the number of open issues and PRs on this project that I don't currently have the time to dedicate to awslimitchecker that it deserves, especially given all of the recent activity and interest.

If there's anyone who's familiar with the project, has contributed before, and willing uphold the 100% code coverage requirement for unit tests, please contact me. The development documentation should be pretty complete, though the release process is pretty wonky. To begin with, I'd ask someone to stage the next release in a branch, more or less ready-to-go, and I'd kick off the release. Assuming that goes well, we'll talk about commit access.

@robpickerill
Copy link
Contributor

Hi @jantman - I'm sorry to hear this. Let me take the opportunity to thank you for all your effort here.

I'm just checking in, is this still the case - your looking for support? I'd be happy to help here in any way I can. I've been looking for something to monitor AWS Limits, and this has ticked a lot of boxes for me. I've been working on a fork, but I'd be happy to help here.

@jantman
Copy link
Owner Author

jantman commented Apr 11, 2021

@robpickerill Rob, I'm definitely still looking for help with this. Lots of things have come together in the past year that have prevented me from working more on it, which I do feel bad about. But I've been spending most of my personal time on other, non-software interests, and my current day job has made a lot of progress moving to a bunch of much smaller AWS accounts, so we have less and less use for this project.

I'd be very happy for any help that you could offer. For starters, if you have stuff in a fork, I'd be very interested in getting that merged and released. Beyond that, the main thing that I could really use some help with is getting some of the current PRs merged to a branch that's ready for release.

@robpickerill
Copy link
Contributor

Beyond that, the main thing that I could really use some help with is getting some of the current PRs merged to a branch that's ready for release.

Let me see if I can get that done over the week, and prepare some PR's up. Leave with me and thanks again!

@robpickerill
Copy link
Contributor

Hey Jason, apologies I missed last week, got sidetracked with work and other items. Awesome, you've merged PR's - is there anything you need help with?

@jantman
Copy link
Owner Author

jantman commented Apr 21, 2021

Hey Jason, apologies I missed last week, got sidetracked with work and other items. Awesome, you've merged PR's - is there anything you need help with?

No worries! Um... there's still a handful of issues open, that I really haven't even looked at...

@jantman jantman pinned this issue Aug 4, 2021
@oksanalipkovska
Copy link

Hi guys, hope it's the correct place to ask, with new CloudFront checks how do I override limit for already increased entries? Awslimitchecker doesn't get the info that it was increased from AWS, for example CloudFront/Cache behaviors per distribution (limit 25) WARNING: E4J4RN2GZQXXX=22, current limit is 30, how do I override it just for this distributions and not for all of them so i can still get correct info about others?

@jantman
Copy link
Owner Author

jantman commented Aug 16, 2021

@oksanalipkovska No, this is not the right place to ask that. But awslimitchecker does not currently support overriding a limit on a per-resource basis. To do that, you'd need to write a wrapper script and suppress that yourself; please see https://awslimitchecker.readthedocs.io/en/latest/python_usage.html

@oksanalipkovska
Copy link

@oksanalipkovska No, this is not the right place to ask that. But awslimitchecker does not currently support overriding a limit on a per-resource basis. To do that, you'd need to write a wrapper script and suppress that yourself; please see https://awslimitchecker.readthedocs.io/en/latest/python_usage.html

Thank you @jantman , I'll check it out

@avazhnov-griddynamics
Copy link

As I see, @sean-zou is pretty active in https://github.com/mulesoft-labs/awslimitchecker.
But there is no "issues", only merge requests tab.

@vigneshwerv
Copy link

@jantman: Are you still looking for a maintainer? I've used this tool in the past (thank you for maintaining it thus far!) and plan to utilize it in my current job as well, although it's more oriented towards the serverless architecture.

@jantman
Copy link
Owner Author

jantman commented Apr 8, 2023

@vigneshwerv Yes, I am. If you're interested, reviewing/triaging some of the current PRs and Issues would be a wonderful first step!

@jantman jantman mentioned this issue Apr 17, 2023
14 tasks
@Pokom
Copy link

Pokom commented Jun 9, 2023

@jantman we use this tool internally at Grafana and would like to see if we can get someone involved as a maintainer. We're not quite sure who yet, @iainlane has issued #584 that could use some attention.

I'd be more then happy to take this conversation offline to talk through the different options and how much assistance you can provide 😄

@jantman
Copy link
Owner Author

jantman commented Jun 9, 2023

@Pokom I might be able to take a peek at that issue next week.

I'm happy to take the convo offline as well, but the bottom line is that (as evidenced from the lack of activity on this project) I'd really like to find someone to completely hand over maintenance, and possibly ownership, of this project to. This was a personal-time venture for me that was previously heavily utilized at my day job. We've split most of our stuff out to many smaller accounts so service limits are much less of a concern for us, and my personal-time interest in this is essentially zero at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants