urbit/pkg/arvo/ted/gcp/is-configured.hoon

::  Tells whether GCP Storage appears to be configured.
::
::  Thread since it needs to be called from Landscape.
::
::
/-  gcp, spider, settings
/+  strandio
=,  strand=strand:spider
^-  thread:spider
|^
|=  *
=/  m  (strand ,vase)
^-  form:m
;<  has=?  bind:m
  %:  has-settings
    %client-email
    %private-key
    %private-key-id
    %token-uri
    ~
  ==
%-  pure:m
!>
^-  json
b+has
::
++  has-settings
  |=  set=(list @tas)
  =/  m  (strand ?)
  ^-  form:m
  ?~  set
    (pure:m %.y)
  ;<  has=?  bind:m  (has-setting i.set)
  ?.  has
    (pure:m %.n)
  ;<  has=?  bind:m  (has-settings t.set)
  (pure:m has)
::
++  has-setting
  |=  key=@tas
  =/  m  (strand ?)
  ^-  form:m
  ;<  has=?  bind:m
    %+  scry:strandio  ?
    /gx/settings-store/has-entry/gcp-store/[key]/noun
  (pure:m has)
::
--
interface, gcp: don't spam the console with 500s Options here were: make the get-token thread try to return a unit, or write a different thread to check whether GCP Storage seemed to be configured and poll on that thread, or move the whole thing into a Gall app. The compromise between time-to-implement and overall cleanliness seemed to be to write a different thread that just checks whether the settings fields have been poked. Unfortunately this means GcpManager is now a somewhat hefty JavaScript state machine. Took out the logic to check whether S3 was configured in GcpManager, since it was really only there to prevent spamming the console with 500s. If you have both S3 and GCP Storage configured for some reason, you will now use GCP per the logic in useStorage. 2021-02-27 02:42:57 +03:00			`:: Tells whether GCP Storage appears to be configured.`
			`::`
			`:: Thread since it needs to be called from Landscape.`
			`::`
			`::`
			`/- gcp, spider, settings`
			`/+ strandio`
			`=, strand=strand:spider`
			`^- thread:spider`
			`\|^`
			`\|= *`
			`=/ m (strand ,vase)`
			`^- form:m`
			`;< has=? bind:m`
			`%: has-settings`
			`%client-email`
			`%private-key`
			`%private-key-id`
			`%token-uri`
			`~`
			`==`
			`%- pure:m`
			`!>`
gcp: isConfigured doesn't touch store Makes the thread return a simple boolean; almost as simple as just returning %.y or %.n. gcpManager now stores whether GCP is configured as a private variable. Also fixes some type errors in gcp. 2021-04-06 21:59:23 +03:00			`^- json`
interface, gcp: don't spam the console with 500s Options here were: make the get-token thread try to return a unit, or write a different thread to check whether GCP Storage seemed to be configured and poll on that thread, or move the whole thing into a Gall app. The compromise between time-to-implement and overall cleanliness seemed to be to write a different thread that just checks whether the settings fields have been poked. Unfortunately this means GcpManager is now a somewhat hefty JavaScript state machine. Took out the logic to check whether S3 was configured in GcpManager, since it was really only there to prevent spamming the console with 500s. If you have both S3 and GCP Storage configured for some reason, you will now use GCP per the logic in useStorage. 2021-02-27 02:42:57 +03:00			`b+has`
			`::`
			`++ has-settings`
			`\|= set=(list @tas)`
			`=/ m (strand ?)`
			`^- form:m`
			`?~ set`
			`(pure:m %.y)`
			`;< has=? bind:m (has-setting i.set)`
			`?. has`
			`(pure:m %.n)`
			`;< has=? bind:m (has-settings t.set)`
			`(pure:m has)`
			`::`
			`++ has-setting`
			`\|= key=@tas`
			`=/ m (strand ?)`
			`^- form:m`
			`;< has=? bind:m`
			`%+ scry:strandio ?`
			`/gx/settings-store/has-entry/gcp-store/[key]/noun`
			`(pure:m has)`
			`::`
			`--`