Skip to content

Webui updates for DAPI 5.6#139

Open
aknot242 wants to merge 8 commits into
mainfrom
update-node
Open

Webui updates for DAPI 5.6#139
aknot242 wants to merge 8 commits into
mainfrom
update-node

Conversation

@aknot242

Copy link
Copy Markdown
Collaborator

Proposed changes

DAPI v5.6 had some breaking changes. Update the UI to conform. The change from v5.5 to v5.6 is moving Certs and WAF Policies from .output into .declaration.

Checklist

Before creating a PR, run through this checklist and mark each as complete:

@aknot242

Copy link
Copy Markdown
Collaborator Author

@copilot resolve the merge conflicts in this pull request

Copilot AI commented May 27, 2026

Copy link
Copy Markdown

@copilot resolve the merge conflicts in this pull request

Conflicts are resolved and merged with origin/main in commit bd7c696.

@aknot242 aknot242 closed this May 27, 2026
@aknot242 aknot242 reopened this May 27, 2026

Copilot AI commented Jun 26, 2026

Copy link
Copy Markdown

@copilot The owner of this workspace provided me feedback on the webui. He would like changes. Here is his message which includes what he is asking to change:

When switching from "Form" to "JSON" mod...

Implemented in 89bc27c.

  • JSON mode is now read-only.
  • API Gateway profile selection now ensures enforceOnPaths and paths are set for rate limiting, authentication, and authorization.
  • Added tests covering both behaviors.

…s enabled

When a location has `apigateway` configured, authentication and
authorization must be nested under `locations[].apigateway`, not at
`locations[]` directly. The `ApiGatewayEditor` already handles auth/authz
in the correct place, so the location-level `LocationAuthEditor` and
`LocationAuthzEditor` are now suppressed when `loc.apigateway != null`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants