Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/dontlaugh/packer-provisioner-deno

A Packer plugin that runs Deno scripts for provisioning VMs and containers
https://github.com/dontlaugh/packer-provisioner-deno

deno packer-plugin packer-provisioner

Last synced: about 2 months ago
JSON representation

A Packer plugin that runs Deno scripts for provisioning VMs and containers

Lists

README 

        
# packer-provisioner-deno



Run Deno scripts to provision stuff with Packer.



This plugin installs deno on the target machine, runs `deno bundle` locally, 

uploads the bundled scripts onto the target machine, and executes them.



## Installation



This provisioner is a Packer plugin. [See the docs for an overview](https://www.packer.io/docs/extending/plugins.html#installing-plugins).



Build or download this plugin and place in



```

$HOME/.packer.d/plugins

```



You may need to create the plugins directory.



## Provisioner Configuration



You must specify `"type": "deno"` in a provisioners stanza to use this plugin.



The following provisioner config keys are supported. See also the **examples** directory.



* `local_deno_bin` (string) - A fully qualified path to a local deno executable. This

  binary will be used for local bundling and uploaded to the target `remote_folder`.

  Useful if you are building deno from source. Other version specifiers ignored.

* `target_deno_version` (string) - a version passed to the deno installer script.

  Must match a git tag from deno's [releases](https://github.com/denoland/deno/releases).

* `remote_folder` (string) - The target directory where `scripts` will be uploaded.

* `skip_install` (boolean) - If `true`, do not install Deno on the target machine, but

  assume it is already present.

* `scripts` (array of string) - A list of paths to TypeScript files that will be

  passed to `deno run -A`, one by one, in order. These are your provisioning scripts.

  Currently, these must be standalone scripts with no path-based dependencies.



## Development and Tests



You will need Go 1.13 or later. **$GOPATH/bin** should be on your PATH. 



If you want to hack, make a symlink from **$GOPATH/bin/packer-provisioner-deno**

to the packer plugins directory. Something like this should work, after an

initial `go install`:



```

ln -s $GOPATH/bin/packer-provisioner-deno $HOME/.packer.d/plugins/packer-provisioner-deno

```



After that, run the test script



```

./test.sh

```



A test build will run in a Docker container.



## TODO



We want to accomplish the following



- [x] Install deno onto target system

- [x] Upload individual deno scripts

- [x] Execute individual deno scripts as root

- [x] Add a DigitalOcean cloud builder test

- [x] Allow uploading local deno builds easily (for testing local dev builds)

- [x] Manually bundle scripts locally and upload those.

- [ ] Execute scripts as non-root user

- [ ] Specify sandboxing flags in the packer config (`--allow-net` and friends; we run with `-A` right now)

- [ ] Global system install of deno outside any user's HOME

- [ ] Add a Vagrant builder test

- [ ] Specify alternative install command (for test deno builds fetchable from network)