-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: added missing examples and plugged test gaps #384
Conversation
/run pipeline |
/run pipeline |
/run pipeline |
pipeline failing by the error
re-running the pipeline |
/run pipeline |
pipeline failing by the error
re-running the pipeline |
/run pipeline |
This was because the KMS (us-south HPCS) was being upgraded/migrated at the time the test ran. |
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.
At a higher level, it should be unnecessary to include common-dev-assets in a PR. This should be bumped on a standalone cycle and by including it, there is a risk of merge conflicts as the main branch changes or potentially rolling it back.
It is good to see backup-restore coverage being added to elasticsearch. However, when compared to etcd and mongodb example it is different. The ICD module tests should be converging, not diverging with every commit.
The basic example changes are good. Converging the source, so that it is more consistent across modules. This reduces maintenance moving forward, allow for cut-n-paste or possibly cherry picking changes from one module to another.
/run pipeline |
/run pipeline |
/run pipeline |
The main branch Not sure why this is the case , but I don't see any recent renovate PR to update CI depnedecies |
/run pipeline |
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.
LGTM
I will follow up as to why renovate is not bumping common-dev-assets automatically.
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
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.
LGTM. All issues addressed.
@Aditya-ranjan-16 FYI, there are no code changes to the module or DA, just the example and test - so this means we do no need a new release. See Release versioning for more info |
🎉 This PR is included in version 1.28.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
added missing examples and covered test gaps
GIT Issue
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
adds missing examples and covers test gaps
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers