-
Notifications
You must be signed in to change notification settings - Fork 4k
Update to R4.5 RP standard (#22) #9680
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
Conversation
Static analysis failures but these don't look related to the changes being made. Please advise. |
@@ -83,7 +84,7 @@ public class NewAzureRmNetAppFilesVolume : AzureNetAppFilesCmdletBase | |||
Mandatory = true, | |||
HelpMessage = "The maximum storage quota allowed for a file system in bytes")] | |||
[ValidateNotNullOrEmpty] | |||
public long? UsageThreshold { get; set; } | |||
public long UsageThreshold { get; set; } |
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.
This is one of the places causing the breaking change issue
@@ -71,7 +71,7 @@ public class NewAzureRmNetAppFilesPool : AzureNetAppFilesCmdletBase | |||
Mandatory = true, | |||
HelpMessage = "The size of the ANF pool")] | |||
[ValidateNotNullOrEmpty] | |||
public long? PoolSize { get; set; } | |||
public long PoolSize { get; set; } |
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.
This is one of the places causing the breaking change issue
@leonardbf I made comments on where is causing the breaking change issue. Please take a look. You were removing the nullable property of these type (which is the |
@niander the nullable property in the generated code changed because the swagger changed such that these became required fields. I therefore matched this in the cmdlet and actually this was necessary to resolve a build error in assigning the non-nullable to nullable in the cmdlet body. I suppose I could provide a default but this is contrary to what expected. What's the normal solution to resolve this. Also, can you confirm, is this the sole cause of the failing checks? |
@leonardbf Hi! I am sorry but I forgot that NetApp is still in preview. Thus, its is ok to have this breaking change. The only thing we need here is to suppress it. Check our docs here to see how to do it. I am not sure if this is the sole cause of all failing checks but according to the |
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.
just a small comment and I think after suppressing the breaking changes and passing CI it is good to go
@@ -45,6 +45,6 @@ | |||
// | |||
// You can specify all the values or you can default the Build and Revision Numbers | |||
// by using the '*' as shown below: | |||
[assembly: AssemblyVersion("0.9.0")] | |||
[assembly: AssemblyFileVersion("0.9.0")] | |||
[assembly: AssemblyVersion("1.1.0")] |
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.
You don't need to change assembly versions for test projects
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.
ok, I will revert this
@leonardbf Ping waiting for your changes to fix the anlysis breaks, per Niander's comments |
@niander or @markcowl ok, thanks. I have looked at the static analysis page referenced above and see that I need to add the breaking changes file to the exceptions area. However, I'm not sure where I find the original BreakingChangeIssues.csv. It says it is under the Jenkin's build artifacts. Can you give me the link to that please. Also, I'd like to be sure about the preview status. The ANF service went GA a few weeks ago so does that not also mean that the PowerShell cmdlets are actually now GA? |
@niander assistance with the couple of points in my previous comment would be appreciated. Many thanks. |
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.
Just forget to add a comment and please change the changelog.md file
@@ -24,5 +24,5 @@ | |||
[assembly: ComVisible(false)] | |||
[assembly: CLSCompliant(false)] | |||
[assembly: Guid("42656543-77AD-4968-BA4B-BE0778705625")] | |||
[assembly: AssemblyVersion("0.1.1")] | |||
[assembly: AssemblyFileVersion("0.1.1")] | |||
[assembly: AssemblyVersion("1.1.0")] |
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.
You don't need to change this too
@leonardbf Hi. You can find the |
@niander I updated the PR with the BreakingChangeIssues.csv file just to check the validation but the pipeline now seems to be stuck. I don't see any links to the process to try and restart. |
/azp run |
Pull request contains merge conflicts. |
Replaced with #9762 |
Addition of protocolTypes
Internal ticket NFSAAS-2898
Description
Checklist
CONTRIBUTING.md
platyPS
module