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

Wrong configuration default for aws_message_type #747

Open
edmundoa opened this issue Feb 22, 2021 · 0 comments
Open

Wrong configuration default for aws_message_type #747

edmundoa opened this issue Feb 22, 2021 · 0 comments

Comments

@edmundoa
Copy link
Contributor

Description

While looking into adapting the AWS custom input UI to work on the Forwarder, I found that the default value set in the configuration API for aws_message_type is using one of the AWS regions instead of one of the values set in AWSMessageType. This is where the configuration option is set:

request.addField(new DropdownField(
CK_AWS_MESSAGE_TYPE,
"AWS Message Type",
Region.US_EAST_1.id(),
AWSMessageType.getMessageTypes().stream()
.collect(Collectors.toMap(AWSMessageType::toString, AWSMessageType::getLabel)),
"The type of AWS message that this input will receive.",
ConfigurationField.Optional.NOT_OPTIONAL));

I don't think users creating inputs through the custom UI are impacted by this, though, since the UI sets it's own default for that configuration option, so this will only affect those creating inputs through the API.

Environment

  • Graylog Version: Graylog-4.1.0-SNAPSHOT (Integrations 4a765d1)
@edmundoa edmundoa added the bug label Feb 22, 2021
@edmundoa edmundoa changed the title Wrong configuration default for aws_message_type Wrong configuration default for aws_message_type Feb 22, 2021
@bernd bernd added the triaged label Feb 22, 2021
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

2 participants