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

Keep directories and files generated for V4M deployment #591

Open
1 task done
miaeyg opened this issue Jan 28, 2025 · 0 comments
Open
1 task done

Keep directories and files generated for V4M deployment #591

miaeyg opened this issue Jan 28, 2025 · 0 comments
Labels
enhancement New feature or request new Added to an issue when it's new ;)

Comments

@miaeyg
Copy link

miaeyg commented Jan 28, 2025

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
@miaeyg miaeyg added enhancement New feature or request new Added to an issue when it's new ;) labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new Added to an issue when it's new ;)
Projects
None yet
Development

No branches or pull requests

1 participant