Skip to content

Releases: fnproject/fn_go

Support OCI v2 IMDS Endpoint

24 Jan 19:12
e8ddcd5
Compare
Choose a tag to compare

This release supports OCI v2 IMDS endpoint

Adding support for multiarch and arm based functions

21 Jun 08:23
a556df1
Compare
Choose a tag to compare

Now Applications can be created with a particular shape (GENERIC_X86, GENERIC_ARM and GENERIC_X86_ARM) this repo contains necessary interfaces and other change required by FnCLI (cli) to talk to oci-sdk.

Allowing functions with empty image and digest for pbf based functions

15 Mar 11:20
ac5542c
Compare
Choose a tag to compare

This change would allow fn inspect functions and fn list functions for PBF(Pre-Built Functions) function with empty image and digest field. By default, it was not supported.

Non-root compartment image support for cloudshell and IP

05 Apr 08:54
5c2cbfd
Compare
Choose a tag to compare
Merge pull request #49 from fnproject/image-comp-cloudshell

Add non-root compartment image support to cloud shell and ip

OracleProviders: add ImageCompartmentID support

13 Jan 16:00
d8b70e0
Compare
Choose a tag to compare

Add ImageCompartmentID to the OracleProvider, ImageCompartmentID will default to empty string "" if not defined.

Oracle providers: Upgrade OCI SDK to v48.0.0

01 Oct 17:11
b3de5b2
Compare
Choose a tag to compare

Upgrade OCI SDK to v48.0.0 to keep it current. In addition to this, OCI ConfigurationProvider is exposed by OracleProvider.

Oracle providers: fix bug when setting disable-certs to true

04 Mar 16:08
Compare
Choose a tag to compare

Ensure http client Transport is defined before trying to set InsecureSkipVerify

The HTTP client provided by oci-go-sdk doesn't explicitly specify the Transport, such that DefaultTransport is used when the client is used. This was causing an issue when the disable-certs flag is true, as we were trying to modify the Transport to set TLSClientConfig.InsecureSkipVerify, causing a panic as DefaultTransport had yet to be set.

Oracle providers: handle case where REGION is not present in OCI config

24 Feb 15:31
Compare
Choose a tag to compare
OCI shim: handle case where REGION is not present in OCI config

There was an issue with the new 'OCI shim' provider code, whereby, despite api-url being set in the Fn context, we still required REGION to be set in the OCI config. This is incorrect behaviour as we should require only api-url. However, OCI SDK client construction requires a non-blank region in the config provider, despite the fact that we override endpoint with api-url, so we have to work around that here.

Oracle providers: fix blank digest behaviour in OCI shim

09 Dec 16:45
Compare
Choose a tag to compare
OCI shim: fix blank digest behaviour

In order to replicate the behaviour of the OSS endpoints, we don't set digest in the body if a blank string is passed

Oracle providers: use OCI API

08 Dec 11:54
6f853b4
Compare
Choose a tag to compare
Use OCI API for Oracle providers (#42)

* Bump go-swagger to 0.25.0 and regenerate client

This results in the removal of some old concepts such as 'calls' and 'logs' (which I think are long disused and date from the v1 days?)

* Revendor latest versions of dependencies

* First pass at Apps shim

* Add tests for Apps shim

Mock out OCI SDK backend for this

* Change Oracle user provider to use OCI shim

Apps only for now. This respects the existing config precedence of env vars > Fn CLI context > OCI config file

* Bump to Go 1.14

* Don't export appsShim struct

* First pass at Fns shim

* Add tests for Fns shim

* Add Triggers shim

These are just stubbed out as Oracle Functions doesn't support Triggers

* Re-add 'Signer' to user provider

This is used by the invoke code in Fn CLI, so it's required. Fortunately, we can simply extract the key information from the OCI config provider we've constructed.

* Switch Oracle IP provider to use OCI API shim

Also, allow user provider to derive API endpoint entirely from OCI config

* Switch Oracle CS provider to use OCI shim

* Respect disableCerts in OCI shim

* Cleanup

* Don't pass nil contexts to OCI client

* Add basic useragent prefix

* Final cleanup