Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add Application Signals Service Level Objective Table #2291
Add Application Signals Service Level Objective Table #2291
Changes from 3 commits
c30e534
10c3f80
a5a8c32
06b8364
01153d9
71fa7a0
42cb587
95d856a
8bcc5ca
8b20b90
1dc7bcd
4241701
5f4baac
1061f1e
2aa9a5c
1d1a7b9
b9ef639
f685380
508d4b9
b629224
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Query, how do I identify regions supported by this application_signals service?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @johnlayton,
Thank you for your contribution! 🎉
In this plugin, we are currently using AWS Go SDK v1, specifically version
v1.51.19
. Unfortunately, in this version, the AWS Application Signals service is not yet available. After reviewing the AWS Go SDK v1 repository, I found that support for this service was added in version v1.53.20.To use the
EndpointID
of the Application Signals service, we would need to update the AWS Go SDK v1 tov1.53.20
. This would enable us to leverage the EndpointID reference.Alternatively, if we prefer not to update the AWS SDK v1, we could potentially use a hardcoded value (
application-signals
) to retrieve the supported regions for the Application Signals service. However, I’m not entirely certain if using a hardcoded value would fully resolve the issue in listing supported regions for the service.Please let us know what works best for you.
Thanks again!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great feedback. Just to confirm (I am new to Go) the
go.mod
andgo.sum
changes need to be reverted except for addinggithub.com/aws/aws-sdk-go-v2/service/applicationsignals v1.3.1
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @johnlayton,
I noticed that the current package version we are using in the AWS plugin (v1.27.0) already supports the applicationsignals service. Therefore, there’s no need to update AWS SDK V2 to support this table.
However, for the service endpoint reference, we may need to update AWS SDK V1 to version
v1.53.20
.To resolve this, you can follow the steps outlined below:
go get github.com/aws/[email protected]
.v1.53.20
to obtain the endpoint ID reference by running the command:go get github.com/aws/[email protected]
.aws_application_signals_service_level_objective
table, depending on the API behavior, if required.Please let me know if you need any further clarification.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi. I updated the dependencies as suggested. I still see changes to
configsources
andendpoints
, and the linting fails. Is this expected or am I still missing something?Is it related to this comment -> #2291 (review)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @johnlayton, thank you so much for your efforts and contribution! I’ve merged the PR into a branch.
The lint failure was caused by the use of the deprecated function EndpointResolverWithOptionsFunc with AWS SDK V2 version 1.30.5.
I'll look into resolving it.