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

Publishing CAP warnings from filenames with multiple dots is handled incorrectly #789

Open
nimhbg opened this issue Oct 12, 2024 · 0 comments

Comments

@nimhbg
Copy link

nimhbg commented Oct 12, 2024

It is assumed here that the filename uploaded to the wis2box-incoming bucket contains a single dot. But that may not and does not have to be the case.

Example:

  1. Upload a CAP warning file named foo.bar1.xml to wis2box-incoming bucket.
  2. This will result in a file named foo.xml in the wis2box-public bucket when the workflow is executed by the wis2box-management container.
  3. Upload another different CAP warning file named foo.bar2.xml to wis2box-incoming.
  4. This will result in the same file foo.xml in wis2box-public and so the first CAP warning file will be overwritten and lost.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant