swirlsMD

Activity Graph

Page 1 of 1

2017-10-23

[03:00:07] swirlsMD: has joined #ruby
[05:33:05] swirlsMD: Ping timeout: 240 seconds
[14:52:35] swirlsMD: has joined #ruby
[15:06:57] swirlsMD: Ping timeout: 240 seconds
[15:08:01] swirlsMD: has joined #ruby
[15:21:28] swirlsMD: Ping timeout: 258 seconds
[15:22:37] swirlsMD: has joined #ruby
[15:53:05] swirlsMD: Ping timeout: 248 seconds

2017-10-22

[04:12:23] swirlsMD: has joined #ruby
[04:16:33] swirlsMD: Ping timeout: 248 seconds
[05:11:54] swirlsMD: has joined #ruby
[05:16:01] swirlsMD: Ping timeout: 240 seconds

2017-10-21

[15:25:10] swirlsMD: has joined #ruby
[17:15:36] swirlsMD: Ping timeout: 255 seconds
[22:11:44] swirlsMD: has joined #ruby
[22:16:32] swirlsMD: Ping timeout: 260 seconds

2017-10-20

[05:01:04] swirlsMD: Ping timeout: 258 seconds
[09:57:20] swirlsMD: has joined #ruby
[10:01:59] swirlsMD: Ping timeout: 252 seconds
[11:57:45] swirlsMD: has joined #ruby
[12:02:21] swirlsMD: Ping timeout: 258 seconds
[14:46:59] swirlsMD: has joined #ruby
[15:50:25] swirlsMD: Ping timeout: 248 seconds
[17:29:44] swirlsMD: has joined #ruby
[18:13:36] swirlsMD: Ping timeout: 246 seconds
[18:59:22] swirlsMD: has joined #ruby
[20:44:46] swirlsMD: Ping timeout: 264 seconds
[21:11:52] swirlsMD: has joined #ruby
[22:39:01] swirlsMD: Ping timeout: 240 seconds

2017-10-18

[00:30:27] swirlsMD: Ping timeout: 240 seconds
[02:33:00] swirlsMD: has joined #ruby
[02:37:21] swirlsMD: Ping timeout: 248 seconds
[02:55:14] swirlsMD: has joined #ruby
[02:56:58] swirlsMD: Read error: Connection reset by peer

2017-10-17

[19:23:41] swirlsMD: has joined #ruby
[19:24:12] swirlsMD: Howdy folks, wondering if anyone had some tricks / tips on how to supress output while running Rake?
[19:25:38] swirlsMD: havenwood: Not a bad thought, will that work for when Rake outputs its commands?
[19:25:56] swirlsMD: havenwood: trying to prevent some creds from getting posted
[19:26:59] swirlsMD: havenwood: Will do, thanks!
[19:31:28] swirlsMD: havenwood: How about when using 'sh' in the rakefile itself? Or should I just avoid using 'sh'
[19:33:17] swirlsMD: havenwood: cooool, much thanks
[19:34:25] swirlsMD: havenwood: Agree, found a stack post about using sh for shelling out in a rake. We're doing weird stuff
[19:34:41] swirlsMD: matthewd: Totally agree, trying to keep them out
[19:35:34] swirlsMD: I guess the question should be, what is best practice for shelling out when using rake?
[19:36:23] swirlsMD: Certainly, its kind of muddy, so don't judge too harshly.
[19:36:40] swirlsMD: Working with another team on a build pipeline. They've standardized on using make or rake files to run tasks
[19:36:42] swirlsMD: We opted for rake
[19:36:53] swirlsMD: Some of the tasks we need to run are around docker or terraform
[19:37:01] swirlsMD: Of which, a few of those needs creds
[19:37:26] swirlsMD: Trying to come up with a way to essentially have rake run a terraform plan/apply (which needs AWS creds)
[19:37:36] swirlsMD: Hence the "trying supress output question"
[19:37:45] swirlsMD: Quit: WeeChat 1.9
[19:38:05] swirlsMD: has joined #ruby
[19:38:20] swirlsMD: and back, thanks computer.
[19:38:34] swirlsMD: Potentially, its a bit of a debate on that front
[19:39:04] swirlsMD: Ultimately we will use Vault to handle the creds, but currently thats not ready, we are trying to work around it
[19:41:53] swirlsMD: matthewd: good points, since were iterating, first part is keeping out of output (since that gets logged somewhere...) Ideally we will have a better solution for this
[19:42:02] swirlsMD: Appreciate the responses, very helpful
[20:16:29] swirlsMD: Ping timeout: 255 seconds
[20:18:53] swirlsMD: has joined #ruby
[20:45:13] swirlsMD: Ping timeout: 252 seconds
[21:39:09] swirlsMD: has joined #ruby
[22:21:27] swirlsMD: Ping timeout: 240 seconds
[22:38:43] swirlsMD: has joined #ruby