Bug/SK-793 | Fix package extract and dispatch folder #597
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ahellander
approved these changes
May 6, 2024
|
fedn will then not create the folder since it already exist, the tarball will be extracted into the folder, any conflicts will be overwritten, any files that already existed will still be there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
on package extract (untar) tarball will now extract to default folder "package" from client CWD. The directory can be chnaged using FEDN_PACKAGE_EXTRACT_DIR environment var.
When a package is extracted FEDn searches for "fedn.yaml" in the root and child folders in the extracted folder. The path of fedn.yaml is saved and will be the "run path" for the dispatcher. In other words relative path in entry_points will be realative "run path"