lockally 0.1.0

data/spec/api/signup_api_spec.rb

@@ -0,0 +1,46 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::SignupApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'SignupApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::SignupApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of SignupApi' do
+    it 'should create an instance of SignupApi' do
+      expect(@api_instance).to be_instance_of(Lockally::SignupApi)
+    end
+  end
+
+  # unit tests for signup
+  # Sign up a new tenant
+  # @param signup_request 
+  # @param [Hash] opts the optional parameters
+  # @return [V1AdminLoginPost200Response]
+  describe 'signup test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/suppressions_api_spec.rb

@@ -0,0 +1,81 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::SuppressionsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'SuppressionsApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::SuppressionsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of SuppressionsApi' do
+    it 'should create an instance of SuppressionsApi' do
+      expect(@api_instance).to be_instance_of(Lockally::SuppressionsApi)
+    end
+  end
+
+  # unit tests for v1_suppressions_email_delete
+  # Remove a suppression
+  # @param email 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'v1_suppressions_email_delete test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_suppressions_email_get
+  # Check whether an address is suppressed
+  # @param email 
+  # @param [Hash] opts the optional parameters
+  # @return [Suppression]
+  describe 'v1_suppressions_email_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_suppressions_get
+  # List suppressed recipients
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :reason 
+  # @option opts [String] :cursor 
+  # @option opts [Integer] :limit 
+  # @return [V1SuppressionsGet200Response]
+  describe 'v1_suppressions_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_suppressions_post
+  # Add a suppression
+  # @param v1_suppressions_post_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Suppression]
+  describe 'v1_suppressions_post test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/templates_api_spec.rb

@@ -0,0 +1,90 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::TemplatesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'TemplatesApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::TemplatesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of TemplatesApi' do
+    it 'should create an instance of TemplatesApi' do
+      expect(@api_instance).to be_instance_of(Lockally::TemplatesApi)
+    end
+  end
+
+  # unit tests for v1_templates_get
+  # List templates
+  # @param [Hash] opts the optional parameters
+  # @return [V1TemplatesGet200Response]
+  describe 'v1_templates_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_templates_id_delete
+  # Delete a template
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'v1_templates_id_delete test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_templates_id_get
+  # Get a template
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @return [Template]
+  describe 'v1_templates_id_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_templates_id_put
+  # Update a template
+  # @param id 
+  # @param template_input 
+  # @param [Hash] opts the optional parameters
+  # @return [Template]
+  describe 'v1_templates_id_put test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_templates_post
+  # Create a template
+  # @param template_input 
+  # @param [Hash] opts the optional parameters
+  # @return [Template]
+  describe 'v1_templates_post test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/tenant_api_spec.rb

@@ -0,0 +1,57 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::TenantApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'TenantApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::TenantApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of TenantApi' do
+    it 'should create an instance of TenantApi' do
+      expect(@api_instance).to be_instance_of(Lockally::TenantApi)
+    end
+  end
+
+  # unit tests for v1_tenant_get
+  # Get the calling tenant
+  # Returns the tenant the presented API key belongs to.
+  # @param [Hash] opts the optional parameters
+  # @return [Tenant]
+  describe 'v1_tenant_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_usage_get
+  # Usage snapshot
+  # Returns the tenant&#39;s current usage + cap consumption. Designed for poll-based alerting on the integrator side (e.g. \&quot;warn when daily quota is 80% used\&quot;). Refreshed live from Postgres — there is no cache, so callers should poll at most once per minute. 
+  # @param [Hash] opts the optional parameters
+  # @return [V1UsageGet200Response]
+  describe 'v1_usage_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/test_api_spec.rb

@@ -0,0 +1,46 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::TestApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'TestApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::TestApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of TestApi' do
+    it 'should create an instance of TestApi' do
+      expect(@api_instance).to be_instance_of(Lockally::TestApi)
+    end
+  end
+
+  # unit tests for v1_test_inbound_post
+  # Simulate an inbound email (test keys only)
+  # Runs a synthetic message through the REAL indexing pipeline — thread adoption, deterministic extraction (incl. injection_risk), and the message.received webhook — so the whole agent loop is testable without a real domain or MTA. Requires an lk_test_* key (create with {\&quot;test\&quot;: true} on POST /v1/api-keys). Body: {mailbox, from, subject, text, in_reply_to?, references?}.
+  # @param [Hash] opts the optional parameters
+  # @return [Object]
+  describe 'v1_test_inbound_post test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/users_api_spec.rb

@@ -0,0 +1,92 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::UsersApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'UsersApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::UsersApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of UsersApi' do
+    it 'should create an instance of UsersApi' do
+      expect(@api_instance).to be_instance_of(Lockally::UsersApi)
+    end
+  end
+
+  # unit tests for create_user
+  # Create a user
+  # @param create_user_request 
+  # @param [Hash] opts the optional parameters
+  # @return [User]
+  describe 'create_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_user
+  # Delete a user
+  # Soft-deletes the user by setting status to deprovisioned.
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'delete_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_user
+  # Get a user
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @return [User]
+  describe 'get_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_users
+  # List users
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @return [ListUsers200Response]
+  describe 'list_users test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_user
+  # Update a user
+  # @param id 
+  # @param update_user_request 
+  # @param [Hash] opts the optional parameters
+  # @return [User]
+  describe 'update_user test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/webhooks_api_spec.rb

