mirror of https://github.com/knative/func.git
e918f74b9e
* feat!: rename 'emit' to 'invoke' and default to local This commit renames 'func emit' command to 'func invoke' and makes the default behavior to send an event to localhost. The special '--sink' value 'local' is changed to 'cluster' to indicate that the function should be invoked on the cluster instead of locally. All other behavior has remained the same. BREAKING CHANGE Signed-off-by: Lance Ball <lball@redhat.com> * fixup: update commands.md doc Signed-off-by: Lance Ball <lball@redhat.com> * squash: change Emitter interface to Invoker Changes Emit() to Send() in the (now named) Invoker interface, and changes Emit() to Invoke() in the client. BREAKING CHANGE Signed-off-by: Lance Ball <lball@redhat.com> * squash: use a common Invoker interface for HTTP and events Signed-off-by: Lance Ball <lball@redhat.com> * checkpoint Signed-off-by: Lance Ball <lball@redhat.com> * fixup: change Emitter to EventInvoker Signed-off-by: Lance Ball <lball@redhat.com> * Invoke v2 Draft * feat: client invoke function * static invoke defaults and methods * remove assimilated invoker package * includes an ignored .func directory on create * Instances manager with local and remote defaults Funciton Info is now Instance, representing a Function in a given environment. Describing a Function instance is now Instances().Get(f, environment) Moves Runner to be async with a Stop method to enable returning runtime pid and port for persisting. Instances now have a place for primary Route in addition to all routes slice Running Functions write PID and Port to .func * cascading targets: local vs remote vs ad-hoc endpoint * runner start signals and cancel cleanup * return run on context done or err on channel * async runner Refactors the image runner to start the container asynchronously, reporting back the port on which it started. Errors are communicated back via a provided channel and stop is signaled using context cancelation. * pid neither required nor available * add withTransport option Incorporates addition of custom transport of the emitter into the renamed version invoker. Flag and help text cleanup. Re-additionof the Info accessor. * schema now includes invocation data * loop build msg * run jobs Externally exposed port is now chosen based on availability, with 8080 preferred and falling back to an os-chosen open port. The Client Run method is now async, returning the port assigned to the running Function, a stop/cleanup function and a runtime errors channel. The Runner is internally divided into the runner and its started Jobs. * job metadata Extracts job metadata tracking to a Job object in the core, Handles multiple instances of the same Function by creating a single file for each instances in .func/instances/<port> * remove superfluous error types and flag bindings * feat: enable invoke target remote * feat: preferentially invoke local, remote if running * feat: read --file for invoke * feat: invoke confirm prompts * fixup cli tests - Updates to handle asynchronous Runner - Standardize on the naming convention for selective running * docker runner tests and lint errors * test refactor * feat: invoke format override * comments, spelling and other cleanup * invoke command doc * feat: invoke format interactive option * rename runjob.go to job.go * e2e test flag update * test naming homoginization * silence build activity messages when verbose * test debugging * code review updates - return Job from Client.Run rather than constituent members - Treat .gitignore as contentious, punting on feature to mutate if extant. - docs wording changes - add invocation format to pertinent manifest.yaml files * help text spelling etc. Co-authored-by: Lance Ball <lball@redhat.com> |
||
|---|---|---|
| .. | ||
| customLanguagePackRepo | ||
| customTemplateRepo | ||
| README.md | ||
README.md
Test Repositories
Contains examples of previously-installed repositories for use in tests.
customTemplatesRepo
Contains an example of a repository consisting of simple templates, subgrouped by runtime. As the base case, it contains no additional metadata and is intended to show the simplest possible way to provide custom templates.
customLanguagePackRepo
Contains an example of a repository that includes a manifest.yaml, defining an alternate internal location for templates (used when the root needs to contain other directories, such as those necessary for language pack repos which also contain templates)