WEEK 7: ENTRY 3

 At my internship today, I was tasked to write a GET Request Golang code to the Elasticsearch API. Having written a GET request previously for the BigQuery API, I thought it would be an easy and fast task to complete. However, it was the total opposite. With the Elasticsearch Rest API, I had to use a Golang package that could use my SSO Auth token to be able to have the permission to call the API, and to my surprise it is turning out to be more difficult than I previously envisioned. Because of security reasons, not all system users are granted permission to make an API call. I did not realize this until I made an API GET Request. From the look at my code, everything seems  correct, but when I pushed my code and took a look at my logs on the console, there was a 403 error code, which simply means unauthorize. 


Even after the admin authorized my system user to make API calls, my code was not working still. I had to use a different approach. I tried testing my http client with a Big Query API call and that worked, so it narrowed down my issue because clearly the http client is correct. For a moment, I thought perhaps, my Go package version was not compatible with the Elasticsearch API version. But again, when I searched about that, it did indicate that the version’s package does not matter. So then what is going wrong? I am still asking myself that question and hoping that I’ll find the answer soon. 


Basically, I intend to look into the issue this weekend during my spare time so that I can have a fresh thinking and approach. I’ll also do more reading with the other Golang package alternatives. So too, my manager gave me some informal feedback on how I always seem to be stuck at one approach, so it’ll be something I’ll be working on next week. I’ll basically try to change my approach on how I tackle issues by adopting a step-by-step approach while considering the pros and cons of my approach. 

Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more