Sebastian Brudziński

Update deploy_to_uat_env.sh

    • -1
    • +1
    /deployment/uat_env/deploy_to_uat_env.sh
Update deploy_to_test_env.sh

Revert "Update deploy_to_uat_env.sh"

This reverts commit 2529ec82f84013a93223defc6c6f3c31440a1622.

    • -1
    • +1
    /deployment/uat_env/deploy_to_uat_env.sh
Update deploy_to_uat_env.sh

    • -1
    • +1
    /deployment/uat_env/deploy_to_uat_env.sh
Disable TLS verify

    • -1
    • +1
    /deployment/uat_env/deploy_to_uat_env.sh
Bring back TLS verify

    • -1
    • +1
    /deployment/uat_env/deploy_to_uat_env.sh
OLMIS-6899 Fix validation of PI draft without ID
OLMIS-6899 Fix validation of PI draft without ID
OLMIS-6899 Fix validation of PI draft without ID

OLMIS-6899 Validate physical inventory submit
OLMIS-6899 Validate physical inventory submit
OLMIS-6899 Add changelog entry

OLMIS-6899 Validate the same PI is not sumitted twice

On attempt to submit a PI draft that is already marked as submitted

in the database, a validation error is thrown.

typo?

typo?

Since DefaultAdjustmentReasonValidator, DefaultFreeTextValidator, and DefaultUnpackKitValidator still implement StockEventValidator and exist as bean, won't they get executed twice? First in a for ...

Since DefaultAdjustmentReasonValidator, DefaultFreeTextValidator, and DefaultUnpackKitValidator still implement StockEventValidator and exist as bean, won't they get executed twice? First in a for loop, and then via those above extension point injections (not 100% sure, but I think this is what happens)

I'd even change it to WARN

I'd even change it to WARN

Ultimately we need covid-ui here, but I understand the image is not ready yet

Ultimately we need covid-ui here, but I understand the image is not ready yet

Remove the ftp container

Remove the ftp container

We should be using the stable versions

We should be using the stable versions

Do we need that heavy logging in all of the services?

Do we need that heavy logging in all of the services?

Looks good, but the CHANGELOG is missing. This changes the logic of populating the modified date so it should be explained there

Looks good, but the CHANGELOG is missing. This changes the logic of populating the modified date so it should be explained there