Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Document MicrosoftGraphOrgReaderProcessor integration
See original GitHub issueNow that we have a good documentation for GithubOrgReaderProcessor and LdapOrgReaderProcessor thanks to #4561 we should also provide one for MicrosoftGraphOrgReaderProcessor.
- How to setup?
- How to configure? (Secrets, filters, …)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Integrations · Backstage Software Catalog and Developer ...
Integrations allow Backstage to read or publish data using external providers such as GitHub, GitLab, Bitbucket, LDAP, or cloud providers.
Read more >@backstage/plugin-catalog-backend-module-msgraph: Versions ...
Full version history for @backstage/plugin-catalog-backend-module-msgraph including change logs.
Read more >backstage/backstage release-2021-06-24 on GitHub
Add the processor to the catalog builder: // packages/backend/src/plugins/catalog.ts builder.addProcessor( MicrosoftGraphOrgReaderProcessor.
Read more >Errors in Event Log after every execution of azcopy - azure-storage ...
Execute any azcopy copy command (maybe it can be aslo triggered by some other azcopy commands, but i have tried only copy). Have...
Read more >SharePoint Integration Installation Guide
Overview. This article will walk through the steps required to integrate from both the Microsoft side and the Beekeeper side.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It would be a kinda good learning exercise for understanding the catalog, I think! You have the two other “Org Data” sections in the docs (e.g. here) to base it off of, and it’s mostly about documenting the config options etc which requires you to learn a bit about how config propagates in backstage. Little things like that. I can help out if you want.
My PR for splitting this out into a separate package (#5854) also contains the documentation in the README. Do we just want to include a small page in the microsite that links to the README?