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
{{ message }}
This repository has been archived by the owner on Nov 18, 2020. It is now read-only.
I am trying to use @EnvironmentVariable annotation, currently if annotated environment variable is not set in the deployed environment the fields are left with "null" value.
I can see we have option to set a default value, can we also have an option to throw an exception if a given environment variable is not set. This allows us to fail the applications during configuration initialization.
The text was updated successfully, but these errors were encountered:
Makes sense, as there is no way to fail fast currently. This can actually be added to all annotations. Let me plan this for next release. Thank you for raising this issue!
fmbenhassine
changed the title
Ability to throw exemption/reject if an Environment Variable is not set
Add ability to fail fast by throwing an exception if a property is absent
Jun 7, 2020
I am trying to use @EnvironmentVariable annotation, currently if annotated environment variable is not set in the deployed environment the fields are left with "null" value.
I can see we have option to set a default value, can we also have an option to throw an exception if a given environment variable is not set. This allows us to fail the applications during configuration initialization.
The text was updated successfully, but these errors were encountered: