-
Notifications
You must be signed in to change notification settings - Fork 203
Clarifies EDOT SDK authentication using API keys #11170
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
|
This pull request does not have a backport label. Could you fix it @alexandra5000? 🙏
|
🔍 Preview links for changed docs |
theletterf
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.
Let's get @hegerchr 's approval as well.
(Is this related to elastic/opentelemetry#487?)
|
@theletterf Yes, it's related |
|
Hi @hegerchr could you please approve this PR? 🙏 |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
4ffd6e9 to
9639558
Compare
|
@Mergifyio backport 9.1 9.2 |
✅ Backports have been created
|
* Clarifies EDOT SDK authentication using API keys * Remove snippet (cherry picked from commit 15bc3df)
* Clarifies EDOT SDK authentication using API keys * Remove snippet (cherry picked from commit 15bc3df)
* Clarifies EDOT SDK authentication using API keys * Remove snippet (cherry picked from commit 15bc3df) Co-authored-by: Aleksandra Spilkowska <[email protected]>
* Clarifies EDOT SDK authentication using API keys * Remove snippet (cherry picked from commit 15bc3df) Co-authored-by: Aleksandra Spilkowska <[email protected]>
What does this PR do?
Updates documentation to explicitly describe how EDOT SDKs authenticate with the Collector for central configuration using Elasticsearch API keys.
Explains required privileges and configuration for the
apikeyauthextension, improves example clarity, and corrects previous references to resource settings.Why is it important?
Helps users correctly set up secure and functional central configuration flows for SDKs.
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry in./changelog/fragmentsusing the changelog tool- [ ] I have added an integration test or an E2E testDisruptive User Impact
None
Related issues