Skip to content

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

Closed
wants to merge 0 commits into from
Closed

Conversation

leonardbf
Copy link
Contributor

Addition of protocolTypes
Internal ticket NFSAAS-2898

Description

Checklist

@leonardbf
Copy link
Contributor Author

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; }
Copy link
Member

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; }
Copy link
Member

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

@niander
Copy link
Member

niander commented Jul 19, 2019

@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 ? suffix for the type names)

@leonardbf
Copy link
Contributor Author

@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 ? suffix for the type names)

@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?

@niander
Copy link
Member

niander commented Jul 19, 2019

@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 BreakingChangeIssues.csv those two are the only static analysis breaking change issues.

Copy link
Member

@niander niander left a 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")]
Copy link
Member

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

Copy link
Contributor Author

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

@markcowl
Copy link
Member

@leonardbf Ping waiting for your changes to fix the anlysis breaks, per Niander's comments

@leonardbf
Copy link
Contributor Author

leonardbf commented Jul 23, 2019

@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 BreakingChangeIssues.csv those two are the only static analysis breaking change issues.

@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?

@leonardbf
Copy link
Contributor Author

@niander assistance with the couple of points in my previous comment would be appreciated. Many thanks.

Copy link
Member

@niander niander left a 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")]
Copy link
Member

@niander niander Jul 29, 2019

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

@niander
Copy link
Member

niander commented Jul 29, 2019

@leonardbf Hi. You can find the BreakingChangeIssues.csv file in your computer when you build your project and run the static analysis. It is the same one generated by the CI (azure devops, since we are not using jenkins anymore. Sorry about that). About the PowerShell module going from Preview to Release it should happen after we merge these changes and release a new version of it. After that we can talk about going to Release and adding the module to Az

@leonardbf
Copy link
Contributor Author

@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.

@cormacpayne
Copy link
Member

/azp run

@azure-pipelines
Copy link
Contributor

Pull request contains merge conflicts.

@leonardbf leonardbf mentioned this pull request Aug 2, 2019
8 tasks
@leonardbf
Copy link
Contributor Author

Replaced with #9762

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

Successfully merging this pull request may close these issues.

5 participants