|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5008 | minor | always | 03-30-12 00:26 | 03-30-12 12:59 | |
|
|
|||||
| Reporter: | rickHigh | Platform: | |||
| Assigned To: | alex | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.28 | ||
|
|
|||||
| Summary: | 0005008: Use license-add to add a license to an un-licensed instance | ||||
| Description: |
$ resinctl license-add --license 1013792.license command 'license-add' is only available with Resin Pro Expectations: I can use license-add to add a license to an un-licensed instance. User Story (as I understand it): Customer downloads Resin Pro. Customer installs Resin Pro on n-number of EC2 or remote instances. Customer buys a license. Customer uses license-add to add the license to said remote instances. Cloud Tutorial Perspective: From a cloud / cluster tutorial perspective, if license-add only works with licensed copies, then I have to figure out a secure reliable way to transmit license files from dev box to EC2 instance. If license-add works with non-licensed Resin, then I can just us license-add to add the license to the remote server and not explain how to setup secure file transfer or use S3 to transmit files. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||