Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve content management for launch packages #15

Open
ncoghlan opened this issue Sep 26, 2024 · 0 comments
Open

Improve content management for launch packages #15

ncoghlan opened this issue Sep 26, 2024 · 0 comments
Labels
Affects: Python API Affects the public Python API of the project Affects: Spec Format Affect the stack specification format Category: Enhancement New feature or request

Comments

@ncoghlan
Copy link
Collaborator

Launch packages currently ship everything inside the specified folder. This means things like README.md files that shouldn't be deployed have to be kept outside the package folder they relate to.

It would be useful to support at least the choice between path/to/launch_package/** and path/to/launch_package/*.py when deciding which launch package files to copy to the build folder for deployment (any changes to the filter that affected the included files would show up in the input metadata as a change to the directory hash)

@ncoghlan ncoghlan added the Category: Enhancement New feature or request label Oct 1, 2024
@ncoghlan ncoghlan transferred this issue from another repository Oct 18, 2024
@ncoghlan ncoghlan added Affects: Python API Affects the public Python API of the project Affects: Spec Format Affect the stack specification format labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Python API Affects the public Python API of the project Affects: Spec Format Affect the stack specification format Category: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant