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
Couper 1.9 is a feature release bringing more comfort and enhanced stability to
the Couper configuration. It also improves the permission handling and provides a
couple of bug fixes. For a complete list of changes see below.
As of release 1.9 it is possible to split a Couper configuration into multiple .hcl-files. You can now, for example, use different configuration files for
your api, files and definitions blocks, or keep your development, testing
and production setups separated. All the configuration files given at startup will be merged together.
The new block beta_health (beta)
allows you to configure recurring health check requests for a backend.
By default, Couper won't request backends considered unhealthy which might help
them recover due to the reduced amount of requests.
The current health state of a backend can be accessed by variable.
Changes in healthiness will be logged and exported as metrics.
To make permission handling easier to grasp we've dropped the term scope and
accordingly changed the names of the beta_scope, beta_scope_claim and beta_scope_map
attributes to beta_required_permission, beta_permissions_claim and beta_permissions_map,
respectively. Furthermore, beta_required_permission (formerly beta_scope) can now
be an HCL expression. If beta_required_permission is specified in both an endpoint
and its parent api block, the former overrides the latter.
Our permission handling examples illustrate some common use cases: basic example, roles example, map example
Along with this release goes the latest extension for VSCode
which now indicates misplaced blocks and attributes, missing block labels and so on.
We've also updated the completion suggestions and fixed a couple of syntax highlighting
issues.
renamed beta_scope attribute for api and endpoint blocks to beta_required_permission; beta_required_permission in endpoint now overridingbeta_required_permission in containing api block; allowing an expression as attribute value
renamed beta_scope_claim and beta_scope_map attributes for jwt block to beta_permissions_claim and beta_permissions_map
removed beta_operation_denied and beta_scopeerror types
renamed beta_insufficient_scopeerror type to beta_insufficient_permissions
added request.context.beta_required_permission and request.context.beta_granted_permissionsrequest variables
Keys in object type attribute values are only handled case-insensitively if reasonable (e.g. they represent HTTP methods or header field values) (#461)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
1.9.0
Couper 1.9 is a feature release bringing more comfort and enhanced stability to
the Couper configuration. It also improves the permission handling and provides a
couple of bug fixes. For a complete list of changes see below.
As of release 1.9 it is possible to split a Couper configuration into multiple
.hcl
-files. You can now, for example, use different configuration files foryour
api
,files
anddefinitions
blocks, or keep your development, testingand production setups separated. All the configuration files given at
startup will be merged together.
The new block
beta_health
(beta)allows you to configure recurring health check requests for a backend.
By default, Couper won't request backends considered unhealthy which might help
them recover due to the reduced amount of requests.
The current health state of a backend can be accessed by variable.
Changes in healthiness will be logged and exported as metrics.
To make permission handling easier to grasp we've dropped the term
scope
andaccordingly changed the names of the
beta_scope
,beta_scope_claim
andbeta_scope_map
attributes to
beta_required_permission
,beta_permissions_claim
andbeta_permissions_map
,respectively. Furthermore,
beta_required_permission
(formerlybeta_scope
) can nowbe an HCL expression. If
beta_required_permission
is specified in both anendpoint
and its parent
api
block, the former overrides the latter.Our permission handling examples illustrate some common use cases:
basic example,
roles example,
map example
Along with this release goes the latest extension for VSCode
which now indicates misplaced blocks and attributes, missing block labels and so on.
We've also updated the completion suggestions and fixed a couple of syntax highlighting
issues.
Added
beta_health
-block tobackend
-block to enable continuous health-checks for defined backends (#313)backends.<name>.health
variable to access the current health-check state (subject to change)url
attribute could make use of our wildcard pattern/**
and relative urls in combination with a backend reference (#480)jwks_max_stale
injwt
block (#502)jwks_ttl
,jwks_max_stale
andconfiguration_max_stale
inoidc
block (#502)backend
,backend_openapi_validation
andbackend_timeout
error types (#490)response.bytes
log-field to backend logs if read from body, fallback is theContent-Length
header (#494)endpoint
andaccess_control
(#500)Changed
beta_scope
attribute forapi
andendpoint
blocks tobeta_required_permission
;beta_required_permission
inendpoint
now overridingbeta_required_permission
in containingapi
block; allowing an expression as attribute valuebeta_scope_claim
andbeta_scope_map
attributes forjwt
block tobeta_permissions_claim
andbeta_permissions_map
beta_operation_denied
andbeta_scope
error typesbeta_insufficient_scope
error type tobeta_insufficient_permissions
request.context.beta_required_permission
andrequest.context.beta_granted_permissions
request variablesspa
block can be defined multiple times now (#510)files
block can be defined multiple times now (#513)Fixed
error_handler
blocks (#462)error_handler
blocks for an error type defined in bothendpoint
andapi
(#469)allowed_methods
attribute ofapi
orendpoint
blocks (#478)backend
blocks inproxy
andrequest
blocks (#483)error_handler
block following anothererror_handler
block has no label (#486)duplicate endpoint /**
error for APIs sharing the same base path (#507)backend_responses
(#501)expected_status
check for a request configured via aproxy
orrequest
block if abackend
error occured (#505)merge()
function removes key withnull
value. (#518)Removed
beta_oidc
block (useoidc
block instead) (#475)beta_oauth_authorization_url
andbeta_oauth_verifier
functions (useoauth2_authorization_url
andoauth2_verifier
functions instead) (#475)path
attribute fromendpoint
(andproxy
) block; usepath
attribute inbackend
block instead (#516)This discussion was created from the release v1.9.0.
Beta Was this translation helpful? Give feedback.
All reactions