You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the execution agent, in the `url` field you need to provide a URL to a service (for example, a REST API) that will accept the invocation event.
8
-
9
-
- The service can be a private service running inside your private network;
10
-
- Or, it can be a public accessible service from the public internet (**note** in this scenario, the execution agent needs corresponding outbound network rules that will allow it to contact the public service).
11
-
12
-
:::note
13
-
**IMPORTANT**: To make use of the **Port execution agent**, you need to configure:
7
+
To make use of the **Port execution agent**, you need to configure:
14
8
15
9
<!-- TODO: add back the URLs here for changelog destination -->
Well Done! **Port Agent** is now running in your environment and will trigger any webhook that you've configured (for self-service actions, or changes in the software catalog).
20
+
When using the execution agent, in the `url` field you need to provide a URL to a service (for example, a REST API) that will accept the invocation event.
28
21
29
-
When a new invocation is detected, the agent will pull it from your Kafka topic and forward it to the internal API in your private network.
22
+
- The service can be a private service running inside your private network;
23
+
- Or, it can be a public accessible service from the public internet (**note** in this scenario, the execution agent needs corresponding outbound network rules that will allow it to contact the public service).
24
+
25
+
Once configured, the Port Agent will run in your environment and trigger webhooks for self-service actions or software catalog changes.
26
+
27
+
When a new invocation is detected, the agent pulls it from your Kafka topic and forwards it to the internal API in your private network.
For a complete list of all available configuration parameters and their descriptions, see the [Port Agent Helm chart README](https://github.com/port-labs/helm-charts/tree/main/charts/port-agent).
33
+
:::
33
34
34
-
## Advanced configuration
35
-
Some environments require special configuration when working with the Port agent. This includes working with self-signed certificates and/or proxies.
35
+
## Self-signed certificate configuration
36
36
37
-
Port's agent uses Python's [requests](https://requests.readthedocs.io/en/latest/) library. This allows passing advanced configuration using environment variables.
37
+
For self-hosted 3rd-party applications with self-signed certificates, the agent can be configured to trust custom CA certificates. The `selfSignedCertificate` parameters control this behavior.
38
38
39
-
To add an environment variable using the agent's Helm chart, either:
When `selfSignedCertificate.enabled` is set to `true`, the Helm chart automatically:
118
+
- Mounts the certificate to `/usr/local/share/ca-certificates/cert.crt`
119
+
- Sets `SSL_CERT_FILE` and `REQUESTS_CA_BUNDLE` environment variables to point to the certificate
120
+
121
+
### Multiple certificates
122
+
123
+
For environments requiring multiple custom certificates, use the `extraVolumes` and `extraVolumeMounts` parameters alongside the built-in `selfSignedCertificate` feature. One certificate must be provided via `selfSignedCertificate`, and additional certificates can be mounted as extra volumes.
`NO_PROXY`allows blacklisting certain addresses from being handled through a proxy. This variable accepts a comma-seperated list of hostnames or urls.
206
+
`NO_PROXY`allows blacklisting certain addresses from being handled through a proxy. This variable accepts a comma-separated list of hostnames or URLs.
73
207
74
208
For example:
75
209
```sh showLineNumbers
76
210
NO_PROXY=http://127.0.0.1,google.com
77
211
```
78
212
79
-
For more information take a look at the Requests [proxy configuration documentation](https://requests.readthedocs.io/en/latest/user/advanced/#proxies).
80
-
81
-
### SSL Environment Configuration
82
-
83
-
### Certificate Configuration
84
-
85
-
#### Self-signed certificate
86
-
87
-
Use the following Helm values:
88
-
- Set `selfSignedCertificate.enabled` to `true`.
89
-
- Put your PEM-encoded CA content in `selfSignedCertificate.certificate`.
90
-
91
-
The certificate should be mounted to `/usr/local/share/ca-certificates/`.
92
-
93
-
`REQUESTS_CA_BUNDLE`is an environment variable used to specify a custom Certificate Authority (CA) bundle for verifying SSL/TLS certificates in HTTPS requests.
94
-
95
-
Set `REQUESTS_CA_BUNDLE` to the file path of your CA bundle, which should contain one or more CA certificates in PEM format.
96
-
97
-
For example:
98
-
```sh
99
-
REQUESTS_CA_BUNDLE=/path/to/cacert.pem
100
-
```
101
-
102
-
This configuration directs the `requests` library to use the specified CA bundle for SSL/TLS certificate verification, overriding default system settings. It's useful for trusting self-signed certificates or certificates from a private CA.
103
-
104
-
#### Multiple certificates
105
-
106
-
Use the following Helm values:
107
-
- Keep your certificate via `selfSignedCertificate` as above.
108
-
- Add other certificates by supplying files via `extraVolumes` and mounting them with `extraVolumeMounts` into the container at `/usr/local/share/ca-certificates/<your-cert-name>.crt`.
109
-
110
-
:::info Certificate file requirements
111
-
- Each certificate must be provided in a separate PEM file. Files containing multiple certificates are not supported.
112
-
- Certificates must be mounted to `/usr/local/share/ca-certificates/` with a `.crt` file extension.
113
-
:::
213
+
For more information, see the Requests [proxy configuration documentation](https://requests.readthedocs.io/en/latest/user/advanced/#proxies).
114
214
115
215
## Next Steps
116
216
117
217
Follow one of the guides below:
118
218
119
-
- [GitLab Pipeline Trigger](/actions-and-automations/setup-backend/gitlab-pipeline/gitlab-pipeline.md) - Create an action that triggers GitLab Pipeline execution.
219
+
- [GitLab Pipeline Trigger](/actions-and-automations/setup-backend/gitlab-pipeline/gitlab-pipeline.md) - Create an action that triggers GitLab Pipeline execution.
0 commit comments