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

Mismatch in the DefaultAction Enum values. #9880

Closed
marcan2020 opened this issue Aug 21, 2019 · 8 comments
Closed

Mismatch in the DefaultAction Enum values. #9880

marcan2020 opened this issue Aug 21, 2019 · 8 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. feature-request This issue requires a new behavior in the product in order be resolved. Service Attention This issue is responsible by Azure service team. Storage

Comments

@marcan2020
Copy link

Description

Opening an issue for tracking as requested by @blueww in #9837.

There's a mismatch between models representing the same thing:

@marcan2020 marcan2020 added Azure PS Team feature-request This issue requires a new behavior in the product in order be resolved. labels Aug 21, 2019
@blueww
Copy link
Member

blueww commented Aug 22, 2019

Will see if can take it in the next major release.

@blueww blueww added the Storage label Aug 22, 2019
@cormacpayne cormacpayne added the Service Attention This issue is responsible by Azure service team. label Aug 22, 2019
@zhusijia26 zhusijia26 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Sep 25, 2019
@kartikshah9
Copy link

@blueww can you please provide an update on this? Has the bug #10396 been fixed and merged. Can this GitHub issue be closed?

@blueww
Copy link
Member

blueww commented Nov 20, 2019

@kartikshah9
This has not been fixed.
For current breaking change process, We need fix it in a major release, and need add warning message for breaking several release before the major release.
#10396 is no merged, and rejected since need add warning several release before the major release.

@kartikshah9
Copy link

@blueww is there a timeline for fixing the above issue in a major release. Request if you can provide an update on the same

@blueww
Copy link
Member

blueww commented Dec 20, 2019

It should be fixed in the next major release.
I will raise a PR for warning message before that.

@kartikshah9 BTW, when will be the next major release?

@zhusijia26
Copy link

@blueww has the fix been released?

@blueww
Copy link
Member

blueww commented Jan 15, 2020

@zhusijia26
No, this hasn't been fixed, since it's a breaking change, it might be fixed in a major release (twice a year).
And I have raised a PR to add breaking change warning, and this PR merged.
Then when the next major release come, we can fix it.

@blueww
Copy link
Member

blueww commented May 19, 2020

Close as the PR to fix this is merged.
It will be in the next PSH release.

@blueww blueww closed this as completed May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. feature-request This issue requires a new behavior in the product in order be resolved. Service Attention This issue is responsible by Azure service team. Storage
Projects
None yet
Development

No branches or pull requests

5 participants