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

Export AppInsights/Component ConnectionString and InstrumentationKey #2899

Merged
merged 3 commits into from
Apr 18, 2023

Conversation

super-harsh
Copy link
Collaborator

Closes #2820

What this PR does / why we need it:
This PR supports exporting ConnectionString and InstrumentationKey for AppInsights/Component.

If applicable:

  • this PR contains documentation
  • this PR contains tests

@codecov-commenter
Copy link

Codecov Report

Merging #2899 (f4a48c0) into main (710e3d6) will increase coverage by 0.00%.
The diff coverage is 57.64%.

❗ Current head f4a48c0 differs from pull request most recent head dc9643c. Consider uploading reports for the commit dc9643c to get more accurate results

@@           Coverage Diff            @@
##             main    #2899    +/-   ##
========================================
  Coverage   54.40%   54.40%            
========================================
  Files        1248     1248            
  Lines      546976   547288   +312     
========================================
+ Hits       297577   297773   +196     
- Misses     200647   200723    +76     
- Partials    48752    48792    +40     
Impacted Files Coverage Δ
...sights/v1api20200202storage/component_types_gen.go 45.71% <0.00%> (-9.46%) ⬇️
...ights/v1beta20200202storage/component_types_gen.go 63.20% <48.21%> (-3.85%) ⬇️
...api/insights/v1beta20200202/component_types_gen.go 63.54% <56.84%> (-0.80%) ⬇️
.../api/insights/v1api20200202/component_types_gen.go 62.48% <76.84%> (+1.45%) ⬆️

... and 10 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@matthchr matthchr added this to the v2.1.0 milestone Apr 18, 2023
@@ -22,6 +22,10 @@ github.com/Azure/azure-service-operator/v2/api/insights/v1api20200202
│ │ │ └── "LogAnalytics"
│ │ ├── Kind: *string
│ │ ├── Location: *string
│ │ ├── OperatorSpec: *Object (1 property)
│ │ │ └── ConfigMaps: *Object (2 properties)
│ │ │ ├── ConnectionString: *genruntime.ConfigMapDestination
Copy link
Member

Choose a reason for hiding this comment

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

Aren't these secrets, not ConfigMaps?

Shouldn't they be going to secrets?

Or do they not actually contain any secret values?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I thought the same as well and investigated a bit. Azure docs state its not a secret here

@super-harsh super-harsh merged commit 4f5cbc2 into main Apr 18, 2023
8 checks passed
@super-harsh super-harsh deleted the feature/export-component branch April 18, 2023 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

Feature: expose Component's (appinsights) InstrumentationKey and ConnectionString
4 participants