Mika Marttila

@iloveitaly rebased this branch as well to resolve conflicts

Feature flag is probably a good idea as this might cause unexpected exceptions for people using this gem. I'm happy to implement the flag! One option is to have simple...

@freezepl Agreed. As long as we're only handling one response error it should not be any more complicated to turn the feature on. I did the gate now. I think...

How about this: With `raise_on_response_errors` being **false** by default it would not be a breaking change and could already be merged to master. Then at 1.0 you could change the...

I agree with @iloveitaly that these sort of hard NetSuite failures should raise instead fail silently. It would've been especially helpful when we we're setting up the access management for...

@freezepl @iloveitaly Rebased with master to resolve conflicts.

I'm no longer maintaining the fork. Best people to have a chat about changes to this PR are @beyondcompute and @edimossilva

I got it working by moving arguments after options and using an argument that doesn't have dashes. This works as expected: ``` kubernetes-run my-kube-namespace my-kube-context --template=task-runner-template --max-watch-seconds=86400 --entrypoint=bin/rake db:migrate:status ```...