[Feature Req] charm-build exclude/ignore

[rgildein]

Checklist

• Confirmed this is an issue with charm-tools, not charmstore-client
• Provide versions of tools used
• Described the feature or ways to replicate the issue

What version am I running?

I ran the following command: snap info charm and got the following ouput:

summary:   charm and charm-tools
publisher: Canonical✓
store-url: https://snapcraft.io/charm
contact:   https://discourse.juju.is/c/charming
license:   unset
description: |
  charmstore-client and charm-tools
commands:
  - charm
snap-id:      2Rryoc2ylScfbFl4eQtpntHD9iuZuMvt
tracking:     latest/stable
refresh-date: 21 days ago, at 02:20 CET
channels:
  latest/stable:    2.8.2               2021-02-01 (609) 119MB classic
  latest/candidate: 2.8.2               2021-02-01 (609) 119MB classic
  latest/beta:      2.8.2               2021-02-01 (609) 119MB classic
  latest/edge:      2.8.2+git-1-62b5015 2021-02-04 (614) 119MB classic
installed:          2.8.2                          (609) 119MB classic

I am using: Ubuntu 20.10

Issue/Feature

I believe it will be really useful to have an argument to exclude a file or directory when running charm-build. When working on reactive charms, I often rebuild my development version for testing purpose. These versions include my venv directory and the PyCharm helper directory (.idea). For this reason, the build takes longer as well as deployment of the charm. To avoid extending the deployment, I manually remove these directories from the charm-build directory.

I expect/expected the following

A command like this should not copy the venv and .idea directories to the builded charm

charm-build --log-level DEBUG -o ~/canonical/charm-build/ --exclude venv --exclude .idea .

[jameinel]

I believe we support '.jujuignore' which has the same syntax as .gitignore for defining what parts of the charm should not end up in the final .zip file.

…

On Tue, Feb 23, 2021 at 12:01 PM Robert Gildein ***@***.***> wrote: Checklist - Confirmed this is an issue with charm-tools, not charmstore-client - Provide versions of tools used - Described the feature or ways to replicate the issue What version am I running? I ran the following command: snap info charm and got the following ouput: summary: charm and charm-tools publisher: Canonical✓ store-url: https://snapcraft.io/charm contact: https://discourse.juju.is/c/charming license: unset description: | charmstore-client and charm-tools commands: - charm snap-id: 2Rryoc2ylScfbFl4eQtpntHD9iuZuMvt tracking: latest/stable refresh-date: 21 days ago, at 02:20 CET channels: latest/stable: 2.8.2 2021-02-01 (609) 119MB classic latest/candidate: 2.8.2 2021-02-01 (609) 119MB classic latest/beta: 2.8.2 2021-02-01 (609) 119MB classic latest/edge: 2.8.2+git-1-62b5015 2021-02-04 (614) 119MB classic installed: 2.8.2 (609) 119MB classic I am using: Ubuntu 20.10 Issue/Feature I believe it will be really useful to have an argument to exclude a file or directory when running charm-build. When working on reactive charms, I often rebuild my development version for testing purpose. These versions include my venv directory and the PyCharm helper directory (.idea). For this reason, the build takes longer as well as deployment of the charm. To avoid extending the deployment, I manually remove these directories from the charm-build directory. I expect/expected the following A command like this should not copy the venv and .idea directories to the builded charm charm-build --log-level DEBUG -o ~/canonical/charm-build/ --exclude venv --exclude .idea . — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#602>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABRQ7O4JKUCQOGHOVREOXTTAPNNZANCNFSM4YC3CHQQ> .

[rgildein]

This is really helpful and I will use it, thanks.
However, this does help to deploy the charm, but the charm-build
still copies those directories.