-
Notifications
You must be signed in to change notification settings - Fork 91
Extraction of custom files/tree from archive is not done during domain creation #1004
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
Comments
Working on this bug |
@CarolynRountree i tested the nw WDT (1.9.19). In the pod [oracle@sample-domain1-managed-server1 base_domain]$ pwd [oracle@sample-domain1-managed-server1 custom]$ pwd the 2 custom folder are not extracted to $DOMAIN_HOME |
@belfo We followed the structure of the archive file to extract under wlsdeploy/custom https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/. This is under $DOMAIN_HOME but I take it you need it directly under domain home. Can you clarify what and why please? |
@CarolynRountree That was my comprehension of extracting in the idea of "custom is extracted under $DOMAIN_HOME" So i misunderstood. Will look into it to see if it work by having a wlsdeploy/custom in in the path Thx for the reply |
Hi,
The 1.9.18 release touts this feature:
This is then intended to be implemented by PR #969
Unfortunately, it doesn't work. Looking at the PR, it adds a line of 'self.library_helper.extract_custom_files()' in topology_updater.py, which (I assume) will do extraction during an update. But during a create, this code is not called. Instead there is an addition of just an empty line in domain_creator.py; I'm assuming the intention was to insert the same extract_custom_files() call there and a test confirms this will indeed cause the files to extract during create.
Thanks,
ken1
The text was updated successfully, but these errors were encountered: