Deploy DotNet project to Azure Function App dev #5
jem41deploy-dev.yaml
on: workflow_dispatch
build-and-deploy
1m 55s
Annotations
10 warnings
|
build-and-deploy
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L5
Non-nullable property 'defaultRedirectUrl' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L6
Non-nullable property 'customDomain' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L7
Non-nullable property 'UlsDataStorage' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L8
Non-nullable property 'env' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L9
Non-nullable property 'dataDogKey' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/AdminApiSettings.cs#L10
Non-nullable property 'version' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build-and-deploy:
src/lib/NLogWrapper.cs#L19
Non-nullable field 'logger' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
build-and-deploy:
src/lib/NLogWrapper.cs#L19
Non-nullable field 'serviceName' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
|
build-and-deploy:
src/lib/NLogWrapper.cs#L19
Non-nullable field 'shortenerSettings' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|