-
Notifications
You must be signed in to change notification settings - Fork 110
Conversation
You can use the `+dfx canister set-controller+` command to specify a user or canister as the controlling identity for a specific canister. | ||
|
||
For example, you might create a new identity called `+pubsadmin+` then run the `+dfx canister set-controller+` to specify that you want the `+pubsadmin+` identity to be the controller of the `+my_wallet+` canister by running the following commands: | ||
|
||
.... | ||
dfx identity new pubsadmin | ||
dfx canister set-controller my_wallet pubsadmin | ||
.... | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the discussion we had in the architecture meeting, you would not need to do set controller on the wallet canister. The get-principal command will be sent to the Onboarding team and they will set the controller to the user provided principal.
Therefore, this example should change to just show setting the controller of a normal hello canister or similar
|
||
Use the `+dfx canister set-controller+` command to specify the identity name or principal to use as the new **controller** for a specified canister on the Internet Computer network. | ||
A controller identity has special rights to manage the canister it controls. | ||
For example, only a controlling identity can be used to upgrade or transfer cycles to the canister under its control. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is true but you can also specify a custodian
in the wallet canister so multiple identities can transfer cycles to it. Therefore, I would just remove this and just specify that only the controller may install, reinstall, upgrade etc.
Overview
Add CLI reference for new subcommand