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

add vmware 0.5.4 to index #1367

Merged
merged 23 commits into from
Mar 18, 2020
Merged

add vmware 0.5.4 to index #1367

merged 23 commits into from
Mar 18, 2020

Conversation

ctaggart
Copy link
Contributor

@ctaggart ctaggart commented Mar 9, 2020


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

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

@ctaggart
Copy link
Contributor Author

ctaggart commented Mar 9, 2020

CI failed with You have CLI core version 2.2.0 and this extension requires a min of 2.0.66 and max of 2.1.0.

@ctaggart
Copy link
Contributor Author

ctaggart commented Mar 9, 2020

Removing it didn't work:

ERROR: The 'None' extension is not compatible with this version of the CLI.
You have CLI core version 2.2.0 and this extension requires a min of 2.0.66 and max of 2.1.0.

Do I have to update to the latest CLI core to get it past this?

@ctaggart
Copy link
Contributor Author

CI passes! 🎉

@ctaggart ctaggart changed the title add azure_vmware_virtustream_cli_extension 0.5.0 to index add azure_vmware_virtustream_cli_extension 0.5.2 to index Mar 10, 2020
@ctaggart ctaggart marked this pull request as ready for review March 10, 2020 17:37
@ctaggart ctaggart requested a review from zikalino as a code owner March 10, 2020 17:37
@qwordy
Copy link
Member

qwordy commented Mar 12, 2020

It's a long extension name. 😂

@ctaggart
Copy link
Contributor Author

Yes, azure-vmware-virtustream-cli-extension is a long name. Would you like it renamed?

@ctaggart
Copy link
Contributor Author

az extension add --name azure-vmware-virtustream-cli-extension isn't the most convenient.
az extension add --name vmware would be nice.

@ctaggart
Copy link
Contributor Author

Hold off on merging this. I'm going to change it to just vmware.

@ctaggart ctaggart closed this Mar 12, 2020
@shivam-msft
Copy link
Contributor

Hold off on merging this. I'm going to change it to just vmware.

Sure Cameron. Just "vmware" would be nice.

@ctaggart
Copy link
Contributor Author

The extension installs and works just fine with:

az extension add -s https://github.com/virtustream/azure-vmware-virtustream-cli-extension/releases/download/0.5.3/vmware-0.5.3-py2.py3-none-any.whl -y

CI then runs azdev linter and fails. Any ideas why?

azdev linter --include-whl-extensions vmware
Traceback (most recent call last):
  File "scripts/ci/verify_linter.py", line 213, in <module>
    main()
  File "scripts/ci/verify_linter.py", line 195, in main
    linter_on_external_extension(modified_files[0])
  File "scripts/ci/verify_linter.py", line 160, in linter_on_external_extension
    azdev_extension.linter()
  File "scripts/ci/verify_linter.py", line 77, in linter
    self._cmd('azdev linter --include-whl-extensions {}'.format(self.extension_name))
  File "scripts/ci/verify_linter.py", line 68, in _cmd
    check_call(cmd, shell=True)
  File "/opt/hostedtoolcache/Python/3.6.10/x64/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'azdev linter --include-whl-extensions vmware' returned non-zero exit status 1.

@shivam-msft
Copy link
Contributor

The extension installs and works just fine with:

az extension add -s https://github.com/virtustream/azure-vmware-virtustream-cli-extension/releases/download/0.5.3/vmware-0.5.3-py2.py3-none-any.whl -y

CI then runs azdev linter and fails. Any ideas why?

azdev linter --include-whl-extensions vmware
Traceback (most recent call last):
  File "scripts/ci/verify_linter.py", line 213, in <module>
    main()
  File "scripts/ci/verify_linter.py", line 195, in main
    linter_on_external_extension(modified_files[0])
  File "scripts/ci/verify_linter.py", line 160, in linter_on_external_extension
    azdev_extension.linter()
  File "scripts/ci/verify_linter.py", line 77, in linter
    self._cmd('azdev linter --include-whl-extensions {}'.format(self.extension_name))
  File "scripts/ci/verify_linter.py", line 68, in _cmd
    check_call(cmd, shell=True)
  File "/opt/hostedtoolcache/Python/3.6.10/x64/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'azdev linter --include-whl-extensions vmware' returned non-zero exit status 1.

Hi @qwordy ,

As far as I understand, there are some new linter verifications which were merged from master in this PR (in this commit) which made the CI fail. Can you have a look.

@haroldrandom
Copy link
Contributor

haroldrandom commented Mar 13, 2020

@shivam-msft I am taking care of it. Currently facing an unknown ADO issue that it can not run on PR. will keep posted.

@ctaggart
Copy link
Contributor Author

I'm going to bump this up to 0.5.4 as requested.

@ctaggart ctaggart changed the title add vmware 0.5.3 to index add vmware 0.5.4 to index Mar 13, 2020
@haroldrandom
Copy link
Contributor

@ctaggart The bug in job "CLI Linter on Modifed Extensions" has been fixed. It's feel to go. please take care of the rest of problems.

Welcome to ping me if anything wrong in CI.

src/index.json Outdated Show resolved Hide resolved
@ctaggart
Copy link
Contributor Author

Thanks @haroldrandom !

@ctaggart
Copy link
Contributor Author

CI is passing again. All requested updates are complete. This is ready for a squash merge. cc @shivam-msft

@yungezz
Copy link
Member

yungezz commented Mar 15, 2020

will merge it after sync with master branch

@shivam-msft
Copy link
Contributor

CI is passing again. All requested updates are complete. This is ready for a squash merge. cc @shivam-msft

Looks good to me @ctaggart

@ctaggart
Copy link
Contributor Author

will merge it after sync with master branch

@yungezz I merged the master branch into this repository and it built fine. Is that what you meant? Can you merge this pull request?

@yungezz yungezz merged commit 897f790 into Azure:master Mar 18, 2020
@ctaggart ctaggart deleted the vmware-vs branch March 18, 2020 04:26
@ctaggart
Copy link
Contributor Author

It works! Here is a screenshot from Azure Cloud Shell:

image

@shivam-msft
Copy link
Contributor

It works! Here is a screenshot from Azure Cloud Shell:

image

Awesome!

ManuInNZ pushed a commit to ManuInNZ/azure-cli-extensions that referenced this pull request Apr 11, 2020
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.

6 participants