-
Notifications
You must be signed in to change notification settings - Fork 80
Remove unused go-generate files #266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, to generate updated models and operations, I suggest you use our We don't use We should remove the |
@mjuraga Hi! Actually I did use When I ran type configTypeServiceDiscovery struct {
Consuls *[]*models.Consul `yaml:"consuls,omitempty" hcl:"consuls,omitempty"`
AWSRegions *[]*models.AwsRegion `yaml:"aws_regions,omitempty" hcl:"aws_regions,omitempty"`
} However, when I ran type configTypeServiceDiscovery struct {
Consuls *[]*models.Consul `yaml:"consuls,omitempty" hcl:"consuls,omitempty"`
Nomads *[]*models.Nomad `yaml:"nomads,omitempty" hcl:"nomads,omitempty"`
AWSRegions *[]*models.AwsRegion `yaml:"aws_regions,omitempty" hcl:"aws_regions,omitempty"`
} So, do you suggest I edit the Thanks! |
Yes, you should change the file manually, we won't be running go generate again. It had some issues with these kind of fields, and we decided it was easier to just add stuff manually then to rewrite the |
That would be awsome @mr-karan. Thanks! |
I ran
go run generate/go-generate.go $(pwd)
to generate updated models and configuration files. It generated a fileconfiguration_generated.go
(as it seems to be hardcoded here: https://github.com/haproxytech/dataplaneapi/blob/master/generate/go-generate.go#L356)I manually renamed
configuration_generated.go
=>configuration_storage.go
and ranmake build
. I found the app doesn't compile anymore:The old file had this struct:
The new generated file has this struct but the fields are different:
It's also missing the LogTargets from
StorageDataplaneAPIConfiguration
struct.Please let me know if this is a bug or I am doing something wrong!
Thanks
The text was updated successfully, but these errors were encountered: