Max Kaplan

Deprecating this makes me a bit sad... The existing BCS interface is still pretty raw and rough; is there a world where instead we add an endpoint to the node...

I see this only seems to support one file for the source- how would a multifile source work?

Just a thought; it could signal security to rotate to 0x to guarantee the original module author can’t touch the account contents

I think you could split the string with regex to pull out already colored parts, and then colorize each of those. Will try to pr if I have time, no...

@jsm Actually, something like this: ``` require 'colorize' def colorize_nicely(str, color={color: :red, background: :green}) k = '' r = /(\033\[[\d;]+m.*?\033\[[\d;]+m\s+?)/m z = str.split(r).reject { |s| !s || (k

bump- wanted to see how it looked but could not

Yes, yes it is :-) we are already ready with crowdin, and we’ll be able to get to this in the next few months! White papers are a bit harder...

can you tell me what the actual value the indexer got was perchance?

Is it still happening with latest main, after u64 changes? I will also try to debug with versions you provided

This is also critical for our use case as well :-) Would it simplify anything to make the `node_pool` optional, and require there to be an associated `digitalocean_kubernetes_node_pool` resource?