mirror of
https://github.com/containers/podman.git
synced 2025-12-01 10:38:05 +08:00
d5841ed528
Support a new concept in containers.conf called "modules". A "module" is a containers.conf file located at a specific directory. More than one module can be loaded in the specified order, following existing override semantics. There are three directories to load modules from: - $CONFIG_HOME/containers/containers.conf.modules - /etc/containers/containers.conf.modules - /usr/share/containers/containers.conf.modules With CONFIG_HOME pointing to $HOME/.config or, if set, $XDG_CONFIG_HOME. Absolute paths will be loaded as is, relative paths will be resolved relative to the three directories above allowing for admin configs (/etc/) to override system configs (/usr/share/) and user configs ($CONFIG_HOME) to override admin configs. Pulls in containers/common/pull/1599. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
54 lines
2.2 KiB
Markdown
54 lines
2.2 KiB
Markdown
# Request Based SFTP API
|
|
|
|
The request based API allows for custom backends in a way similar to the http
|
|
package. In order to create a backend you need to implement 4 handler
|
|
interfaces; one for reading, one for writing, one for misc commands and one for
|
|
listing files. Each has 1 required method and in each case those methods take
|
|
the Request as the only parameter and they each return something different.
|
|
These 4 interfaces are enough to handle all the SFTP traffic in a simplified
|
|
manner.
|
|
|
|
The Request structure has 5 public fields which you will deal with.
|
|
|
|
- Method (string) - string name of incoming call
|
|
- Filepath (string) - POSIX path of file to act on
|
|
- Flags (uint32) - 32bit bitmask value of file open/create flags
|
|
- Attrs ([]byte) - byte string of file attribute data
|
|
- Target (string) - target path for renames and sym-links
|
|
|
|
Below are the methods and a brief description of what they need to do.
|
|
|
|
### Fileread(*Request) (io.Reader, error)
|
|
|
|
Handler for "Get" method and returns an io.Reader for the file which the server
|
|
then sends to the client.
|
|
|
|
### Filewrite(*Request) (io.Writer, error)
|
|
|
|
Handler for "Put" method and returns an io.Writer for the file which the server
|
|
then writes the uploaded file to. The file opening "pflags" are currently
|
|
preserved in the Request.Flags field as a 32bit bitmask value. See the [SFTP
|
|
spec](https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-02.txt#section-6.3) for
|
|
details.
|
|
|
|
### Filecmd(*Request) error
|
|
|
|
Handles "SetStat", "Rename", "Rmdir", "Mkdir" and "Symlink" methods. Makes the
|
|
appropriate changes and returns nil for success or an filesystem like error
|
|
(eg. os.ErrNotExist). The attributes are currently propagated in their raw form
|
|
([]byte) and will need to be unmarshalled to be useful. See the respond method
|
|
on sshFxpSetstatPacket for example of you might want to do this.
|
|
|
|
### Fileinfo(*Request) ([]os.FileInfo, error)
|
|
|
|
Handles "List", "Stat", "Readlink" methods. Gathers/creates FileInfo structs
|
|
with the data on the files and returns in a list (list of 1 for Stat and
|
|
Readlink).
|
|
|
|
|
|
## TODO
|
|
|
|
- Add support for API users to see trace/debugging info of what is going on
|
|
inside SFTP server.
|
|
- Unmarshal the file attributes into a structure on the Request object.
|