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

When delete-data command is used, log file specified is empty #72

Open
plawton-umd opened this issue Jan 24, 2024 · 0 comments
Open

When delete-data command is used, log file specified is empty #72

plawton-umd opened this issue Jan 24, 2024 · 0 comments

Comments

@plawton-umd
Copy link

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

When I ran registry-manager with the delete-data command and a log file specified after the -l, the log file was empty. There was output - it was included in the email from the cron job.

🕵️ Expected behavior

I expected the information received in the cron tab's email to be in the specified log file (like harvest's log file).

📜 To Reproduce

  1. registry-manager delete-data -packageId 91dd1d72-c568-4031-9b90-697af955e4a8 -es $OPENSEARCH_URL -index registry -auth $AUTH_FILE -l package_delete.log

...

🖥 Environment Info

  • Version of this software 4.6.2
  • Operating System: Linux
    ...

📚 Version of Software Used

No response

🩺 Test Data / Additional context

No response

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants