You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently when using this project to deploy the V4M (monitoring and logging) it seems that all the directories and files created for the deployment are created in a temporary path under /tmp and once the execution completes whether successful or not this temporary path is deleted.
Describe the solution you'd like
I think it would be useful to create and keep the generated files for review and documentation and not to delete them.
I recommend to store the V4M deployment directory in the same location as the deployment files of SAS Viya (in /config mount point of the docker container)
Describe alternatives you've considered
I thought to change the playbook.yaml file so to remove the Ansible action that deletes the temporary path it created tmpdir
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently when using this project to deploy the V4M (monitoring and logging) it seems that all the directories and files created for the deployment are created in a temporary path under
/tmp
and once the execution completes whether successful or not this temporary path is deleted.Describe the solution you'd like
I think it would be useful to create and keep the generated files for review and documentation and not to delete them.
I recommend to store the V4M deployment directory in the same location as the deployment files of SAS Viya (in
/config
mount point of the docker container)Describe alternatives you've considered
I thought to change the
playbook.yaml
file so to remove the Ansible action that deletes the temporary path it createdtmpdir
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: