APIGOV-29369 Apigee X Dual Agent Docs #598
Open
+505
−197
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
alrosca
requested review from
vivekschauhan,
jcollins-axway,
sbolosan and
dgghinea
✅ Deploy preview is ready!
|
sbolosan
reviewed
Jan 30, 2025
|
|
||
| ## Configure the agents with Axway Central CLI | ||
| Set up Google Cloud Platform (GCP) so an Apigee agents can connect to and managed your Apigee X environment within Amplify. |
There was a problem hiding this comment.
...son an Apigee agent instead of agents
sbolosan
reviewed
Jan 30, 2025
|
|
||
| Note that the Docker image of the agent is expecting this `da_env_vars.env` or `ta_env_vars.env` as an argument of the Docker runner `docker run --env-file <PATH>/da_env_vars.env...` | ||
|
|
||
| If you are either struggling with a variable value or you want to benefit from the advanced agents features (API filtering / SSL security / proxy access / logging), the following section describe all the variables the agents (Discovery / Traceability) rely on. |
There was a problem hiding this comment.
...the following section describes, instead of describe
|
|
||
| #### Default mode with browser authentication | ||
| 1. Navigate to *APIs and Services* in your GPC project. |
There was a problem hiding this comment.
typo "GCP" instead of "GPC"
| | APIGEE_AUTHFILEPATH | The path where you put the GCP authentication file in docker container (**Ground agent only**) | | ||
| | APIGEE_PROJECTID | the Project ID for your GCP project | | ||
| | APIGEE_DEVELOPEREMAIL | The Apigee developer email | | ||
| | APIGEE_MODE | Apigee agent running mode | |
There was a problem hiding this comment.
Should we list the modes we support and is there a default mode?
|
|
||
| | Variable name | Description | | ||
| |--------------------------------------|----------------------------------------------------------------------------------------| | ||
| | APIGEE_METRICSFILTER_FILTEREDAPIS | The names of the APIs for which the metrics will be processed | |
There was a problem hiding this comment.
Maybe give an example of the filter format?
robertengaxway
approved these changes
Jan 31, 2025
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.
Thank you for your contribution to the Amplify-Central repo.
Describe the changes
Enter a brief description of your changes to communicate to the reviewers what you changed and why.
Deploy preview link
Please add the deploy preview link to the specific page that you've changed.
Checklist for contributors
Before submitting this PR: