build(deps): bump github.com/aws/aws-sdk-go from 1.36.31 to 1.36.33 in /processor/resourcedetectionprocessor #2210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.36.31 to 1.36.33. - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Changelog](https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-go@v1.36.31...v1.36.33) Signed-off-by: dependabot[bot] <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #2210 +/- ##
==========================================
- Coverage 90.49% 90.46% -0.04%
==========================================
Files 397 397
Lines 19577 19577
==========================================
- Hits 17716 17710 -6
- Misses 1401 1406 +5
- Partials 460 461 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
bogdandrutu
approved these changes
Jan 28, 2021
dyladan
referenced
this pull request
in dynatrace-oss-contrib/opentelemetry-collector-contrib
Jan 29, 2021
* POC/Proposal for exposing configuration schemas Issue: https://github.com/open-telemetry/opentelemetry-collector/issues/1995 This change proposes a way to generate metadata for the configuration structs used by Collector components. The generated metadata could be used for documentation and tooling. The way it works is, given a component, its configuration struct is found, and its field names, types, tags, default values, and comments are retrieved and put into a struct. This is done recursively, but respecting "squashed" fields, and any fields omitted with a "-" tag. The final struct is marshaled to a yaml file in the directory of the configuration type. Also included are a simple command line interface and an example metadata file. The CLI lets users create a metadata file for either a given component or for all registered components. Tests have not been included as this change is meant to be exploratory. * Use a map rather than an array for fields * Expose component configuration schemas Issue: https://github.com/open-telemetry/opentelemetry-collector/issues/1995 This change adds a command line utility to generate schema files for each of the configuration structs used by Collector components. The intent is for these generated files to be used by documentation utilities and tooling. The way it works is, given a component, its default configuration struct is retrieved and introspected, producing field names, types, default values, and comments. Those are recursively put into a graph of structs, respecting "squashed" fields and any fields omitted with a "-" tag. Finally, the struct is marshaled to a yaml file in the directory of the configuration type. The CLI lets users create a metadata file for either one component or for all registered components. For reference, preliminary feedback was gathered here open-telemetry/opentelemetry-collector#2169 * Create a local go module, don't panic on mapstructure errors * Move code to internal, exclude cfgschema from Makefile * Increase test coverage * Increase test coverage * Fix lint * Reorg so schemagen can be used from contrib * Don't export stuff that no longer needs to be exported
pmatyjasek-sumo
referenced
this pull request
in pmatyjasek-sumo/opentelemetry-collector-contrib
Apr 28, 2021
Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.36.31 to 1.36.33. - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Changelog](https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-go@v1.36.31...v1.36.33) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
ljmsc
referenced
this pull request
in ljmsc/opentelemetry-collector-contrib
Feb 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps github.com/aws/aws-sdk-go from 1.36.31 to 1.36.33.
Release notes
Sourced from github.com/aws/aws-sdk-go's releases.
Changelog
Sourced from github.com/aws/aws-sdk-go's changelog.
Commits
86719c2Release v1.36.33 (2021-01-27)b9efcacMerge pull request #3753 from aws/KaibaLopez-stale-actiona667741Release v1.36.32 (2021-01-26) (#3754)d7693d1Update stale_issues.ymldf6799bRelease v1.36.31 (2021-01-22) (#3749)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)