Revert "Removing Neon Reference from Index.json as part of Neon CLI Deprecation"#9690
Revert "Removing Neon Reference from Index.json as part of Neon CLI Deprecation"#9690
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @necusjz, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
CodeGen Tools Feedback CollectionThank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey |
There was a problem hiding this comment.
Pull request overview
This PR reverts the earlier removal of the neon Azure CLI extension from the central src/index.json extension index to unblock CI in other pull requests, and also rolls back a runtime deprecation warning emitted by the Neon extension loader.
Changes:
- Re-add the
neonextension entries (multiple published wheel versions) tosrc/index.json. - Remove the Neon extension loader’s deprecation warning log and its associated
loggingsetup.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
src/neon/azext_neon/__init__.py |
Stops emitting a deprecation warning during command table load (and removes now-unneeded logging code). |
src/index.json |
Restores the neon extension block in the extension index to resolve downstream CI failures relying on it. |
| def load_command_table(self, args): | ||
| logger.warning(_DEPRECATION_WARNING) | ||
| from azext_neon.commands import load_command_table |
|
Hi @necusjz Release SuggestionsModule: neon
Notes
|
152ef4c to
18fa99c
Compare
Reverts #9661
it will cause ci failed in other pull requests, e.g.,
