15:07:26 #startmeeting ansible core irc meeting 15:07:26 Meeting started Thu May 31 15:07:26 2018 UTC. 15:07:26 This meeting is logged and archived in a public location. 15:07:26 The chair is bcoca. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:07:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:07:26 The meeting name has been set to 'ansible_core_irc_meeting' 15:07:30 #topic open floor 15:07:55 Hello 15:08:20 #chair sac shertel 15:08:20 Current chairs: bcoca sac shertel 15:08:26 * bcoca waves 15:11:32 when will 2.7 dates be released? 15:11:44 .hello2 15:11:45 maxamillion: maxamillion 'Adam Miller' 15:12:04 we'll release the release dates once we know the release dates, i cannot give you a release date on releaseing the release dates though 15:12:45 Greetings. 15:13:15 chicken -> egg 15:16:10 ok, if nothing else, closing meeting in 1 min 15:18:24 I have something to discuss sorry late to the meeting 15:19:00 PR#39774 15:19:24 Adding digital_ocean_space alias for s3_bucket module 15:20:12 I think this might jumble the docs and be confusing 15:21:35 I'd rather handle this with s3_url in the same way for ceph and fakes3 15:21:54 * shertel finds PR related to this topic that I was recently looking at 15:23:14 abond Can you test if this is compatible with digital ocean spaces? https://github.com/ansible/ansible/pull/36832 15:24:46 (in theory that should be compatible with walrus still too - but it's not clear if the walrus API is a good drop-in for s3, so I wish that could be tested first to see if it even works on devel currently) 15:26:35 shertel Thank you, I will test that out. 15:29:09 Thanks, abond. This should fix custom endpoints in general rather than adding more special cases. I'm not sure if there are DO docs that would make the AWS module easier to find for those users, but that would be good. 15:30:07 also, #ansible-aws channel might be better for this discussion, you would not have had to wait for this meeting 15:30:49 #endmeeting