Whirr
  1. Whirr
  2. WHIRR-569

create a default set of keys for itests so that we can login into instances when itests fail

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 0.9.0
    • Component/s: core
    • Labels:
      None

      Description

      as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.

      As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.

        Issue Links

          Activity

          Tom White made changes -
          Fix Version/s 0.9.0 [ 12319840 ]
          Fix Version/s 0.8.1 [ 12322955 ]
          Tom White made changes -
          Fix Version/s 0.8.1 [ 12322955 ]
          Fix Version/s 0.8.0 [ 12321649 ]
          Andrei Savu made changes -
          Fix Version/s 0.8.0 [ 12321649 ]
          Fix Version/s 0.8.0-alpha.1 [ 12318880 ]
          Tom White made changes -
          Link This issue is related to WHIRR-152 [ WHIRR-152 ]
          David Alves made changes -
          Summary use a default set of keys for itests (kept in /resources) so that we can login into instances when itests fail create a default set of keys for itests so that we can login into instances when itests fail
          Description as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
          While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
          as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.

          As per Andrei's suggestion while we should't make the itests depend on a user's keys we could make Cluster.withTemporaryKeys() generate the keypair @ ~/.whirr if not present already (and reuse if present), thus keeping the process secure but allowing users to use the itest keys to log into instances.
          David Alves made changes -
          Field Original Value New Value
          Description as discussed right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
          While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
          as discussed in IRC right now when an itest fails we need to edit .properties rerun without temporary keys to be able to login into the boxes, which is less than ideal.
          While we should't make the itests depend on a user's keys we could include a set of test keys in the source tree (e.g. /resources) that we use for the purpose of (i)testing.
          David Alves created issue -

            People

            • Assignee:
              David Alves
              Reporter:
              David Alves
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development