@@ -0,0 +1,83 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Lockally::WebhooksApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'WebhooksApi' do
+  before do
+    # run before each test
+    @api_instance = Lockally::WebhooksApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of WebhooksApi' do
+    it 'should create an instance of WebhooksApi' do
+      expect(@api_instance).to be_instance_of(Lockally::WebhooksApi)
+    end
+  end
+
+  # unit tests for v1_webhooks_get
+  # List webhooks
+  # Returns the calling tenant&#39;s webhook subscriptions. Never returns the signing secret — only metadata. 
+  # @param [Hash] opts the optional parameters
+  # @return [V1WebhooksGet200Response]
+  describe 'v1_webhooks_get test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_webhooks_id_delete
+  # Delete a webhook
+  # Hard-delete; cascades to &#x60;webhook_deliveries&#x60; history.
+  # @param id 
+  # @param [Hash] opts the optional parameters
+  # @return [nil]
+  describe 'v1_webhooks_id_delete test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_webhooks_id_patch
+  # Update a webhook
+  # Supply at least one of &#x60;url&#x60;, &#x60;events&#x60;, &#x60;paused&#x60;. Setting &#x60;paused&#x60; to &#x60;false&#x60; ALSO resets &#x60;consecutive_failures&#x60; to 0 — re-arms the 50-failure auto-pause counter. 
+  # @param id 
+  # @param v1_webhooks_id_patch_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Webhook]
+  describe 'v1_webhooks_id_patch test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for v1_webhooks_post
+  # Create a webhook
+  # Subscribes a URL to one or more event types. Returns the &#x60;signing_secret&#x60; ONCE in the response — store it immediately. The dispatcher signs every outbound POST per design L3:      X-Lockally-Signature: t&#x3D;&lt;unix&gt;,v1&#x3D;&lt;hex(hmac_sha256(secret, t + \&quot;.\&quot; + body))&gt;  Verify on your end using HMAC-SHA256 with a 5-minute timestamp window (replay protection). A reference verifier ships in [internal/webhook](https://github.com/ucheigwedinma/lockally/blob/main/internal/webhook/sign.go).  Event names: see the [event catalogue](https://github.com/ucheigwedinma/lockally/blob/main/docs/v1-design.md#64-webhook-event-catalogue-v1). 
+  # @param v1_webhooks_post_request 
+  # @param [Hash] opts the optional parameters
+  # @return [Webhook]
+  describe 'v1_webhooks_post test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/activate_add_on200_response_spec.rb

@@ -0,0 +1,54 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::ActivateAddOn200Response
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::ActivateAddOn200Response do
+  #let(:instance) { Lockally::ActivateAddOn200Response.new }
+
+  describe 'test an instance of ActivateAddOn200Response' do
+    it 'should create an instance of ActivateAddOn200Response' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::ActivateAddOn200Response)
+    end
+  end
+
+  describe 'test attribute "id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "add_on"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "status"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/add_calendar_member_request_spec.rb

@@ -0,0 +1,46 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::AddCalendarMemberRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::AddCalendarMemberRequest do
+  #let(:instance) { Lockally::AddCalendarMemberRequest.new }
+
+  describe 'test an instance of AddCalendarMemberRequest' do
+    it 'should create an instance of AddCalendarMemberRequest' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::AddCalendarMemberRequest)
+    end
+  end
+
+  describe 'test attribute "user_email"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "role"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["viewer", "editor", "owner"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.role = value }.not_to raise_error
+      # end
+    end
+  end
+
+end

data/spec/models/add_contact_list_member_request_spec.rb

@@ -0,0 +1,36 @@
+=begin
+#lockally control plane
+
+#The lockally control plane lets integrators and direct customers manage everything except actual mail data flow (which uses standard JMAP / IMAP / SMTP-submission against the data plane endpoints).  **Authentication.** All `/v1/*` endpoints require a Bearer API key in the `Authorization` header. Keys are formatted `lk_live_<8-char-prefix>_<32-char-secret>`. Generate the first key for a tenant via `cmd/seed`; subsequent keys via `POST /v1/api-keys`.  **Errors.** Failures return [RFC 9457](https://www.rfc-editor.org/rfc/rfc9457) `application/problem+json` documents.  **Scopes.** Each endpoint requires a specific scope on the presented key. Insufficient scope returns `403` with the required scope name in `detail`. 
+
+The version of the OpenAPI document: 0.1.0
+Contact: support@lockally.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.23.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Lockally::AddContactListMemberRequest
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Lockally::AddContactListMemberRequest do
+  #let(:instance) { Lockally::AddContactListMemberRequest.new }
+
+  describe 'test an instance of AddContactListMemberRequest' do
+    it 'should create an instance of AddContactListMemberRequest' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Lockally::AddContactListMemberRequest)
+    end
+  end
+
+  describe 'test attribute "contact_id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end