We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello! Thanks for
Current directory contain templates and emptry templates:
tree . ├── Chart.yaml ├── README.md ├── output ├── templates │ ├── api-gateway-deployment.yaml │ ├── api-gateway-service.yaml │ ├── config-server-deployment.yaml │ ├── config-server-service.yaml │ ├── customers-service-deployment.yaml │ ├── customers-service-service.yaml │ ├── discovery-server-deployment.yaml │ ├── discovery-server-service.yaml │ ├── distr-persistentvolumeclaim.yaml │ ├── tracing-server-deployment.yaml │ ├── tracing-server-service.yaml │ ├── vets-service-deployment.yaml │ ├── vets-service-service.yaml │ ├── visits-service-deployment.yaml │ └── visits-service-service.yaml └── templates1 3 directories, 17 files
Run helmtrans
helmtrans yamltohelm -p templates -o templates1 ERROR: assignment to entry in nil map
The text was updated successfully, but these errors were encountered:
Same problem when I try to read a group of yamls into a folder (darwin/mac release)
ERROR: assignment to entry in nil map
Sorry, something went wrong.
Could it be this fucntion where print that ERROR message?
helmtrans/src/util.go
Line 429 in 0e874e6
Here reference to "ERROR:" message... it shoud build the "ERROR: assignment to entry in nil map" , right?
The commad seems call to this concatenate functions but I don't find the final functions to do the yaml conversion from helm :
Because ScanRestFile (latest func to call in Yamltohelm) is not referenced any more to continue conversion:
No branches or pull requests
Hello! Thanks for
Current directory contain templates and emptry templates:
Run helmtrans
The text was updated successfully, but these errors were encountered: