NGINX Declarative API v5.4.1

Added:
None

Updated:

• Kubernetes deployment sample manifest

Fixed:

• Issue when rate limit profile name contained whitespaces

Removed:
None

Notes:

• NGINX App Protect support for NGINX One Console does not currently support logging

Known issues:

• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.4.0

Added:

• OpenID Connect support for https://nginx.org/en/docs/http/ngx_http_oidc_module.html
• ACME protocol support for https://nginx.org/en/docs/http/ngx_http_acme_module.html
• DNS resolvers support at HTTP context level

Updated:

• README.md
• FEATURES-5.4.md
• Postman collection

Fixed:

• Minor bugfixes
• Authentication, authorization, rate limiting and cache profile names for the API Gateway use case are now checked for validity

Removed:

• API v5.2

Notes:

• NGINX App Protect support for NGINX One Console does not currently support logging

Known issues:

• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.3.4

Added:

• Stable support for NGINX App Protect through NGINX One Console. Note: NGINX App Protect logging not supported yet.

Updated:

• README.md
• FEATURES.md
• Postman collection

Fixed:

• Fixed issue when PATCH was used with NGINX One Console

Removed:
None

Notes:

• NGINX App Protect support for NGINX One Console does not currently support logging

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.3.3

Added:

• Initial code for NGINX App Protect support for NGINX One Console - currently alpha stage/unstable
• HTTP and stream servers configurations are now created into dedicated files under /etc/nginx/servers/http/ and /etc/nginx/servers/stream/ for added readability

Updated:

• README.md
• FEATURES.md

Fixed:

• Bug found in v5.3.2 when TLS certificates and keys were base64-encoded in .output.[nms|nginxone].certificates[].contents.content

Removed:

• NGINX Declarative API v5.1

Notes:

• NGINX App Protect support for NGINX One Console is currently alpha stage, unstable and incomplete

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.3.2

Added:
None

Updated:
None

Fixed:

• Bug when API Gateway JSON used a non-URL referenced, base64-encoded OpenAPI schema

Removed:

• Unused NGINX App Protect compiler module

Notes:
None

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.3.1

Added:
None

Updated:
None

Fixed:

• Bug when NGINX Instance Manager REST API respond with HTTP/500 when deploying NGINX App Protect WAF policies

Removed:
None

Notes:
None

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.3.0

Added:

• API v5.3
• Concurrent access and queuing mode - see the overview

Updated:

• Postman collection
• README.md
• FEATURES.md

Fixed:

• API Gateway use case breaks when multiple API gateways across multiple servers use the same location
• NGINX One Console config sync groups bug due to REST API pagination being enabled

Removed:

• API v5.0

Notes:
None

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.2.3

Added:

• Caching support at http, server, location and for the API Gateway use case
• Pre-built docker images

Updated:

• Postman collection
• README.md
• FEATURES.md

Fixed:
None

Removed:
None

Notes:
None

Known issues:

• authentication, authorization, rate limiting and cache profile names for the API Gateway use case are not checked for validity
• API Gateway use case breaks when multiple API gateways across multiple servers use the same location
• API Gateway: no support (yet) for per-location upstream servers in OpenAPI schemas

NGINX Declarative API v5.2.2

Added:
None

Updated:
None

Fixed:

• API Gateway use case: query_string was not forwarded to upstream servers
• Fixed configuration publish to NGINX One Console when immediate HTTP/200 confirmation was received

Removed:
None

Notes:
None

NGINX Declarative API v5.2.1

Added:
None

Updated:

• Features list
• v5.2 Usage README

Fixed:

• Postman collection requests missing the URL
• Issue #75 Support for externally-provided NGINX Plus R33+ jwt license tokens by omitting .output.license.token
• Issue #76 Python exception when DNS failed to resolve NGINX Instance Manager / NGINX One Console FQDN

Removed:
None

Notes:
None