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

http_conn_validator: Initial commit #2

Merged
merged 1 commit into from
Oct 9, 2015

Conversation

Spredzy
Copy link
Contributor

@Spredzy Spredzy commented May 30, 2015

Initial commit of the new provider http_conn_validator that allows
one to check if a web service is actually listening on a given ip,
port and specific URL. The https protocol can be used if specified.
It supports both IPv4 and IPv6 address.

It either takes a string connection in the namevar or received the
informations through the server, port, use_ssl and test_url
parameters.

Case 1:

   http_conn_validator { 'https://127.0.0.1:8080/test_url' : }

Case 2:

   http_conn_validator { 'local elasticsearch' :
     server => '127.0.0.1',
     port   => 9200,
   }

@nibalizer
Copy link
Member

A lot of the comments on #1 apply here. I suggest we focus review there then apply those decisions here.

@igalic
Copy link
Contributor

igalic commented Aug 6, 2015

@Spredzy ping

@Spredzy
Copy link
Contributor Author

Spredzy commented Aug 24, 2015

@igalic I am/was waiting to get approval from #3 so I can make this change happen in a single commit.

@@ -1 +1,45 @@
# puppet-healthcheck

Copy link
Contributor

Choose a reason for hiding this comment

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

Right now this conflicts with the existing tcp_conn_validator code. It'll need to be reworked.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

Initial commit of the new provider http_conn_validator that allows
one to check if a web service is actually listening on a given ip,
port and specific URL. The https protocol can be used if specified.
It supports both IPv4 and IPv6 address.

It either takes a string connection in the namevar or received the
informations through the `server`, `port`, `use_ssl` and `test_url`
parameters.

Case 1:

   http_conn_validator { 'https://127.0.0.1:8080/test_url' : }

Case 2:

   http_conn_validator { 'local elasticsearch' :
     host   => '127.0.0.1',
     port   => 9200,
   }
@Spredzy
Copy link
Contributor Author

Spredzy commented Sep 24, 2015

@igalic @nibalizer Until I find a proper solution to address comment on #3 can we go ahead with this one (it matches #1) and will resubmit a review when a solution for reachable/check solution will be found

@igalic
Copy link
Contributor

igalic commented Sep 24, 2015

@Spredzy, from what i gather, @adrienthebo's ensurable comment should be equally valid for this check

@Spredzy
Copy link
Contributor Author

Spredzy commented Oct 6, 2015

@igalic Agree but I'd like to do that in a second patchset. This current commit offers the same feature as the one currently available on tcp_conn_validator. I need to work on a different patchset to bring @adrienthebo's suggestion on both providers.

nibalizer added a commit that referenced this pull request Oct 9, 2015
http_conn_validator: Initial commit
@nibalizer nibalizer merged commit 6b16252 into voxpupuli:master Oct 9, 2015
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

Successfully merging this pull request may close these issues.

4 participants