Open bflad opened 10 months ago
It would be really useful to completely override this, we got an existing folder/package structure with existing packages (k8s
and k8s_test
for instance). We would like to push the generated files with the right package name directly to the existing folder that already got packages defined.
Use Cases or Problem Statement
Super minor, but came up during the templating RFC review that a common naming convention for resource/data source files is
{THING}_(data_source|resource).go
which makes it easier to find correlated resources and data sources for the same real world resource. Currently the generator creates schema/data model packages asresource_{THING}
, etc.Proposal
While still in technical preview, consider flipping the naming convention for the generated packages.
Additional Information
No response
Code of Conduct