Adding a library to a volume goes to internal directory

[fernanluyano]

When uploading a JAR to a Volume, it's put in an ".internal" directory instead of the volume path I provided.
E.g., where the libraries_volume variable is of the form /Volumes/...

workspace:
  root_path: /Users/${workspace.current_user.userName}/.bundle/${bundle.name}
  artifact_path: ${var.libraries_volume}

artifacts:
  jobs_jar:
    files:
      - source: "workflows-fat-jar-*.jar"
    type: jar

[andrewnester]

Artifacts are indeed always put in .internal folder in artifact path created by DABs. The reason is that we want to be able safely clean everything that DABs created if needed, in this case we can safely remove .internal folder.

What's your concern with having .internal folder?

[fernanluyano]

There is no direct concern. But it’s a bit obscure since I’d expect it to go to the location I told it to, in a volume. It makes clients be aware of it when pointing to a library location inside the volume, in a job