Updated releaseNotes for version 3.4.0

Author: JonPSmith

AuthPermissions.AspNetCore/CreateNuGetRelease.nuspec

@@ -8,14 +8,13 @@
     <copyright>Copyright (c) 2021 Jon P Smith</copyright>
     <description>Provides extra authorization and multi-tenant features to a ASP.NET Core application.</description>
     <releaseNotes>
-- New feature: Stop users linked to a tenant from accessing the the tenant while its being changed - see Example4 and Example6
+- BREAKING CHANGE (small): Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
 - New feature: Take the application "down for maintenance", which diverts users to a "please wait" page - see Example4 and Example6
 - New feature: Code for minimal API's fluent HasPermission - see pull request #51. (thanks to @idan-h)
+- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The name of the sharding file can have an EnvironmentName, e.g. "shardingsettings.Production.json"
 - Improved feature: The RefreshUsersClaims classes have been moved to SupportCode project and a few classes have been renamed
 - Improved feature: Sharding now has distributed lock on changes to the shardingsettings.json file
-- Improved feature: Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
-- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The AuthUserAdmin method QueryAuthUsers now takes an optional DatabaseInfoName to allow tenant admin users on sharding
 - Bug Fix: The ReadShardingSettingsFile now return the default sharding DatabaseInformation if no sharding file is found
 - Updated NuGets: There was a security alert on one of the NuGets. All the NuGets have been updated to the latest

AuthPermissions.AspNetCore/MultiProjPack.xml

@@ -10,14 +10,13 @@
     <copyright>Copyright (c) 2021 Jon P Smith</copyright>
     <description>Provides extra authorization and multi-tenant features to a ASP.NET Core application.</description>
     <releaseNotes>
-- New feature: Stop users linked to a tenant from accessing the the tenant while its being changed - see Example4 and Example6
+- BREAKING CHANGE (small): Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
 - New feature: Take the application "down for maintenance", which diverts users to a "please wait" page - see Example4 and Example6
 - New feature: Code for minimal API's fluent HasPermission - see pull request #51. (thanks to @idan-h)
+- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The name of the sharding file can have an EnvironmentName, e.g. "shardingsettings.Production.json"
 - Improved feature: The RefreshUsersClaims classes have been moved to SupportCode project and a few classes have been renamed
 - Improved feature: Sharding now has distributed lock on changes to the shardingsettings.json file
-- Improved feature: Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
-- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The AuthUserAdmin method QueryAuthUsers now takes an optional DatabaseInfoName to allow tenant admin users on sharding
 - Bug Fix: The ReadShardingSettingsFile now return the default sharding DatabaseInformation if no sharding file is found
 - Updated NuGets: There was a security alert on one of the NuGets. All the NuGets have been updated to the latest

AuthPermissions.SupportCode/DownStatusCode/SetRemoveStatus.cs

@@ -119,6 +119,7 @@ public async Task<Func<Task>> SetTenantDownWithDelayAsync(TenantDownVersions dow
         return () =>  RemoveTenantDownAsync(downType, mainKey, secondaryKey);
     }
 
+    //Not used, but kept in case it might be useful 
     ///// <summary>
     ///// This removes the cache entry that was "downing" the tenant
     ///// </summary>

Example6.MvcWebApp.Sharding/Controllers/TenantController.cs

@@ -112,7 +112,10 @@ public async Task<IActionResult> Delete(int id)
         [HasPermission(Example6Permissions.TenantDelete)]
         public async Task<IActionResult> Delete(ShardingSingleLevelTenantDto input)
         {
+            var removeDownAsync = await _upDownService.SetTenantDownWithDelayAsync(TenantDownVersions.Deleted, input.TenantId);
             var status = await _authTenantAdmin.DeleteTenantAsync(input.TenantId);
+            if (status.HasErrors)
+                await removeDownAsync();
 
             return status.HasErrors
                 ? RedirectToAction(nameof(ErrorDisplay),

ReleaseNotes.md

@@ -6,14 +6,13 @@
 
 ## 3.4.0
 
-- New feature: Stop users linked to a tenant from accessing the the tenant while its being changed - see Example4 and Example6
+- BREAKING CHANGE (small): Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
 - New feature: Take the application "down for maintenance", which diverts users to a "please wait" page - see Example4 and Example6
 - New feature: Code for minimal API's fluent HasPermission - see pull request #51. (thanks to @idan-h)
+- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The name of the sharding file can have an EnvironmentName, e.g. "shardingsettings.Production.json"
 - Improved feature: The RefreshUsersClaims classes have been moved to SupportCode project and a few classes have been renamed
 - Improved feature: Sharding now has distributed lock on changes to the shardingsettings.json file
-- Improved feature: Refresh users claims now uses Net.DistributedFileStoreCache - see Example4
-- Improved feature: Added timeout on user invitation - see Example 3 and 5 (inspired by @idan-h)
 - Improved feature: The AuthUserAdmin method QueryAuthUsers now takes an optional DatabaseInfoName to allow tenant admin users on sharding
 - Bug Fix: The ReadShardingSettingsFile now return the default sharding DatabaseInformation if no sharding file is found
 - Updated NuGets: There was a security alert on one of the NuGets. All the NuGets have been updated to the latest