-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update Authorization E2E Scenarios #641
Merged
Merged
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
* add e2e test for defect fix * fix upgrade * fix upgrade * add downgrade test * fix title
shaynafinocchiaro
requested review from
abhi16394,
mbasha-dell,
alikdell,
bharathsreekanth and
chimanjain
as code owners
July 18, 2024 03:21
shaynafinocchiaro
requested review from
shefali-malhotra,
panigs7,
tdawe,
atye,
sharmilarama and
shanmydell
as code owners
July 18, 2024 03:21
xuluna
previously approved these changes
Jul 18, 2024
donatwork
previously approved these changes
Jul 18, 2024
shaynafinocchiaro
requested review from
xuluna and
donatwork
and removed request for
xuluna
July 18, 2024 14:07
atye
approved these changes
Jul 18, 2024
EvgenyUglov
approved these changes
Jul 18, 2024
mbasha-dell
approved these changes
Jul 18, 2024
donatwork
approved these changes
Jul 18, 2024
ChristianAtDell
added a commit
that referenced
this pull request
Oct 15, 2024
* fix lint * fix lint * prevent short circuit * Fix sanity e2e tests * Revert auth storage templates * Revert auth storage templates * Add e2e test (#629) * add e2e test for defect fix * fix upgrade * fix upgrade * add downgrade test * fix title * Migrate application mobility upgrade to scenarios file * Cages to correct broken authorization e2e for operator * add script changes * auth e2e changes for v1 and v2 * use conditional instead of new steps * v1 changes * minor changes * add uprade path * remove unnecessary steps * remove steps * add support for multiple drivers in a single scenario * Changing logs * add more changes for V2 and multiple drivers * add new step for deleting CRs and combine resources into one file * remove duplicate step * support both drivers on creation and delete for CRs * fix tenant name for token * update scenarios * Adding Powerscale port * only support powerflex for V2 * update readme * move scenario * update note --------- Co-authored-by: JacobGros <jacobgrosner4@gmail.com> Co-authored-by: Fernando Alfaro Campos <Fernando.Alfaro_campos@Dell.com> Co-authored-by: Alik Saring <alik.saring@dell.com> Co-authored-by: Harshita Pandey <Harshita_Pandey@dell.com>
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.
Description
This PR updates all authorization e2e scenarios to cover v1 and v2 versions of authorization.
Adds a step
Delete Authorization CRs for [driver]
.V2 scenarios only support powerflex driver.
Upgrade can only be performed from V1 to other V1 versions.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration