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

Allow setting metadata-dir separately from output-dir #16

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

Allow setting metadata-dir separately from output-dir #16

ncoghlan opened this issue Sep 30, 2024 · 0 comments
Labels
Affects: Command Line Affects the command line interface Affects: Python API Affects the public Python API of the project Category: Enhancement New feature or request

Comments

@ncoghlan
Copy link
Collaborator

ncoghlan commented Sep 30, 2024

The current CLI help provides no indication that the metadata for built archives and locally exported environments will be published to <output path>/__venvstacks__/ by default.

Adding a --metadata-dir option will both provide a place to document the default location, and allow the metadata to be placed somewhere else if desired (e.g outside the artifact folder, in a location that makes caching or publishing the manifests separately from the built archives straightforward).

@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: Command Line Affects the command line interface labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Command Line Affects the command line interface Affects: Python API Affects the public Python API of the project Category: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant