You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated to the latest commit (919e701) because I wanted to use the new type:"filecontent" feature (thank you!). It works as expected, but I notice in the help output the argument is followed by ..., which I believe implies multiple arguments could be supplied. Is this an artifact of the field type being []byte?
See <function-io> in the help output below.
$ _output/bin/linux_arm64/xfn run negz/xfn-nop:latest ~/fnio.yaml mooUsage: crossplane run <image> <function-io> ...Run a Composition Function.Arguments: <image> OCI image to run. <function-io> ... YAML encoded FunctionIO to pass to the function.Flags: -h, --help Show context-sensitive help. -d, --debug Print verbose logging statements. -v, --version Print version and quit. -c, --cache-dir="/xfn" Directory used for caching function images and containers. --timeout=30s Maximum time for which the function may run before being killed. --map-root-uid=100000 UID that will map to 0 in the function's user namespace. The following 65336 UIDs must be available. Ignored if xfn does not have CAP_SETUID and CAP_SETGID. --map-root-gid=100000 GID that will map to 0 in the function's user namespace. The following 65336 GIDs must be available. Ignored if xfn does not have CAP_SETUID and CAP_SETGID.
// Command runs a Composition function.typeCommandstruct {
CacheDirstring`short:"c" help:"Directory used for caching function images and containers." default:"/xfn"`Timeout time.Duration`help:"Maximum time for which the function may run before being killed." default:"30s"`MapRootUIDint`help:"UID that will map to 0 in the function's user namespace. The following 65336 UIDs must be available. Ignored if xfn does not have CAP_SETUID and CAP_SETGID." default:"100000"`MapRootGIDint`help:"GID that will map to 0 in the function's user namespace. The following 65336 GIDs must be available. Ignored if xfn does not have CAP_SETUID and CAP_SETGID." default:"100000"`Imagestring`arg:"" help:"OCI image to run."`FunctionIO []byte`arg:"" help:"YAML encoded FunctionIO to pass to the function." type:"filecontent"`
}
The text was updated successfully, but these errors were encountered:
negz
changed the title
Argument fields of type:"filecontent appear to accept multiple argumentsfilecontent argument fields appear to accept multiple arguments
Dec 22, 2022
I just updated to the latest commit (919e701) because I wanted to use the new
type:"filecontent"
feature (thank you!). It works as expected, but I notice in the help output the argument is followed by...
, which I believe implies multiple arguments could be supplied. Is this an artifact of the field type being[]byte
?See
<function-io>
in the help output below.The text was updated successfully, but these errors were encountered: