Do you have an example of your hipchat playbook?
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this
I got it worked out, although notify for v2 will not work. I described the
issue in the pull request
here: https://github.com/ansible/ansible-modules-extras/pull/118
This could use some testing from someone who has access to a v1 account
since I could not test it there anymore.
--
You receive
If you start a hipchat account today, you are put on v2 by default. All the
v1 documents are also marked deprecated.
So, I made an attempt to support v1 and v2
here:
https://github.com/mikemilano/ansible-modules-extras/blob/devel/notification/hipchat.py
I added a new module parameter: version
No one does, because it's written for the v1 API yet.
On Wed, May 28, 2014 at 9:52 AM, Lars Sommer
wrote:
> I will work on it more today but you could receive a 401 if you were using
> a notification API token that is assigned to a particular room and you were
> trying to use it to authentica
I will work on it more today but you could receive a 401 if you were using
a notification API token that is assigned to a particular room and you were
trying to use it to authenticate anywhere else that was a valid URL. My
main concern was how the URL string got assembled by the module parameters.
According to this: https://www.hipchat.com/docs/api, the v2 API is still in
beta, so there should not be any issues with the module as it stands. A 401
indicates an authorization issue, not a target URL problem, so I would
double check your API token and username.
On Tue, May 27, 2014 at 3:55 PM,
http://docs.ansible.com/hipchat_module.html
https://www.hipchat.com/docs/apiv2/method/send_room_notification
Difference in expected URL:
https://api.hipchat.com/v1/rooms/message
vs
https://api.hipchat.com/v2/room/{id_or_name}/notification
I was receiving a 401 until I started messing with the api
