daml/release/sdk-config.yaml.tmpl

114 lines
3.8 KiB
Cheetah
Raw Normal View History

2019-04-04 11:33:38 +03:00
version: __VERSION__
commands:
- name: studio
path: daml-helper/daml-helper
desc: "Launch Daml Studio"
args: ["studio"]
completion: true
- name: new
path: daml-helper/daml-helper
desc: "Create a new Daml project"
args: ["new"]
completion: true
- name: create-daml-app
path: daml-helper/daml-helper
desc: "Create a new Daml project based on create-daml-app"
args: ["create-daml-app"]
completion: true
- name: init
path: daml-helper/daml-helper
desc: "Configure a folder as a Daml project"
args: ["init"]
completion: true
- name: build
path: damlc/damlc
args: ["build", "--project-check"]
desc: "Build the Daml project into a DAR file"
completion: true
- name: test
path: damlc/damlc
args: ["test"]
desc: "Run the scenarios in the given Daml file and all dependencies"
completion: true
- name: start
2019-04-04 11:33:38 +03:00
path: daml-helper/daml-helper
args: ["start"]
desc: "Launch Sandbox and Navigator for current Daml project"
completion: true
- name: clean
path: damlc/damlc
args: ["clean", "--project-check"]
desc: "Delete build artifacts from project folder"
completion: true
- name: damlc
path: damlc/damlc
desc: "Run the Daml compiler"
completion: true
2019-04-04 11:33:38 +03:00
- name: sandbox
path: daml-helper/daml-helper
desc: "Launch Sandbox"
Add `platform-version` field to `daml.yaml` (#6736) * Add `platform-version` field to `daml.yaml` This PR adds the `platform-version` field to `daml.yaml`. Based on the approach agreed upon in #6558, the logic for this all sits in `daml-helper` and there are no changes to the assistant. The details of how the logic work are in a comment so I’m not going to repeat them here but the commands that are affected are: - `daml sandbox` - `daml sandbox-classic` - `daml json-api` - `daml start` (but only for sandbox and the JSON API, not for Navigator or anything else) For tests, I’ve added a test to the compat workspace that installs two SDKs simultaneously and tries out various combinations and verifies that we get the correct version. Open to other ideas for testing this but that seemed like the most sensible option that actually tests what we run. changelog_begin - [DAML Assistant] You can now specify the version of Sandbox and the JSON API independently of your SDK version by setting ``platform-version`` in your ``daml.yaml``. This is useful if you are deploying to a ledger that is running components from a different SDK version. See https://docs.daml.com/tools/assistant.html#project-config-file-daml-yaml for details. changelog_end * Run platform-version tests changelog_begin changelog_end * Fix tag globbing changelog_begin changelog_end * fmt changelog_begin changelog_end * . changelog_begin changelog_end * Try to fix env vars changelog_begin changelog_end * Remove hardcoded references to 1.2.0 changelog_begin changelog_end * Rephrase doc comment changelog_begin changelog_end * get things to compile changelog_begin changelog_end * maybe fix things for realz changelog_begin changelog_end * Remove debugging output changelog_begin changelog_end * Get angry at windows changelog_begin changelog_end * why is windows changelog_begin changelog_end * . changelog_begin changelog_end
2020-07-15 17:30:01 +03:00
args: ["run-platform-jar", "--logback-config=sandbox-logback.xml", "sandbox"]
- name: sandbox-classic
path: daml-helper/daml-helper
desc: "Deprecated. Launch Sandbox Classic (the default Sandbox implementation for SDK <= 0.13.55)"
Add `platform-version` field to `daml.yaml` (#6736) * Add `platform-version` field to `daml.yaml` This PR adds the `platform-version` field to `daml.yaml`. Based on the approach agreed upon in #6558, the logic for this all sits in `daml-helper` and there are no changes to the assistant. The details of how the logic work are in a comment so I’m not going to repeat them here but the commands that are affected are: - `daml sandbox` - `daml sandbox-classic` - `daml json-api` - `daml start` (but only for sandbox and the JSON API, not for Navigator or anything else) For tests, I’ve added a test to the compat workspace that installs two SDKs simultaneously and tries out various combinations and verifies that we get the correct version. Open to other ideas for testing this but that seemed like the most sensible option that actually tests what we run. changelog_begin - [DAML Assistant] You can now specify the version of Sandbox and the JSON API independently of your SDK version by setting ``platform-version`` in your ``daml.yaml``. This is useful if you are deploying to a ledger that is running components from a different SDK version. See https://docs.daml.com/tools/assistant.html#project-config-file-daml-yaml for details. changelog_end * Run platform-version tests changelog_begin changelog_end * Fix tag globbing changelog_begin changelog_end * fmt changelog_begin changelog_end * . changelog_begin changelog_end * Try to fix env vars changelog_begin changelog_end * Remove hardcoded references to 1.2.0 changelog_begin changelog_end * Rephrase doc comment changelog_begin changelog_end * get things to compile changelog_begin changelog_end * maybe fix things for realz changelog_begin changelog_end * Remove debugging output changelog_begin changelog_end * Get angry at windows changelog_begin changelog_end * why is windows changelog_begin changelog_end * . changelog_begin changelog_end
2020-07-15 17:30:01 +03:00
args: ["run-platform-jar", "--logback-config=sandbox-logback.xml", "sandbox-classic"]
2019-04-04 11:33:38 +03:00
- name: navigator
path: daml-helper/daml-helper
desc: "Launch the Navigator"
args: ["run-jar", "--logback-config=daml-sdk/navigator-logback.xml", "daml-sdk/daml-sdk.jar", "navigator"]
2019-04-04 11:33:38 +03:00
- name: extractor
path: daml-helper/daml-helper
desc: "Launch the Extractor (early access)"
args: ["run-jar", "--logback-config=daml-sdk/extractor-logback.xml", "daml-sdk/daml-sdk.jar", "extractor"]
- name: ledger
path: daml-helper/daml-helper
desc: "Interact with a Daml ledger"
args: ["ledger"]
completion: true
- name: packages
path: daml-helper/daml-helper
desc: "Query packages of a remote Daml ledger"
args: ["packages"]
completion: true
- name: codegen
path: daml-helper/daml-helper
desc: "Run a language bindings code generation tool"
args: ["codegen"]
completion: true
- name: deploy
path: daml-helper/daml-helper
desc: "Deploy Daml project to a ledger"
args: ["deploy"]
completion: true
- name: ide
path: damlc/damlc
args: ["lax", "ide"]
- name: json-api
path: daml-helper/daml-helper
desc: "Launch the HTTP JSON API"
Add `platform-version` field to `daml.yaml` (#6736) * Add `platform-version` field to `daml.yaml` This PR adds the `platform-version` field to `daml.yaml`. Based on the approach agreed upon in #6558, the logic for this all sits in `daml-helper` and there are no changes to the assistant. The details of how the logic work are in a comment so I’m not going to repeat them here but the commands that are affected are: - `daml sandbox` - `daml sandbox-classic` - `daml json-api` - `daml start` (but only for sandbox and the JSON API, not for Navigator or anything else) For tests, I’ve added a test to the compat workspace that installs two SDKs simultaneously and tries out various combinations and verifies that we get the correct version. Open to other ideas for testing this but that seemed like the most sensible option that actually tests what we run. changelog_begin - [DAML Assistant] You can now specify the version of Sandbox and the JSON API independently of your SDK version by setting ``platform-version`` in your ``daml.yaml``. This is useful if you are deploying to a ledger that is running components from a different SDK version. See https://docs.daml.com/tools/assistant.html#project-config-file-daml-yaml for details. changelog_end * Run platform-version tests changelog_begin changelog_end * Fix tag globbing changelog_begin changelog_end * fmt changelog_begin changelog_end * . changelog_begin changelog_end * Try to fix env vars changelog_begin changelog_end * Remove hardcoded references to 1.2.0 changelog_begin changelog_end * Rephrase doc comment changelog_begin changelog_end * get things to compile changelog_begin changelog_end * maybe fix things for realz changelog_begin changelog_end * Remove debugging output changelog_begin changelog_end * Get angry at windows changelog_begin changelog_end * why is windows changelog_begin changelog_end * . changelog_begin changelog_end
2020-07-15 17:30:01 +03:00
args: ["run-platform-jar", "--logback-config=json-api-logback.xml", "json-api"]
- name: trigger-service
path: daml-helper/daml-helper
desc: "Launch the trigger service"
args: ["run-jar", "--logback-config=daml-sdk/trigger-service-logback.xml", "daml-sdk/daml-sdk.jar", "trigger-service"]
- name: oauth2-middleware
path: daml-helper/daml-helper
desc: "Launch the OAuth 2.0 middleware"
args: ["run-jar", "--logback-config=daml-sdk/oauth2-middleware-logback.xml", "daml-sdk/daml-sdk.jar", "oauth2-middleware"]
- name: trigger
path: daml-helper/daml-helper
args: ["run-jar", "--logback-config=daml-sdk/trigger-logback.xml", "daml-sdk/daml-sdk.jar", "trigger"]
desc: "Run a Daml trigger"
- name: script
path: daml-helper/daml-helper
args: ["run-jar", "--logback-config=daml-sdk/script-logback.xml", "daml-sdk/daml-sdk.jar", "script"]
desc: "Run a Daml script"
- name: test-script
path: daml-helper/daml-helper
args: ["run-jar", "--logback-config=daml-sdk/test-script-logback.xml", "daml-sdk/daml-sdk.jar", "test-script"]
desc: "Run all Daml script tests in a DAR"
- name: repl
path: damlc/damlc
args: ["repl"]
desc: "Launch the Daml REPL"