Update migration branch with recent improvements from main branch

how-to/configure-placeos-for-microsoft-365/calendar-access/azure-app-registration.md

@@ -28,14 +28,15 @@ After completion of this step, we will apply a policy restriction so the applica
 10. Click 'Application Permissions'.
 11. Add the following permissions:\
     \- `Calendars.ReadWrite`\
-    \- `Group.Read.All`\
     \- `User.Read.All`\
+    \- `GroupMember.Read.All`\
+    \- `Place.Read.All`\
     ![](https://lh4.googleusercontent.com/XDYxU9SORBoh9sbS-TLeu-RCd0zBGP-4xQjqr7PE2O4a1DQFLj4Az1OXRRVhTPoxLrxjDxrGEd36urvVQIRGmEopr7TAltvIrTsUnewaH8LJumCjrSrYFwb5zTO2FdLkvbqELAYLy8lzZz04Jw)
-12. Click 'Add permissions'.
-13. Click ‘Grant admin consent for xyz’.\
+13. Click 'Add permissions'.
+14. Click ‘Grant admin consent for xyz’.\
     <img src="../../../.gitbook/assets/image (11).png" alt="" data-size="original">
-14. Configuration of the Azure App is now complete.
-15. Supply PlaceOS or your integration partner with (be aware that supplying these credentials to PlaceOS prior to configuring the application policy in exchange will allow PlaceOS to see ALL calendars in your organisation):
+15. Configuration of the Azure App is now complete.
+16. Supply PlaceOS or your integration partner with (be aware that supplying these credentials to PlaceOS prior to configuring the application policy in exchange will allow PlaceOS to see ALL calendars in your organisation):
     * Application ID
     * Tenant ID
     * Secret

how-to/configure-placeos-for-microsoft-365/user-authentication/create-microsoft-azure-app-registration.md

@@ -36,6 +36,7 @@
     * `profile`
 13. Click 'Grant admin consent'
 14. This completes the App Registration.
+15. Securely send the Azure App Registration Tenant ID, Client ID, and Client Secret Value (from steps 5-7) to the PlaceOS Administrator who will be configuring the single-sign-on authentication integration.
 
 {% hint style="success" %}
 For more detailed information about the permissions required by PlaceOS, please reference the [Microsoft Azure Permissions Table.](../../../reference/microsoft-azure-permissions.md)

reference/system-requirements.md

@@ -24,12 +24,12 @@ See [PlaceOS Kubernetes Terraform](https://github.com/place-labs/k8s-terraform/)
 * Availability Zones: 1 or more (3 recommended)
 * Nodes: 3 or more
 * Minimum node size:
-  * 4 cores
-  * 8 GB RAM
+  * 2 cores
+  * 16 GB RAM
 * Persistent Volumes utilized:
-  * 10 x 1 GB
-  * 1x 20GB
-  * 1x 100GB
+  * 7 x 8 GB
+  * 8 x 100 MB
+  * 2 x 50 GB
 
 ### Non-Production Environment
 
@@ -40,12 +40,11 @@ See [PlaceOS Kubernetes Terraform](https://github.com/place-labs/k8s-terraform/)
 * Availability Zones: 1 or more
 * Nodes: 2 or more
 * Minimum node size:
-  * 4 cores
+  * 2 cores
   * 8 GB RAM
 * Persistent Volumes utilized:
-  * 10 x 1 GB
-  * 1x 20GB
-  * 1x 100GB
+  - 3 x 8 GB
+  - 3 x 100 MB
 
 #### OR Linux VM based Deploymentm for development/testing purposes
 

tutorials/backend/write-a-driver/README.md

@@ -17,7 +17,7 @@ From a driver structure standpoint there is no difference between these types.
 * The same driver works over a TCP, UDP or SSH transport
 * All drivers support HTTP methods (except logic modules)
   * for example a websocket driver or tcp driver will also be provided a default HTTP client at the base URI of the websocket and IP address of the tcp driver.
-  * this default client URL can be overwritten, for example where the [HTTP port](https://github.com/PlaceOS/drivers/blob/master/drivers/aver/cam520\_pro.cr#L43-L45) is different to the websocket port\
+  * this default client URL can be overwritten, for example where the [HTTP port](https://github.com/PlaceOS/drivers/blob/master/drivers/aver/cam520_pro.cr#L43-L45) is different to the websocket port\
     `transport.http_uri_override = URI.new`
 * All drivers have access to logic helpers when associated with a System
 
@@ -207,7 +207,9 @@ sys.count("Module") #=> 3
 sys.implementing(PlaceOS::Driver::Interface::Powerable) #=> ["Camera", "Display"]
 
 # Look at status on a remote module
-system[:Display][:power] #=> true
+system[:Display][:power] #=> true (JSON::Any)
+system[:Display].status(Bool, :power) #=> true (Bool)
+system[:Display].status?(Bool, :power) #=> true (Bool | Nil)
 
 # Access a different module index
 system[:Display_2][:power]