Issue with using branch_name / commit_oid in data_models API endpoint

Report Bugs
1

Hello!

We’re working on setting up a CI/CD script to automatically validate SQL fields in Holistics. In order to do that, we’re relying on the data_models API endpoint. We’re almost there but are running into an issue. When we don’t specify the branch_name or commit_oid, then the API call works fine. But when we specify the branch_name or commit_oid, then we get the a 500 response with an error that says “InternalHolisticsError”. Would really appreciate some help on this! I’m giving an example of the debug info below for one call each with branch_name and commit_oid:

Example of the response and debug info when we specify branch_name

{
    "type": "InternalHolisticsError",
    "message": "Something went wrong on our server. Debug info 20241002150915_wpo83"
}

Example of the response and debug info when we specify commit_oid

{
    "type": "InternalHolisticsError",
    "message": "Something went wrong on our server. Debug info 20241002151058_4x0kxb"
}

Thanks in advance,
Anya

1 Like
2

Hi @anya.conti

Thank you for reporting this to us and apologize for any inconvenience this may have caused. We are investigating the issue and will get back to you soon.

Best Regards,

1 Like
3

Hi @anya.conti,

I think the branch although exists in Github, but it’s not available in Holistics.

May I confirm that you created the branch outside Holistics and that you haven’t logged into Holistics and switched to that branch?

If that is the case, then let us see how to directly fetch that branch from Github to support this case.

Best,
Huy Vu

4

Hi Huy,

I just opened holistics and switched to the branch and ensured the commit is showing up there and am still running into the same issue.

I also made sure I don’t have any uncommitted changes in holistics before calling the API, so it means it’s not an issue where my user can’t switch branches because I have uncommitted changes.

I also tested on a branch that’s identical to production, so I don’t think it’s an AML compilation error or anything.

All the best,
Anya

5

Hi @Khanh_Tran and @HuyVu, just wanted to check in on updates for this. Any help I can provide if you’re having trouble tracking the issue down? We would LOVE to get the automated validation fully hooked up, and I believe that this is our last step. Thanks a bunch in advance!

6

Hi @anya.conti,

We realize that the data_models endpoint doesn’t work well with the Git workflow, so we’re currently working on an update to improve its integration. We fully understand how important it is for you to set up your validation flow. I’ll keep you posted on our progress. :smiley:

Best Regards,

2 Likes
7

Hi @anya.conti,

We’ve released a patch to update the data_models API endpoint. Please check it on your side to ensure everything works. If you’re using the branch_name, please prefix it with origin/, like origin/master or origin/develop.

Thanks for your patience during the API update! Let me know if it works.

Best Regards,

8

Amazing, confirmed that this appears to work now, thank you so much!

1 Like