Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate license experience for first-time users #521

Open
DavidBoike opened this issue Sep 14, 2022 · 0 comments
Open

Evaluate license experience for first-time users #521

DavidBoike opened this issue Sep 14, 2022 · 0 comments

Comments

@DavidBoike
Copy link
Member

DavidBoike commented Sep 14, 2022

Presumably, at startup time an NServiceBus Functions endpoint would be unable to write trial-related information to the local file system, which would interrupt the intended developer experience for a new user. Likely, a Functions endpoint has to define its license or it will encounter the same error that occurs with AWS Lambda:

NServiceBus.Features.LicenseReminder. Fatal. Failed to initialize the license. Exception: System.IO.IOException: Read-only file system at System.IO.FileSystem.CreateDirectory(String fullPath) at System.IO.Directory.CreateDirectory(String path) at Particular.Licensing.TrialStartDateStore.GetTrialStartDate() at Particular.Licensing.ActiveLicense.Find(String applicationName, LicenseSource[] licenseSources) at NServiceBus.LicenseManager.InitializeLicense(String licenseText, String licenseFilePath) at NServiceBus.Features.LicenseReminder.Setup(FeatureConfigurationContext context)

The pain may be more acute with Lambda, because Functions contains more robust local development tooling, but the experience should still be evaluated, perhaps in concert with Particular/NServiceBus.AwsLambda.Sqs#51. It may well be that nothing needs to be done for the Azure Functions experience, or that the fix for Lambda would fix Functions as well, but at present, this has not been evaluated.

This may also be an issue for NServiceBus.AzureFunctions.Worker.ServiceBus but I suspect the experience is similar enough that the same conclusions would hold for both packages, so I did not raise a similar issue in that repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant