Develocity Instance Configuration
To configure access to a Develocity instance, configure the following application properties:
develocity.instances.<instance-name>.uri=https://develocity.example.com (1)
| 1 | <instance-name> is an identifier you choose (e.g., 'prod-dv' or 'main').
This name is used in access control policies and log messages.
Use alphanumeric characters, dashes, or underscores. |
Provide a Develocity access key in the sensitive application properties:
develocity.instances.<instance-name>.access-key=************ (your access key here)
Advanced Develocity Configuration
The following advanced properties can be configured for each Develocity instance:
develocity.instances.<instance-name>.token-expiration-duration=4h (1)
develocity.instances.<instance-name>.max-retry-attempts=3 (2)
| 1 | The validity duration for generated access tokens. Defaults to 4h. Maximum allowed is 24h (Develocity API limit). Supports standard duration formats like 4h, 30m, PT4H, etc. |
| 2 | The maximum number of retry attempts for Develocity API requests. Defaults to 3. Must be at least 1. |
|
Token Expiration Duration: The token expiration duration controls how long the short-lived access tokens remain valid. Shorter durations provide better security (reduced exposure if a token is compromised), while longer durations reduce the frequency of token refresh operations. The Develocity API enforces a maximum of 24 hours for token validity. |