-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
docs(aws_sqs source): remove credentials_file from docs #11272
Conversation
Signed-off-by: Stephen Wakely <fungus.humungus@gmail.com>
✔️ Deploy Preview for vector-project ready! 🔨 Explore the source changes: a7c8144 🔍 Inspect the deploy log: https://app.netlify.com/sites/vector-project/deploys/62067b3808c0650007a41064 😎 Browse the preview: https://deploy-preview-11272--vector-project.netlify.app |
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.
Thanks! I left one comment below about reducing some of the duplication.
Do we need to update the code too, to disallow this option?
Nit: I think you could just have both of these _
components defined in the same aws.cue
rather than a new file.
package metadata | ||
|
||
components: _aws_new_sdk: { | ||
configuration: { |
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.
It seems like only the auth
configuration differs from components: _aws_sdk
. Could we maybe inherit the other config and just define auth
here?
Like:
components: _aws_new_sdk: {
configuration: {
auth: ...
endpoint: components._aws_sdk.configuration.endpoint,
}
etc.
Maybe we could just error on startup if the option is used rather than worry about splitting up all AWS authentication configuration structs. |
Signed-off-by: Stephen Wakely <fungus.humungus@gmail.com>
Signed-off-by: Stephen Wakely <fungus.humungus@gmail.com>
Have done this.
|
Signed-off-by: Stephen Wakely <fungus.humungus@gmail.com>
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.
Awesome, thanks!
Signed-off-by: Stephen Wakely <fungus.humungus@gmail.com>
Soak Test ResultsBaseline: 6d8a6a7 ExplanationA soak test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine, quickly, if vector performance is changed and to what degree by a pull request. Where appropriate units are scaled per-core. The table below, if present, lists those experiments that have experienced a statistically significant change in their throughput performance between baseline and comparision SHAs, with 90.0% confidence OR have been detected as newly erratic. Negative values mean that baseline is faster, positive comparison. Results that do not exhibit more than a ±8.87% change in mean throughput are discarded. An experiment is erratic if its coefficient of variation is greater than 0.3. The abbreviated table will be omitted if no interesting changes are observed. No interesting changes with confidence ≥ 90.00%: Fine details of change detection per experiment.
Fine details of each soak run.
|
Closes #11082
This removes the
credentials_file
setting from the docs for the aws_sqs source.Since all the aws sources share a cue file for the aws settings, I have creating a new one (aws_new_sdk.cue) with the
credentials_file
setting removed that this one uses instead.Signed-off-by: Stephen Wakely fungus.humungus@gmail.com