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
refactor!: Make default Apify storages use alias mechanism (#606)
### Description
- Using unnamed Apify-based storage locally outside of the Apify
platform will use the alias mechanism.
### Issues
Closes: #599
### Testing
Added unit tests
Copy file name to clipboardExpand all lines: docs/04_upgrading/upgrading_to_v3.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,3 +101,21 @@ async def main():
101
101
storage_client=custom_storage_client,
102
102
)
103
103
```
104
+
105
+
## Removed Actor.config property
106
+
-`Actor.config` property has been removed. Use `Actor.configuration` instead.
107
+
108
+
## Default storage ids in configuration changed to None
109
+
-`Configuration.default_key_value_store_id` changed from `'default'` to `None`.
110
+
-`Configuration.default_dataset_id` changed from `'default'` to `None`.
111
+
-`Configuration.default_request_queue_id` changed from `'default'` to `None`.
112
+
113
+
Previously using the default storage without specifying its `id` in `Configuration` would lead to using specific storage with id `'default'`. Now it will use newly created unnamed storage with `'id'` assigned by the Apify platform, consecutive calls to get the default storage will return the same storage.
0 commit comments