You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implements #780
Removed the canister manifest (which had one canister ID per canister, as well as paths to outputs) and replaced it with two files:
- `.dfx/canister_ids.json`: stores ephemeral canister ids for (typically) local "networks"
- `canister_ids.json`: stores persistent canister ids for (typically) remote networks.
The `dfx create` command populates these files, while other commands use the values.
Added a `NetworkDescriptor` field to `Environment` (though really only `AgentEnvironment`), in order to tell which `canister_ids.json` file to use.
Added to dfx.json `networks` a `type` field ("persistent" or "ephemeral")
Because of 2 competing requirements;
We need to have two ways of containing canister IDs; one that is persisted in version control and one that isn't.
Because of this, we allow people to specify an
type
in theirdfx.json
networks
keys, which is one of two values:ephemeral
, which is the default forlocal
. Thecanister_ids.json
files will be created inside.dfx
.persistent
, which is the default for non-local
networks. Thecanister_ids.json
file in the root will be updated when creating canister IDs.The format for the
canister_ids.json
file is the same regardless of where it is created;where
NETWORK_NAME
can belocal
, ortungsten
or else.The text was updated successfully, but these errors were encountered: