Skip to content

review backend dependencies #1113

Description

@tormath1

Similar to frontend, let's take a moment to seat and review the backend dependencies. I've seen quite a lot of non-standard dependencies, used for one thing, that could be easily removed or implemented on the Nebraska side.

E.g: https://pkg.go.dev/github.com/labstack/gommon/log ("WORK IN PROGRESS")

$ go mod why github.com/labstack/gommon/log
# github.com/labstack/gommon/log
github.com/kinvolk/nebraska/backend/cmd/nebraska
github.com/labstack/gommon/log

This is for security and maintenance concerns.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendIssues related to the backenddependenciesPull requests that update a dependency filegoPull requests that update Go code

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions