Setup local dev for insights-ingress-go.

[myersCody]

Blocked by: RedHatInsights/insights-ingress-go#112

[codecov-io]

Codecov Report

Merging #276 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #276   +/-   ##
=======================================
  Coverage   92.64%   92.64%           
=======================================
  Files          19       19           
  Lines        1264     1264           
  Branches      140      140           
=======================================
  Hits         1171     1171           
  Misses         70       70           
  Partials       23       23

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9e988e9...8e21dff. Read the comment docs.

[abaiken]

I ran into the following issue:

ERROR: Service 'ingress' failed to build: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/bin/sh\": stat /bin/sh: no such file or directory"

but resolved it by following the instructions here.

[abaiken]

Everything worked 🎉and looks good. The only question that I have is if we shoul still refer to ingress as the file upload service everywhere. Do we want to update documentation to say ingress service (since the file-upload service was a thing of the past) or are we okay since it is technically the thing you upload files to? Thoughts @kholdaway @myersCody?

[myersCody]

I ran into the following issue:

ERROR: Service 'ingress' failed to build: oci runtime error: container_linux.go:265: starting container process caused "exec: \"/bin/sh\": stat /bin/sh: no such file or directory"

but resolved it by following the instructions here.

Great work debugging this issue @abaiken

[myersCody]

Everything worked 🎉and looks good. The only question that I have is if we shoul still refer to ingress as the file upload service everywhere. Do we want to update documentation to say ingress service (since the file-upload service was a thing of the past) or are we okay since it is technically the thing you upload files to? Thoughts @kholdaway @myersCody?

I am okay with changing it if we think it is necessary. I think whatever is the least confusing for people on-boarding to the project is the direction we should go with. However, considering that I am relatively new to the project, I may not be the best source to decide which direction we should go in.

🤷‍♂

[abaiken]

This doesn't make sense. it should be upload to the ingress service

[abaiken]

Awesome work 🎉