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
Copy file name to clipboardExpand all lines: docs/operator-manual/upgrading/3.0-3.1.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,28 @@ The `--staticassets` directory in the API server (`/app/shared` by default) is n
20
20
symlinks. This is to help protect against symlink attacks. If you have any symlinks in your `--staticassets` directory
21
21
to a location outside the directory, they will return a 500 error starting with 3.1.
22
22
23
+
## v1 Actions API Deprecated
24
+
25
+
The `/api/v1/applications/{name}/resource/actions` endpoint is deprecated in favor of `/api/v1/applications/{name}/resource/actions/v2`.
26
+
27
+
This endpoint allows API users to run a custom resource action on a specific resource in an application.
28
+
29
+
The old endpoint accepted various parameters as query parameters. The POST body was the action name.
30
+
31
+
The new endpoint accepts all parameters as part of the POST body as a JSON object. The new endpoint also supports a new
32
+
`resourceActionParameters` field to parameterize action runs.
33
+
34
+
The old endpoint will be removed in a future release, so users should migrate to the new endpoint as soon as possible.
35
+
API clients will just need to change the endpoint URL and switch query string parameters to a JSON body.
36
+
37
+
If the old endpoint is used, the API will log a warning message:
38
+
39
+
> RunResourceAction was called. RunResourceAction is deprecated and will be removed in a future release. Use RunResourceActionV2 instead.
40
+
41
+
The CLI will fall back to the old endpoint if the new one is not available. If it falls back, it will log a warning message:
42
+
43
+
> RunResourceActionV2 is not supported by the server, falling back to RunResourceAction.
44
+
23
45
## OpenID Connect authorization code flow with PKCE is now handled by the server instead of the UI
24
46
25
47
Previously, when PKCE was enabled, the authorization code flow (the process which happens when you log in to Argo CD using OpenID Connect) was handled by the UI, whereas this flow was handled by the server if PKCE was not enabled. The server now always handles this flow, PKCE being enabled or not.
0 commit comments