Exporting releases with multiple jobs fails due to file name exceeding max length
amhuber opened this issue · 3 comments
#556 modified the file name for exported releases to include the job names, but since multiple jobs can be specified on a single export the filename can easily get too long for the filesystem which is breaking our automation:
Downloading exported release:
Moving to final destination:
rename /root/.bosh/tmp/director-resource-fb66b55b-4a6b-4131-9f44-7dad3083c414171120867 /etc/bosh-workspace/releases/alertmanager-blackbox_exporter-bosh_alerts-bosh_dashboards-bosh_exporter-cf_exporter-cloudfoundry_alerts-cloudfoundry_dashboards-firehose_exporter-grafana-grafana_dashboards-nginx-postgres_alerts-postgres_dashboards-postgres_exporter-probe_alerts-probe_dashboards-prometheus2-prometheus_alerts-prometheus_dashboards-system_dashboards-prometheus-26.2.0-ubuntu-xenial-621.82-20200828-001454-555838311.tgz: file name too long
Can we put the new functionality behind a command line option, or only use the new naming convention when a single job is specified?
Tagging @rkoster as the PR submitter.
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/174546790
The labels on this github issue will be updated when the story is started.
This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.
This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.