DevOps - Update Colossus deployment for Giza #2829
Conversation
| }, | ||
| }) | ||
| const remoteKeyFilePath = '/joystream/key-file.json' | ||
| additionalParams = ['--key-file', remoteKeyFilePath] |
There was a problem hiding this comment.
keyfile is required above but additionalParams are not used, since we are passing ACCOUNT_URI.
So we need better handling I think here of keyFile, passphrase, and accountUri configs, especially if both are set, which one takes precedence (based on storage-node implementation of course)
There was a problem hiding this comment.
So according to the method getAccount in storage-node-v2/src/command-base/ApiCommandBase.ts if accountURI is specified it takes precedence and overrides password and keyFile flags.
Also either Keyfile or accountURI must be set otherwise we throw an error.
Will update this in the code.
ahhda
force-pushed
the
colossus_pulumi
branch
from
811ff24
to
e395c5f
Compare
| 'server', | ||
| '--worker', | ||
| workerId, | ||
| '--port=3333', |
There was a problem hiding this comment.
Shouldn't this be the the pulumi configuration parameter 'colossusPort' instead of hard-coded 3333?
| value: `${colossusPort}`, | ||
| }, | ||
| { | ||
| name: 'QUERY_NODE_HOST', |
There was a problem hiding this comment.
this has now changed to QUERY_NODE_ENDPOINT and is a full Url not just the host-name
queryNodeHost,workerId,accountURI,colossusImageconfigMaptopulumi-commonManual testing
Running stack with these configurations
The node runs without any issues
