Update api-management-howto-create-or-invite-developers.md #125177
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
we need to be very clear as to which specific persona we are talking about in each of the articles. "developers" is an overloaded term, especially in API eco-system. you have developers who produce APIs, and producers who consume other people's APIs, and then there are consumers who do not publish anything but are interested in consuming someone else's APIs. Finally, there is the APIM back-office or admins. In my commit, i have tried to articulate how a producer can manage its own consumers, since they are the best people to know who they are writing the APIs for. It could be part of their own org, or outside the org, or outside the company.
|
@jishnath : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit f35f882: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
we need to be very clear as to which specific persona we are talking about in each of the articles. "developers" is an overloaded term, especially in API eco-system. you have developers who produce APIs, and producers who consume other people's APIs, and then there are consumers who do not publish anything but are interested in consuming someone else's APIs. Finally, there is the APIM back-office or admins.
In my commit, i have tried to articulate how a producer can manage its own consumers, since they are the best people to know who they are writing the APIs for. It could be part of their own org, or outside the org, or outside the company.