-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Migrate instrumentation_key to connection_string for spring-cloud extension #3467
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
|
Thank you for your contribution ECNUJason! We will review the pull request and get back to you soon. |
|
spring cloud |
…tation key to connection string, fall back to instrumentation key when connection string is not available
|
Add @kairu-ms for awareness |
|
Could you add some tests for the feature change? |
kairu-ms
left a comment
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.
The sdk version of app-insights already update to 1.0.0 in latest cli. Please update azext.minCliCoreVersion to the latest cli version
by transforming 'intrumentation key' to 'connection string'; 3. Use concret type of exception to replace general CLIError; 4. fix typo for connection; 5. Add unit test;
Updated to |
Sure, added. |
* Revert "Migrate instrumentation_key to connection_string for spring-cloud extension (#3467)" This reverts commit 097827a * Add release note and set version Co-authored-by: Mason(Jie) Chen <[email protected]>
For extension: Spring-Cloud Application-Insights, migration instrumentation key to connection string, fall back to instrumentation key when connection string is not available
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update
src/index.jsonautomatically.The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify
src/index.json.