StatusMessage is not always defined in the progress_event #60
Conversation
|
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 3m 27s |
With MemoryDB, `StatusMessage` is not always defined and this trigger an exception within the existing exception handling block. With this change we fallback on `OperationStatus` if `StatusMessage` is missing. If none of them are available, we will get a `None` instead of an exception. According to the documentation the presence of these two keys is not guarantee. They are both identified as optional (`Required: No`). See: https://docs.aws.amazon.com/cloudcontrolapi/latest/APIReference/API_ProgressEvent.html
goneri
force-pushed
the
StatusMessage-is-not-always-defined-in-the-progress_event_8245
branch
from
ae33577 to
84f3ec2
Compare
|
Build failed. ❌ ansible-galaxy-importer RETRY_LIMIT in 4m 54s |
With MemoryDB,
StatusMessageis not always defined and this trigger an exceptionwithin the existing exception handling block.
With this change we fallback on
OperationStatusifStatusMessageis missing. If none of them are available, we will get a
Noneinstead ofan exception.
According to the documentation the presence of these two keys is not guarantee.
They are both identified as optional (
Required: No).See: https://docs.aws.amazon.com/cloudcontrolapi/latest/APIReference/API_ProgressEvent.html