Skip to content

Lagoon init/pull/push improvements #11

@pirog

Description

@pirog

We're feature complete on Lagoon init/pull/push but there are a few areas we could and should improve:

  1. On init/pull/push when you see a list of "authorizations" to use this is expressed as emails but it should also probably include the lagoon instance url. We also should probably remove "duplicates" eg only show the latest authorization for a given email/lagoon combination.
  2. We do a lot of unneeded calls to the Lagoon API because we are creating multiple instances of the Lagoon API client. We should share a single client instance so that we do not need to make unneeded calls. Eg calling api.auth should just return this.token if its set instead of authing again. Ditto for api.getProjects. NOTE: @mikemilano had it this way originally but @pirog removed it for expediency and because his brain was hurting.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions