Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Sure, I'm still working on that.

Sure, I'm still working on that.

Please add this to template service: https://github.com/OpenLMIS/openlmis-template-service/blob/master/build.gradle#L146
Unfortunately, it does so I reverted the changes and updated task for generating new migration.

Unfortunately, it does so I reverted the changes and updated task for generating new migration.

Revert "Added info about editing migrations"

This reverts commit 451575575e445e620a66661eabe46776ab550d97.

    • -4
    • +0
    ./migration/20170214123504310__initial_schema.sql
    • -4
    • +0
    ./migration/20170214123932959__initial_bootstrap_data.sql
    • -4
    • +0
    ./migration/20170404125519633__alter_auth_users_email_nullable.sql
    • -4
    • +0
    ./migration/20170627082106947__removed_initial_clients_resourceids.sql
    • -4
    • +0
    ./migration/20170711211208618__index_username_of_auth_users.sql
    • -4
    • +0
    ./migration/20170724084322325__remove_auth_role_from_user.sql
    • -4
    • +0
    ./migration/20171215105642158__added_api_keys.sql
    • -4
    • +0
    ./migration/20171219124429037__unique_username_ignore_case.sql
    • -4
    • +0
    ./migration/20180320172415321__connect_api_keys_with_client.sql
    • -4
    • +0
    ./migration/20180613120215847__remove_referencedatauserid_from_user.sql
Hopefully comments do not modify the checksum, but yes - worth checking

Hopefully comments do not modify the checksum, but yes - worth checking

From what I know if a migration that has been applied to a database and it was changed the flyway will throw an exception (about incorrect code or something like that). Could we verify that those c...

From what I know if a migration that has been applied to a database and it was changed the flyway will throw an exception (about incorrect code or something like that). Could we verify that those comments will not break anything?

Added info about editing migrations
Added info about editing migrations
Added info about editing migrations

    • -0
    • +4
    ./migration/20170214123504310__initial_schema.sql
    • -0
    • +4
    ./migration/20170214123932959__initial_bootstrap_data.sql
    • -0
    • +4
    ./migration/20170404125519633__alter_auth_users_email_nullable.sql
    • -0
    • +4
    ./migration/20170627082106947__removed_initial_clients_resourceids.sql
    • -0
    • +4
    ./migration/20170711211208618__index_username_of_auth_users.sql
    • -0
    • +4
    ./migration/20170724084322325__remove_auth_role_from_user.sql
    • -0
    • +4
    ./migration/20171215105642158__added_api_keys.sql
    • -0
    • +4
    ./migration/20171219124429037__unique_username_ignore_case.sql
    • -0
    • +4
    ./migration/20180320172415321__connect_api_keys_with_client.sql
    • -0
    • +4
    ./migration/20180613120215847__remove_referencedatauserid_from_user.sql
OLMIS-5501: Changed usernames

OLMIS-5649 Adding superset client to OpenLMIS

This will be used as the demo application. Also, reverting the change made by Chongsun on the tableau-wdc row to return it to implicit grant type.

    • -1
    • +2
    ./demo-data/auth.oauth_client_details.csv
I'm envisioning this user will show the requisition workflow after a requisition has split, the smaller CHAZ requisition. Hopefully the role assignments are set up with the supervisory node that way.

I'm envisioning this user will show the requisition workflow after a requisition has split, the smaller CHAZ requisition. Hopefully the role assignments are set up with the supervisory node that way.

This user will be used to present split feature. He has all roles/rights required to go through requisition workflow.

This user will be used to present split feature. He has all roles/rights required to go through requisition workflow.

I also updated readme in the reference data service: https://review.openlmis.org/cru/FEOLMIS-3418

I also updated readme in the reference data service: https://review.openlmis.org/cru/FEOLMIS-3418

OLMIS-5622: Added chaz user
OLMIS-5622: Added chaz user
OLMIS-5622: Added chaz user

OLMIS-5634 Change tableau demo data client authorized grant type

From implicit to authorization code. It's more secure than implicit https://oauth.net/2/grant-types/implicit/.

    • -1
    • +1
    ./demo-data/auth.oauth_client_details.csv
Revert "OLMIS-5382: Register the new hapifhir service in Auth."

This reverts commit d0e4126. According to the following documentation, a custom registration of services is not required.

https://openlmis.atlassian.net/wiki/spaces/OP/pages/113520403/Make+Auth+dynamically+retrieve+list+of+registered+OpenLMIS+services

    • -1
    • +0
    ./migration/20180921160044203__add_hapifhir_resourceid.sql
  1. … 1 more file in changeset.
OLMIS-5382: Register the new hapifhir service in Auth.

    • -0
    • +1
    ./migration/20180921160044203__add_hapifhir_resourceid.sql
  1. … 1 more file in changeset.
Added demo data for perf users
Added demo data for perf users
Added demo data for perf users

    • -1
    • +1001
    ./demo-data/auth.auth_users.csv
Add back demo data info about user's passwords to README

This was removed from demo-data's README, but should have been moved.