Will-Lo opened a new pull request #3196: URL: https://github.com/apache/incubator-gobblin/pull/3196
Fixes bug where standalone could not pick up jobs due to env variable not being set Dear Gobblin maintainers, Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! ### JIRA - [x] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR" - https://issues.apache.org/jira/browse/GOBBLIN-1357 ### Description - [x] Here are some details about my PR, including screenshots (if applicable): - Uses new images from apache/gobblin dockerhub. Currently there are no images in the repository so must be generated from locally and pushed to minikube cache until dockerhub is populated with an image - Fixes bug where arguments with spaces was not properly passed in to docker through entrypoint script - Fixes minor bugs with k8s cluster including mysql version bump to support json syntax, bug with standalone not picking up jobs due to environment variable not being set ### Tests - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### Commits - [x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 2. Subject is limited to 50 characters 3. Subject does not end with a period 4. Subject uses the imperative mood ("add", not "adding") 5. Body wraps at 72 characters 6. Body explains "what" and "why", not "how" ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
