-
Notifications
You must be signed in to change notification settings - Fork 933
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
Ginkgo v2 additional changes #2832
Conversation
- would be nice to use command.config but we couldn't see an easy way to thread it Co-authored-by: david alvarado <alvaradoda@vmware.com>
* Add user agent info for plugin api calls - Newer lager was needed with newer diego-ssh * Replace depracted ginkgo calls with non deprecated calls * Remove ACK_GINKGO_RC * Desperate attempt at resolving output issue by using serial decorator and using non deprecated pty * Turn off Gingkno v2 parallel mode * Adjust integration tests to use ginkgo v2 * Add Byte to lograte, disk and memory regexes used by int tests --------- Co-authored-by: M. Oleske <moleske@pivotal.io> Co-authored-by: Al Berez <al.berez@broadcom.com> Co-authored-by: Cristhian Peña <ccjaimes@users.noreply.github.com> Co-authored-by: Marc Paquette <marc.paquette@broadcom.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.
Thanks for finding this deprecated call! The final file diff looks good, though I'm little confused at the other 11 commits. Though won't be a problem with squash and merge option. Assuming they'll be a similar v8/v7 pr?
Yes, will squash and merge this change in main and will update v8/v7 PRs as well. |
Update deprecated v1 calls to use v2
Update deprecated v1 calls to use v2
Update deprecated v1 calls to use v2
Update deprecated v1 calls to use v2
Thank you for contributing to the CF CLI! Please read the following:
If your contribution falls under a company CLA but your membership is not public, expect delays while we confirm.
Where this PR should be backported?
Description of the Change
Replaced deprecated ginkgo v1 references with v2 ones.
We must be able to understand the design of your change from this description.
Keep in mind that the maintainer reviewing this PR may not be familiar with or
have worked with the code here recently, so please walk us through the concepts.
Why Is This PR Valuable?
What benefits will be realized by the code change? What users would want this change? What user need is this change addressing?
Applicable Issues
List any applicable GitHub Issues here
How Urgent Is The Change?
Is the change urgent? If so, explain why it is time-sensitive.
Other Relevant Parties
Who else is affected by the change?