Currently in helmer and kubeconfiggenerator, a Service's chart is untarred with a command like so:
Inside untarChart.untar cmd:tar -xvzf wordpress-chart-0.0.1.tgz
This creates the chart in a folder named "wordpress-chart".
The problem is, that if there is already a folder with that name, then the above operation will not overwrite that folder.
Instead, the contents of the earlier folder will remain in-tact and the newly untarred folder contents will be added to it.
This is problematic.
A better approach will be to untar each service's chart in a folder with that service name.
The change would look like this:
mkdir <service-name> && tar -xvzf wordpress-chart-0.0.1.tgz -C <service-name>
The subsequent steps in which we are using the chart-name in helm install will need to change to instead use the service-name used above in the helm install command.
Currently in helmer and kubeconfiggenerator, a Service's chart is untarred with a command like so:
Inside untarChart.untar cmd:tar -xvzf wordpress-chart-0.0.1.tgzThis creates the chart in a folder named "wordpress-chart".
The problem is, that if there is already a folder with that name, then the above operation will not overwrite that folder.
Instead, the contents of the earlier folder will remain in-tact and the newly untarred folder contents will be added to it.
This is problematic.
A better approach will be to untar each service's chart in a folder with that service name.
The change would look like this:
mkdir <service-name> && tar -xvzf wordpress-chart-0.0.1.tgz -C <service-name>The subsequent steps in which we are using the chart-name in helm install will need to change to instead use the service-name used above in the helm install command.