Skip to content

Conversation

@leonardbf
Copy link
Contributor

Previously the Azure NetApp Files CLI was an extension only.
R4 standard of RP for GA


This checklist is used to make sure that common guidelines for a pull request are followed.

  • The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

  • I adhere to the Command Guidelines.

leonardbf and others added 4 commits May 10, 2019 13:44
Previously the Azure NetApp Files CLI was an extension only.
R4 standard of RP for GA
NFSAAS-2316 first version of ANF CLI
Previously the Azure NetApp Files CLI was an extension only.
R4 standard of RP for GA
NFSAAS-2316 first version of ANF CLI
@leonardbf leonardbf requested a review from tjprescott May 10, 2019 15:08
@leonardbf
Copy link
Contributor Author

@tjprescott There are CI failures but it seems I should be merging branches dev to dev not master to master. Is that correct?

@tjprescott
Copy link
Member

No one is allowed to make PRs to the master branch.

Copy link
Member

@tjprescott tjprescott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will require a full command review. Please schedule accordingly.

++++++++++++++++++

* GA release.
* Previously existed as cli-extension.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You will need to schedule a full command review to move this from an extension to a module. Do not put the date in the version. "Previously existed as cli-extension" is not a customer-facing thing.

Copy link
Contributor Author

@leonardbf leonardbf May 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You will need to schedule a full command review to move this from an extension to a module. Do not put the date in the version. "Previously existed as cli-extension" is not a customer-facing thing.

Ok. I will remove the date and the cli-extension text. Can you tell me the process for the command review? I know one of these was already performed, initiated through email with Shane Mainali among others, and the commands agreed in a meeting. It was then decided that because the swagger was in preview that the service should be an extension. I did not expect another review was needed. Actually I also used the information here https://github.com/Azure/azure-cli/blob/dev/doc/extensions/faq.md#how-do-i-move-from-an-extension-to-a-command-module as a guide which doesn't mention the need for a further review either.

netappfiles_custom = CliCommandType(operations_tmpl='azure.cli.command_modules.netappfiles.custom#{}')
super(NetAppFilesCommandsLoader, self).__init__(cli_ctx=cli_ctx,
min_profile='2017-03-10-profile',
custom_command_type=netappfiles_custom)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add logic to suppress the extension here or the older extension will override your newer module.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to add logic to suppress the extension here or the older extension will override your newer module.

Ok that makes good sense. What needs added to perform this?



def netappfiles_exception_handler(ex):
if isinstance(ex, CloudError) or isinstance(ex, ValidationError) or isinstance(ex, ValueError):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems very generic. The default CLI exception handler should be sufficient.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems very generic. The default CLI exception handler should be sufficient.

Ok. What is the default CLI exception? Should I not capture the CloudError? The ValidationError and ValueError were added deliberately because otherwise certain invalid commands would result in a trace log which didn't seem to be what a CLI user would want to see. Please advise further.

short-summary: A list of space separated tags to apply to the account
- name: --active-directories
type: string
short-summary: An array of active directory (AD) settings in json format. Limitation one AD/subscription. Consists of the fields username (Username of Active Directory domain administrator), password (Plain text password of Active Directory domain administrator), domain (Name of the Active Directory domain), dns (Comma separated list of DNS server IP addresses for the Active Directory domain), smb_server_name (NetBIOS name of the SMB server. This name will be registered as a computer account in the AD and used to mount volumes. Must be 10 characters or less), organizational_unit (The Organizational Unit (OU) within the Windows Active Directory)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this alone, this module can only be created in preview.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this alone, this module can only be created in preview.

Sorry I don't really get your meaning here. Can you explain a bit further?

@leonardbf
Copy link
Contributor Author

This will require a full command review. Please schedule accordingly.

Ok. And this is the case even though it had a command review for the extension? Can you tell me how I go about this? Thanks.

@leonardbf
Copy link
Contributor Author

No one is allowed to make PRs to the master branch.

Ok. So what branch should I be using? Thanks.

@leonardbf
Copy link
Contributor Author

@tjprescott Please give me some feedback on these comments. In particular if a new command review is required then I need to know how and get this moving as soon as I can. Thanks.

@tjprescott
Copy link
Member

Your PR needs to target the dev branch. A full review is required when a new module/extension is created, when transitioning from extension to module and when declaring a module GA.

@leonardbf
Copy link
Contributor Author

@tjprescott I'm closing this PR and opening #9387 on dev branch. I will also initiate a command review but as yet have no info on whether there is a formal process (as for PowerShell) so will just be including some Microsoft and NetApp folks in an email thread as was done previously. However you have raised some points here which look important to include in the code change and as yet I've had no feedback on my questions. Thanks in advance.

@tjprescott tjprescott closed this May 14, 2019
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.

2 participants