Skip to content
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

[feature-1281]: Use volume identifier from array response to support Authorization v2 #322

Merged
merged 7 commits into from
Aug 20, 2024

Conversation

atye
Copy link
Contributor

@atye atye commented Aug 19, 2024

Description

To support volumes with tenant prefixes with Authorization v2, the volume flows should use the volume identifier from the array..

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1281

Checklist:

  • Have you run format,vet & lint checks against your submission?
  • Have you made sure that the code compiles?
  • Did you run the unit & integration tests successfully?
  • Have you maintained at least 90% code coverage?
  • Have you commented your code, particularly in hard-to-understand areas
  • Have you done corresponding changes to the documentation
  • Did you run tests in a real Kubernetes cluster?
  • Backward compatibility is not broken

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

@atye atye force-pushed the authorization-volume-identifier branch from 2fba5a0 to 0488bb4 Compare August 19, 2024 18:07
@atye atye merged commit c8a0dd9 into main Aug 20, 2024
5 checks passed
@atye atye deleted the authorization-volume-identifier branch August 20, 2024 15:10
Sahiba-Gupta pushed a commit that referenced this pull request Oct 11, 2024
…Authorization v2 (#322)

* add volume identifier

* use vol identifier from array

* fix volume compare for tenant

* update volume id

* use vol id from array

* revert

* fix linting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants