fnproject / fn_go Goto Github PK

Here’s the thing, in OSS helm charts I have a zero chance to get a service IP (DNS name) address before API pod provisioning (or am I missing something?). So, in docs, I say that you’ll get fake DNS stub if you want to make your functions accessible - use this DNS name in your host resolve (/etc/hosts, etc.). I do think that this type of behaviour will bring a certain level of problems to people who use OSS helm charts.

However, is there any change that we can make CLI be capable to work with Fn API and FN LB at the same time? Let’s say extend the context, so, that will have an additional endpoint (runner-url for instance, that would be the same/defaulted to api-url when CLI talks to Fn that runs as full node).

In Oracle provider, we have this thing called call_url (https://github.com/fnproject/fn_go/blob/master/provider/oracle/oracle_provider.go#L43). Would be nice to have the same thing in default context since we're moving OSS helm charts towards distributed Fn.

Oracle provider suppose to be the extended version of OCI SDK ConfigurationProvider.

Why?

Oracle provider re-implements most of the code from OCI ConfigurationProvider.
This particular config provider only needs:

• compartment-id
• FnApiUrl
• FnCallUrl
  etc.

In an OCI CloudShell environment, the ~/.oci/config file is found at /etc/oci/config, reference by the env var OCI_CONFIG_PATH. The Oracle provider should understand this if it is set instead of always looking at the default home directory path.

Currently the a context in the Fn CLI requires a "api-url" property. It should not be necessary for the user to know or specify this - the CLI should let this lib derive the api-url from the a known URL pattern and the region property in the selected OCIR profile (specified by "oracle.profile" in an Fn context).

It should still be possible however for an Fn CLI user to explicitly configure api-url in a context if desired to override, just not be needed by default.