You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the semi-productionisation of the Rquest Bridge demo environment, some desirable tidy up of the lkightweight Controller layer has come to light.
This issue represents that work:
Tasks
Rename DummyControllerApi to HutchController
Project, solution etc.
Dockerfile
build/deploy workflows
appsettings
namespaces
assemblyname / root namespace
...?
tidy default / dev appsettings
Modern web startup
add CLI
CLI, web, EF entrypoints
Add /version endpoint
Remove https redirect stuff as this is an api only and should be configured directly by binding only? or should we redirect swagger from http?
external logging
seq? elk?
Acceptance Criteria
Program.cs is lightweight and simply:
inits CLI
bypasses CLI and runs webapp if no args are present
supports EF bootstrapping
base CLI entrypoint and helpers are present
/version web endpoint reports assembly informational version
Dependency Injection Service configuration is separated from Application Pipeline configuration
HutchController builds and deploys successfully using that name
assembly name should be kebab-case
namespaces should be nested under Hutch to match the agent
Https redirection should not be attempted (except for swagger? TBC)
Optionally can log to an external service
The text was updated successfully, but these errors were encountered:
Summary
Following the semi-productionisation of the Rquest Bridge demo environment, some desirable tidy up of the lkightweight Controller layer has come to light.
This issue represents that work:
Tasks
DummyControllerApi
toHutchController
Acceptance Criteria
Program.cs
is lightweight and simply:/version
web endpoint reports assembly informational versionThe text was updated successfully, but these errors were encountered: