SomeoneWeird ( Adam Brady )

import ht from 'hudson-taylor'

let transport = new ht.Transports.Local()
let service = new ht.Service(transport)
let client = new ht.Client({
  account: transport
})

service.on('getRandomAccount', function (data, callback) {
  return callback(null, {
    id: 4,
    name: 'you'
  })
})

let newClient = ht.proxy(client)

newClient.account.getRandomAccount(function (err, data) {
  ...
})

oooo yeaaa

+24 -0

1 commit in hudson-taylor/hudson-taylor/tree/proxy-client hudson-taylor/hudson-taylor/tree/master

4 comments

2 changed files

SomeoneWeird

pr closed time in 2 months

delete branch hudson-taylor/ht-express

delete branch : requested-bits

delete time in 2 months

PR closed hudson-taylor/ht-express

Allow pulling data directly off req enhancement help wanted

+23 -5

1 commit in hudson-taylor/ht-express/tree/requested-bits hudson-taylor/ht-express/tree/master

0 comment

1 changed file

SomeoneWeird

pr closed time in 2 months

delete branch SomeoneWeird/cirrus

delete branch : ignore-json-comments

delete time in 2 months

PR closed SomeoneWeird/cirrus

Strip JSON comments from template + parameter file enhancement

+6 -2

1 commit in SomeoneWeird/cirrus/tree/ignore-json-comments SomeoneWeird/cirrus/tree/master

0 comment

3 changed files

SomeoneWeird

pr closed time in 2 months

startedloft-sh/vcluster

started time in 2 months

delete branch SomeoneWeird/dota-stats

delete branch : next-matches-page

delete time in 2 months

PR closed Curia/dota-stats

Example for separating pages

+347 -23

1 commit in SomeoneWeird/dota-stats/tree/next-matches-page Curia/dota-stats/tree/main

0 comment

4 changed files

SomeoneWeird

pr closed time in 2 months

startedalexellis/k3sup

started time in 2 months

startedianstormtaylor/superstruct

started time in 2 months

delete branch SomeoneWeird/opentelemetry.io

delete branch : patch-1

delete time in 2 months

issue openedaws/aws-cdk

aws-eks: Reusable Kubectl Provider for imported clusters

It would be great if we could define reusable a Kubectl Provider for imported clusters with eks.Cluster.fromClusterAttributes.

Use Case

Currently when a cluster is referred to for the first time in a stack it deploys a new NestedStack that contains a single lambda. For accounts with a large number of stacks this can be a problem when getting close to the service limit of 200 stacks per account.

Proposed Solution

Being able to deploy a single provider for a cluster manually, and then do something like

eks.Cluster.fromClusterAttributes({
   ...
   provider: eks.Provider.fromExisting({ ... })
})

Another potentially solution is to change the KubectlProvider from being a NestedStack to being a Construct.

Other

There is already a getOrCreate function that calls _attachKubectlResourceScope, but this would only work for an existing eks.Cluster instance, not one being created using fromClusterAttributes

[x] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

created time in 2 months

startedAsahiLinux/m1n1

started time in 3 months