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

[Taxii2] Handling Int in Config #3525

Closed
helene-nguyen opened this issue Feb 28, 2025 · 0 comments · Fixed by #3448
Closed

[Taxii2] Handling Int in Config #3525

helene-nguyen opened this issue Feb 28, 2025 · 0 comments · Fixed by #3448
Assignees
Labels
bug use for describing something not working as expected community support use to identify an issue related to feature developed & maintained by community. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@helene-nguyen
Copy link
Member

Description

In some customer environments these could be stored as strings, which will cause an error. Need to handle Int in Config

@helene-nguyen helene-nguyen added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team community support use to identify an issue related to feature developed & maintained by community. and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 28, 2025
@helene-nguyen helene-nguyen added this to the Release 6.5.4 milestone Feb 28, 2025
@helene-nguyen helene-nguyen linked a pull request Feb 28, 2025 that will close this issue
4 tasks
@helene-nguyen helene-nguyen self-assigned this Feb 28, 2025
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected community support use to identify an issue related to feature developed & maintained by community. solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant