tradle / tradleconf Goto Github PK

when I do tradleconf init on the test mycloud, the .env it creates has namespace = "io.https://tradle" instead of "io.tradle"

region="us-east-1"
awsProfile="test"
stackName="tdl-dynamic-plugins-ltd-dev"
stackId="arn:aws:cloudformation:us-east-1:185632214405:stack/tdl-dynamic-plugins-ltd-dev/d6270600-d7ef-11ec-9490-0a460341b8e5"
apiBaseUrl="https://kkilo9hec4.execute-api.us-east-1.amazonaws.com/dev"
namespace="io.https://tradle"

CloudFormation for this mycloud has the correct OrgDomain https://tradle.io

When a MyCloud is disabled, the CLI currently shows errors during all new operations like in #26 because the underlying code can not look up information about a mycloud in the disabled state.

Currently re-enabling is a multi-step manual process that involves going into the AWS console.

To improve this I am thinking of 3 steps to improve the situation:

1. If the cli lambda returns an empty result, we should use a AWS command to see if the lambda in question has been disabled, and if it has: throw an error
2. Find a way to avoid the manual steps when re-enabling a MyCloud
3. If the cli runs into a "mycloud disabled" error, it should offer the user a prompt, asking if they want to re-enable it.

via @spwilko

% tradleconf update -c
Updating! To roll back, run:
tradleconf update-manually --template-url ".../compiled-cloudformation-template.json" --stack-parameters "params-3.1.1-rc.14-1642611680013.json"

· loading release 3.1.1-rc.18, grab a coffee...
TypeError: Cannot read property 'ignore' of undefined
    at Updater.<anonymous> (@tradle/conf/lib/node_modules/@tradle/conf/src/update.ts:211:20)
    at Generator.throw (<anonymous>)
    at rejected (@tradle/conf/lib/node_modules/@tradle/conf/node_modules/tslib/tslib.js:113:69)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)