-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Dependabot: fix cloud providers' SDK dependencies #40125
Conversation
After visiting https://github.com/elastic/beats/network/updates, I noted the following message: > Update configs must have a unique combination of 'package-ecosystem', 'directory', and 'target-branch' In our use case, the two `package-ecosystem: gomod` definitions have the same values: package-ecosystem: gomod directory: / target-branch: <default value> So, I guess we must use only one definition.
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
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.
From platform-ingest eng-prod PoV LGTM
Co-authored-by: Dimitrios Liappis <[email protected]>
Proposed commit message
Fix Dependabot config for cloud providers' SDK dependencies.
After visiting https://github.com/elastic/beats/network/updates, I noted the following message:
In our use case, the two
package-ecosystem: gomod
definitions have the same values:We can't have two
package-ecosystem: gomod
definitions for the same directory.So, I guess we must merge the CSP SDK definition into the existing one.
Checklist
My code follows the style guidelines of this projectI have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues