I'm finding some unexpected behaviour around specifying files to be copied into a charm via `charmcraft.yaml` and the execution directory when building/packing. # Working examples ## Specifying an exact file and executing `charmcraft` from the charm dir Doing: ``` BASE=/tmp/charmcraft-file-copy mkdir -p $BASE cd $BASE charmcraft init mkdir to_copy touch to_copy/foo cat << EOF > charmcraft.yaml type: charm parts: copy_files: plugin: dump source: ./ source-type: local prime: - ./to_copy/foo EOF charmcraft build -f . ``` produces `.charm` file that includes the `./to_copy/foo` as specified in the `charmcraft.yaml`. ## Specifying an exact file and executing `charmcraft` from some other dir This also works if you execute `charmcraft` from another directory, eg: ``` # (continue from previous example) cd /tmp charmcraft build -f $BASE ``` ## Specifying a file pattern and executing `charmcraft` from the charm dir Doing: ``` BASE=/tmp/charmcraft-file-copy mkdir -p $BASE cd $BASE charmcraft init mkdir to_copy touch to_copy/foo cat << EOF > charmcraft.yaml type: charm parts: copy_files: plugin: dump source: ./ source-type: local prime: - ./to_copy/* # <--NOTE: using pattern EOF charmcraft build -f . ``` also works as expected # Broken example ## Specifying a file pattern and executing `charmcraft` from some other dir If we execute the previous example (with pattern for files) from a different directory, eg: ``` # (continue from previous example) cd /tmp charmcraft build -f $BASE ``` we encounter no errors, but we also **do not** have the requested files in the `.charm` file. We see the same problem using `charmcraft pack -p ...`. My expectation would be that this pattern should work, but also if for some reason it cannot copy the files that it would break loudly rather than silently.