> +import org.jclouds.scriptbuilder.domain.StatementList;
> +import org.jclouds.scriptbuilder.statements.ssh.InstallRSAPrivateKey;
> +import org.jclouds.ssh.SshKeys;
> +import org.testng.annotations.Test;
> +
> +import java.util.Map;
> +
> +import static org.testng.Assert.assertEquals;
> +import static org.testng.Assert.assertNull;
> +import static org.testng.Assert.assertTrue;
> +
> +/**
> + * Unit tests for the {@link TemplateOptionsToStatementWithoutPublicKey}
> class.
> + */
> +@Test(groups = "unit", testName =
> "TemplateOptionsToStatementWithoutPublicKeyTest")
> +public class TemplateOptionsToStatementWithoutPublicKeyTest {
I don't get your comment. The tested class just extends the jclouds one to
avoid adding an SSH script to upload the public key. Instead of that,
CloudSigma provides its own mechanism in the API to make the key populated, so
there is no need to generate a statement that manually uploads it.
This test class just tests that the generated options don't contain the upload
key statement when the "authorizePublicKey" option is used.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/70/files#r18021450
