[feature] Remove the pkg directory in Go builder

[laurentsimon]

The pkg directory serves no purpose, let's flatten the directory structure like the generic builder does.

[naveensrinivasan]

The pkg directory serves no purpose, let's flatten the directory structure like the generic builder does.

Can you please explain as to why ?

It usually provides functionality that can be reused and helps with separation of concerns and cleaner code.

[laurentsimon]

we don't expose API to anyone, it's all internal. Right now the pkg folder has all the code, so it serves no real purpose. The builder is very simple, so file separation is enough. We could have folder for each file / logic instead, but its overkill and complicates more than it helps.

[naveensrinivasan]

OK.Why aren't we planning to expose the API? Is there a specific reason?

[laurentsimon]

It's our native builder and provides only the features we need. Also, it adds burden on versioning for us, and there does not seem to be a case for public APIs at this point.

But this can always be re-visited later. Right now it's not a priority for us.

[naveensrinivasan]

But this can always be re-visited later. Right now it's not a priority for us.

Agreed. Thanks for the explanation!