ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity
community.general/test/integration/targets/azure_rm_hdinsightcluster/aliases

5 lines
144 B
Text
Raw Normal View History

adding hdinsight cluster (#52612) * adding hdinsight cluster again * updated hdinsight cluster test * fixes * updated test * some updates * removed non-essential * fixed sanity * fixed test * newer default_compare implementation * debugging code * try to fix comparison issue * fix test * fixed sanity * fix comparison * added zookeeper node * zookeeper target instance count * don't compare passwords * test updates * next iteration * fix * more fixes * another fix * one more fix * flattening configuration * doc update * one more doc change * fixed sanity * properly handling cluster update * changed default_compare function * fixed comparison * changed compare result * compare stuff * removed some custom stuff * improved hdinsight change warning * fixed syntax * fix another syntax * one more hdinsight cluster update fix * and removed some unnecessary stuff * one more update * forgot one lropoller * reduce number of cores * head node size * still bigger nodes * fix mistake * fix problem * fixed another issue * don't delete unexisting
2019-03-20 23:50:57 +01:00
cloud/azure
destructive
shippable/azure/group1
Mark azure_rm_hdinsightcluster test unstable. The unstable alias wasn't intended for slow but otherwise stable tests. However, the alternatives are to either dedicate an entire test group to this one test or mark it unsupported. Marking it unstable at least permits the test to run when changes are made to the integration test or the module itself, which is better than not running the tests at all.
2019-03-21 06:22:23 +01:00
unstable # test is slow (~30 minute run time), not unstable, but this is better than unsupported
Copy permalink