Github user bhaisaab commented on the pull request:

    https://github.com/apache/cloudstack/pull/1489#issuecomment-209018498
  
    ## test_staticroles.py
    
    === TestName: test_static_role_account_acls | Status : SUCCESS ===
    
    ## scripts/util/migrate-dynamicroles.py
    
    I'll add docs for this feature in a separate PR to admin-docs, this is the 
usage information:
    
    Usage: migrate-dynamicroles.py [options]
    
    Options:
      -h, --help            show this help message and exit
      -b DB, --db=DB        The name of the database, default: cloud
      -u USER, --user=USER  User name a MySQL user with privileges on cloud
                            database
      -p PASSWORD, --password=PASSWORD
                            Password of a MySQL user with privileges on cloud
                            database
      -H HOST, --host=HOST  Host or IP of the MySQL server
      -P PORT, --port=PORT  Host or IP of the MySQL server
      -f COMMANDSFILE, --properties-file=COMMANDSFILE
                            The commands.properties file
      -d, --dryrun          Dry run and debug operations this tool will perform
    
    $ sudo ./scripts/util/migrate-dynamicroles.py
    Apache CloudStack Role Permission Migration Tool
    (c) Apache CloudStack Authors and the ASF, under the Apache License, 
Version 2.0
    
    Running this migration tool will remove any default-role rules in 
cloud.role_permissions. Do you want to continue? [y/N]y
    The commands.properties file has been deprecated and moved at: 
/etc/cloudstack/management/commands.properties.deprecated
    Static role permissions from commands.properties have been migrated into 
the db
    Dynamic role based API checker has been enabled!
    
    ## test_dynamicroles.py
    
    === TestName: test_default_role_deletion | Status : SUCCESS ===
    
    === TestName: test_role_account_acls | Status : SUCCESS ===
    
    === TestName: test_role_account_acls_multiple_mgmt_servers | Status : 
SUCCESS ===
    
    === TestName: test_role_inuse_deletion | Status : SUCCESS ===
    
    === TestName: test_role_lifecycle_create | Status : SUCCESS ===
    
    === TestName: test_role_lifecycle_delete | Status : SUCCESS ===
    
    === TestName: test_role_lifecycle_list | Status : SUCCESS ===
    
    === TestName: test_role_lifecycle_update | Status : SUCCESS ===
    
    === TestName: test_role_lifecycle_update_role_inuse | Status : SUCCESS ===
    
    === TestName: test_rolepermission_lifecycle_create | Status : SUCCESS ===
    
    === TestName: test_rolepermission_lifecycle_delete | Status : SUCCESS ===
    
    === TestName: test_rolepermission_lifecycle_list | Status : SUCCESS ===
    
    === TestName: test_rolepermission_lifecycle_update | Status : SUCCESS ===
    
    === TestName: test_rolepermission_lifecycle_update_invalid_rule | Status : 
SUCCESS ===


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to