#github-feed
1 messages ยท Page 23 of 1
- Keep or Remove: Is this a duplicate? Is it implemented? Does it work?
- Documentation: Does the generated doc look okay?
- Is the package documented? https://github.com/dagger/dagger/pull/564#issuecomment-855719428
- Is every
#Definitiondocumented? - Is every input and output documented?
- Annotations: Are the inputs and outputs correctly annotated with
@dagger(input)and@dagger(output)? - Test: Is there a bare minimum of testing?
- Consistency:
...
Tentative plan (suggestion only -- need to confirm with "Quick Start" doc @samalba):
- Provision a S3 bucket on AWS using CloudFormation
- Upload files to the bucket using the same instructions as the "Quick Start" example
Assigning to @samalba to confirm the scenario, please re-assign to @grouville to lead the implementation
Provide basic commands to import/export encryption keys.
Goal: one line command to import the the encryption key used in the examples.
Alternative to the Kubernetes tutorial for application deployment.
Today we don't support Cloud Run, so the first step would be to implement gcp/cloudrun.
We already do support a couple of GCP services (GCR and GKE) and have a generic gcp.#GCloud abstraction to run the gcloud CLI with authentication and presets, hopefully adding support for Cloud Run is quick and painless.
- add todo app from https://github.com/mdn/todo-react
- implement Dockerfile
Bumps merge-deep from 3.0.2 to 3.0.3.
Commits
628ff47 3.0.3
cfbe20c run verb to generate README documentation
e370968 Merge pull request #17 from jonschlinkert/key-properties
393e2cb adding a test to ensure using merge-deep for inheritance still works
c39b161 add test to ensure constructor is not cloned
11e5dd5 add isValidKey function to ensure only valid keys are merged
See full diff in compare view
[ that the file doesn't exist (fixed with a sleep, but if behavior is confirmed, will need to find a better fix...
This is a temporary workaround for issue #495 - right now yarn is barely usable because of exec duplication.
As soon as #495 is fixed, this can be reverted.
I don't think this is related to AWS, pretty sure this is global to usage of secrets.
I gave wrong secrets to awsConfig and I got the following error:
5:35PM INF s3bucket.url | computing
5:35PM ERR s3bucket.url | #13 3.188 fatal error: An error occurred (AuthorizationHeaderMalformed) when calling the ListObjectsV2 operation: The authorization header is malformed; the Credential is mal-formed; expecting "/YYYYMMDD/REGION/SERVICE/aws4_request".
I then tried to fix the keys a...
Implements todoapp deployment to s3 static website
Meta issue to capture docs website.
- Integrate new design
- Make the docs website responsive
- Misc issues (e.g.
inlined code not very readable)
See #193 for previous attempt.
This has been causing massive headaches and some issues are still not fixed.
- Either things were running too many times (cache issue): #449 #495
- Or not enough ("random" generation bug that broke the CI for a few days)
There's a few causes, some of the most recent ones:
always: trueonly guarantees the instructions to run ONCE for eachdagger up.- things like generating a random number with
always: truewill yield the same random n...
- things like generating a random number with
Currently docker.#Run can run an image specified by ref, but cannot run an arbitrary artifact. This prevents composition, for example itโs not possible to build a container then directly running it on a remote host.
Temporarily disable cache mount #495
Updated the whole docs layout
Adding empty template for cloudformation guide
- Fix running from any directory
- Fix display format for test logs
- Move helpers to a common helper file
- Indentation
- Enable shellcheck for universe tests
- doc generation: refactor to allow multi-stage processing
- docs generation: write package doc as README.md if there are sub-packages
Signed-off-by: Tihomir Jovicic
In docs.dagger.io, the complete contents of the API reference (full package hierarchy) is unrolled in the navigation bar, which makes it very long and makes the overall structure hard to read.

Instead of https://todoapp.microstaging.io, use https://todoapp.dagger.run. Similar to https://waypoint.run, itโs self-explanatory that it is part of the Dagger platform, yet distinct from dagger.io.
We should document how to contribute to the Dagger project, with topics such as:
- How to find something useful to do
- Architecture of the codebase
- Contributing to the Dagger engine (go)
- Contributing to the Dagger universe (cue)
- When and how to use Github issues & discussions
- When and how to use Discord
- How to run the tests ; how to add tests
- Contirbuting to the docs
- FAQ: commands you will probably need, but are hard to remember
etc.
See https://github.com/dagger/dagger/pull/610 for examples. The following content must be completely migrated:
./tests/stdlib/to./universe/.dagger/env(requires creating valid dagger environments)./tests/stdlib.batsto./universe/universe.bats(requires adapting the tests)
First version of the user manual.
This is an umbrella issue for the problem of unclear error messagesโฆ Of which there are a lot.
Along with AWS and GCP support that we already have, it would be nice to have Azure support.
It would be a directory in stdlib similar to GCP and AWS one:
https://github.com/dagger/dagger/tree/main/stdlib/gcp
https://github.com/dagger/dagger/tree/main/stdlib/aws
Currently we just ignore the input if it's non existing.
We should at least log a warning to a user that the type of the input is not the same
Currently we write a test, create an environment (using dagger init and new) and copy the .cue test file to .dagger/plan/env. Often, when I'm updating the test I forget to update the same file in the .dagger/plan/env dir.
Maybe a practical solution is using soft links.
Self explanatory, happens on input.
- explain what exactly happens when running
dagger up - it isn't clear is
upcommands are ran sequentially or in parallel - document useful commands like:
dagger query,dagger input edit,dagger -l debug up --no-cache
The Amazon S3 package should support (optionally) creating a bucket when it does not exist.
Changes
Replace docker.#Client with docker.#Command definition
It's a simple wrapper that will expose an interface to run any docker or docker-compose commands
You can configure :
- ssh
- environments
- mount volumes
- command to execute
- package to install
Tests
- docker version with ssh
- docker version with ssh and key passphrase
- docker version with ass and wrong key passphrase
Changes
Replace docker.#Client with docker.#Command definition
It's a simple wrapper that will expose an interface to run any docker or docker-compose commands
You can configure :
- ssh
- environments
- mount volumes
- command to execute
- package to install
Tests
- docker version with ssh
- docker version with ssh and key passphrase
- docker version with ass and wrong key passphrase
Actually, we use the old version of dagger.#Secret in #DockerLogin
#DockerLogin: {
do: "docker-login"
target: string | *"https://index.docker.io/v1/"
username: string
// FIXME: should be a #Secret (circular import)
secret: string | bytes
}
That's a real problem because we can't send secret. Tests are using dagger compute --input-yaml inputs.yaml but it gonna be deprecated.
Changes
- Resolve #552
- Update
docker.#Pushdocumentation - Replace old tests with new one
Issues
op.#DockerLogin doesn't support new type dagger.#Secret, wrote an issue : #627.
I've use an hack to do tests with secret but we should fix this really fast
Bumps github.com/rs/zerolog from 1.22.0 to 1.23.0.
Commits
117cb53 Fix copying stack setting in logger's Output method (#325)
e05605c Use github.com/coreos/go-systemd/v22 (#322)
6ed1127 Fix panic on disabled event with CallerSkipFrame
47a03bc Add ability to customize internal json marshaler (#318)
ffbd37b Add Func log method (#321)
See full diff in compare view
[, add a new field cue to the environment configuration (.dagger/env/FOO/values.yaml):
plan: module(optional) references the local path of the cue module to use as a plan, relative to the workspace root. Default:..plan: package(optional) references the name of the Cue package within the module to use as a plan. Default: defer to cue loader (accept any ...
@samalba @aluzzardi @shykes
Here is the first draft of the Infrastructure provisioning guide. I chose one of the possible angles : I chose to be very didactic. It may be missing some why ? I didn't find them 100% necessary, as most of it would already be explained in previous guides
Signed-off-by: Guillaume de Rouville
Fixing an English typo leading to some ugly AWS CLI help :
โ plan dagger input list
Input Value Set by user Description
...
cfnStack.timeout *10 | >=0 & int false Timeout for waiting for the stack to be created/updated (in minutes) =0 & int false Maximum waiting time until stack creation/update (in minutes)
Signed-off-by: Guillaume de Rouville
Signed-off-by: slumbering
Bumps sass from 1.34.1 to 1.35.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.35.0
To install Sass 1.35.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Fix a couple bugs that could prevent some members from being found in certain files that use a mix of imports and the module system.
Fix incorrect recommendation for migrating division expressions that ref...
First pass at stdlib package doc strings for improved generated reference doc.
This is 100% backward compatible at the moment.
dagger new still defaults to .dagger/env//plan (so no breaking changes).
Switching to the new UX is just a matter of defaulting the module to . instead. This requires updating the docs first.
- add support for
--moduleand--packagetodagger new - editable through
dagger edit(note: renamed fromdagger input edit) - backward compatible and lazy migration (e.g. running
dagger up,dagger editetc will add aplansecti...
Bumps filippo.io/age from 1.0.0-rc.2 to 1.0.0-rc.3.
Release notes
Sourced from filippo.io/age's releases.
Never two without three
Maybeโข๏ธ actuallyโข๏ธ the last v1.0.0 release candidate!
Encrypted identity files are now supported. Regular passphrase-encrypted age files can be used with -i, the passphrase will be requested interactively, and the decrypted file will be read line-by-line as a standard identity file.
Passphrases can now be requested interactiv...
Bumps github.com/spf13/viper from 1.7.1 to 1.8.0.
Release notes
Sourced from github.com/spf13/viper's releases.
v1.8.0
This is a maintenance release primarily containing fixes and improvements. The most prominent change is the etcd update to 3.5.0. Thanks to proper Go modules support, the dependency graph became much smaller.
##ย Changes
Added
Allow BindEnv to register multiple environment variables
Support for accessing slices
Experimental WASM support: Vi...
Bumps sass from 1.35.0 to 1.35.1.
Release notes
Sourced from sass's releases.
Dart Sass 1.35.1
To install Sass 1.35.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Fix a bug where the quiet dependency flag didn't silence warnings in some stylesheets loaded using @import.
See the full changelog for changes in earlier releases.
Changelog
Sourced from sass's changelog....
- Git package uniformization : as it was properly commented, mainly moving
@output+ removing\n. - Add tests for git package
Signed-off-by: Guillaume de Rouville
In the API reference section of the docs, each individual package has an address (for example /reference/universe/alpine), but there is no address for the API reference as a whole.
/referencereturns 404/reference/universereturns 404
This makes it difficult for other docs pages to link to the APi reference, which would be very useful.
[dagger/dagger] Pull request opened: #659 docs: uniform codeblocs => use shell language \+ add title
- @shykes I saw that you used
bashin code blocs, butshellis being used everywhere. So I changed toshellin 102 doc - I separated textual changes from unification, here it's only unification
- I'm doing like Andrea in 108: I work directly in
.dagger, and set the title the same way as he does - Fixing some linting issues hidden by
.mdxformat
Signed-off-by: Guillaume de Rouville
Signed-off-by: Sam Alba
Signed-off-by: Solomon Hykes
@shykes
- I implemented everything you asked : now everything lies in subdirectories, and development angle also changed
- I also directly modified the AWS guide (even though not complete yet), to follow these guidelines
- Also removed the harcoded "us-east-2"
Signed-off-by: Guillaume de Rouville
As seen with @aluzzardi, the doc uses the str type for kubeconfig input. It had been changed as a secret, however, GKE exports a string (cannot export secrets). A revert was necessary in order to run gke and eks packages
Signed-off-by: Guillaume de Rouville
Fix last bugs on Kubernetes's doc : fully tested for kind version
Signed-off-by: Guillaume de Rouville
To avoid duplicate and out-of-date content, remove the original examples directory in favor of the new tutorials and accompanying examples repository.
If we want to reuse content from the original examples, we can always fish it out of the git history.
Authorization scope needs to me less permissive.
issue reported by Discord user julieng
Signed-off-by: slumbering
Use env variables to enable/disable GIthub Oauth
Stop api call (when browser is refresh) when user is granted
always: true is no more mandatory in the example app.
For docs clarity, I replaced always: *true | bool with always: *true | false - which broke the if in the s3.cue.
This PR solves the issue.
Url
The link toward Dagger Universe is broken (404 page not found)

- docs: set env vars for deployment
- docs: netlify: disable auth for deploy preview, enable in production
Changes
Move tests from stdlib to universe
Packages done :
- AWS : eks
- Docker : build
- Docker : build from dockerfile
- Docker : pull and push (done in #628)
- K8S : deployment
- K8S : Helm
- K8S : Kustomize
- Terraform
Fix
I've fix helm tests, kubernetes can't deploy a pod thas has a name longer than 53 characters.
Here's the issue
Add a #Input core type to wrap dagger(input) attribute.
Bumps @docusaurus/core from 2.0.0-beta.0 to 2.0.0-beta.1.
Release notes
Sourced from @โdocusaurus/core's releases.
v2.0.0-beta.1
2.0.0-beta.1 (2021-06-18)
:rocket: New Feature
docusaurus-plugin-content-docs
#4982 feat(v2): add docs pagination_label frontmatter (@โslorber)
docusaurus-theme-classic
#4949 feat(v2): add icon to external navbar links (@โlex111)
#4939 feat(v2): theme default translations Bengali (@โNeilb...
Bumps @docusaurus/preset-classic from 2.0.0-beta.0 to 2.0.0-beta.1.
Release notes
Sourced from @โdocusaurus/preset-classic's releases.
v2.0.0-beta.1
2.0.0-beta.1 (2021-06-18)
:rocket: New Feature
docusaurus-plugin-content-docs
#4982 feat(v2): add docs pagination_label frontmatter (@โslorber)
docusaurus-theme-classic
#4949 feat(v2): add icon to external navbar links (@โlex111)
#4939 feat(v2): theme de...
Changes
Resolve #593
docker.#Runcan now run the container from an artifact.- Improve
docker-run-sshtests
Signed-off-by: slumbering
This is a placeholder issue. @slumbering and @aluzzardi have encountered an issue with the netlify package, which prevents them from configuring Netlify via the netlify.toml file.
FIXME: insert more details on the issue here :)
- Add tests to dagger/examples
- A PR against dagger/examples should run the examples suite
- A PR against dagger/dagger should run the examples suite
Thanks to #648, plans can now reside in a different directory than .dagger/env/XX/plan.
- Move tests directly inside the package, e.g.
universe/docker/test(note: in cue a sub-package is a specialization of the parent package) - Change the universe environment to point to the new plan (e.g. using
dagger edit, change theplankey)
Related to #611, will address #619
To complete #631: #648 introduced a --module and --package flag to dagger new.
By default, we use .dagger/env/XXX/plan as the cue module. Instead, we should default to ..
In preparation of moving universe out of the dagger binary (#285), an intermediary step would be to provide the future UX (e.g. dump universe inside cue.mod) while keeping universe vendored in the binary.
There's a few open questions:
- How do we keep track of versioning?
- How do we detect an outdated version? Do we prompt the user for updates?
- What are the commands to get/upgrade?
This is related to #540 and will allow to cue eval dagger configurations
Perhaps we should put it behind a CloudFront distribution
Feedback from @tiborvass
- Move to a "one step install"
- Consider using
sudoin the install script itself (that's what homebrew does). e.g.curl | shinstead ofcurl | sudo sh - Consider a shorter URL, e.g.
dl.dagger.io/install - Make sure the install script is viewable from the browser (I think the content type is not set so the browser downloads it right away)
Feedback from me: maybe we should just put a CloudFront in top of our bucket rather than using redirects (so it...
Right now only kind is fully functional -- the GKE/EKS examples do not use GCR/ECR.
Currently, only the S3 tutorial (101) uses examples/todoapp has its plan embedded (e.g. examples/todoapp/.dagger/env/s3/plan).
We should make this pattern consistent across all the tutorials.
AFAIK, the kubernetes tutorial is different. I'm not sure about the others.
This prevent the call as specified in the tutorial to error out if
${HOME}/.config/dagger does not exist yet.
Signed-off-by: Kenfe-Mickael Laventure
Allows a unique page that indexes stdlib.
Fixes #681
This simplifies the os.#File API to make it less verbose and more intuitive. Itโs a breaking change. Dependencies in stdlib have been fixed, but I may have missed some.
Complete refacto of the CF doc.
- For consistence, it follows at 99% Andrea's writing style. The process is the same. Learnings are similar, even more detailed
dagger.#Inputis now used- Also fixes an output issue on the Cloudformation's relay: we didn't have the
- Grammarly has been used, for English consistency
100% working as of now!
In this example, the s3 secret can be easily decrypted.
If the secret must remain in the project I think the secret authorization must be limited.
Note: this issue resurrects a discussion started in a now-closed PR
Summary
There are several methods to manage Kubernetes configurations with Dagger. Currently, the Kubernetes tutorial focuses on one method: embedding a configuration in a string, in the cue config. This method has benefits in the context of a tutorial, but it has one major drawback: it is unfamiliar to Kubernetes users. We should modify the tut...
Summary
Maintainers must check each commit to make sure that the DCO statement (Signed-off-by: ) includes the real name of the contributor, and not a pseudonym.
Context
Dagger uses the Developer Certificate of Origin (DCO) process to make sure all contributors are legally allowed to contribute. Major projects like Linux and Docker use DCO to protect their contributors.
DCO is implemented by requiring that ...
I think the executable script used with curl isn't really deserving that project as there were many fuds back in the days when Docker was installable using the same mechanism.
Having, brew, binary and source method is by far enough IMHO
putting also the fact that this method (shell script) will definitely raise at some point, security concerns
there's no need to suggest moving the binary to /usr/local/bin as there are safer ways to make dagger binary available in the user path.
for example we can simply do either:
export PATH=$PATH:$HOME/bin
or
add into the .bashrc file :
# testing if dagger binary is present and updating user PATH
if [ -f ${HOME}/bin/dagger ]; then
export PATH=$PATH:$HOME/bin
fi
users who would want to test out dagger doesn't necessarily have sudo privileges :(
it might be pretty obvious i got that , but the tutorial is for anyone who's willing to discover dagger.
So we shouldn't make assumption they already know it leverages docker (buildkit).
So I think it would be beneficial to add that having a running Docker engine locally before running the demo app is mandatory :)
Signed-off-by: jffarge
TL;DR
- Resolve #685
- Update doc generator to ignore
testsdir
Changes
Move tests plan from .dagger/env/xxxx/plan to xxxx/tests.
E.g
$ ls -R universe/alpine
universe/alpine:
alpine.cue tests
universe/alpine/tests:
alpine.cue
Bumps @docusaurus/preset-classic from 2.0.0-beta.0 to 2.0.0-beta.2.
Release notes
Sourced from @โdocusaurus/preset-classic's releases.
v2.0.0-beta.2
:rocket: New Feature
docusaurus-plugin-content-docs, docusaurus-theme-classic
#5052 feat(v2): docs version banner configuration option (@โslorber)
docusaurus-plugin-content-blog, docusaurus-plugin-content-docs, docusaurus-types, docusaurus
#5037 feat(v2)...
Bumps docusaurus-plugin-sass from 0.2.0 to 0.2.1.
Release notes
Sourced from docusaurus-plugin-sass's releases.
v0.2.1
Fix: dev css modules classnames should include filename #18
Commits
294e8a5 Update package.json
13c60af Merge pull request #18 from frilox042/fix-css-module-identName-dev
39a3301 Fix: dev css modules classnames should include filename
6efa53f Merge pull request #16 from rlamana/dependabot/npm_and_yarn/hosted-git-inf...
Bumps @docusaurus/core from 2.0.0-beta.0 to 2.0.0-beta.2.
Release notes
Sourced from @โdocusaurus/core's releases.
v2.0.0-beta.2
:rocket: New Feature
docusaurus-plugin-content-docs, docusaurus-theme-classic
#5052 feat(v2): docs version banner configuration option (@โslorber)
docusaurus-plugin-content-blog, docusaurus-plugin-content-docs, docusaurus-types, docusaurus
#5037 feat(v2): plugins injectHtmlTags + configur...
@TomChv realized that one of our Bats test didn't fail on a test with missing inputs :
# Inside universe dir
dagger up -e docker-run-local >&- # <-- should fail and exit code should return 1, but not the case
The behavior:
If the stdout isn't linked to a terminal, we don't print missing inputs as errors but as warnings. As bats redirects the stdout, we fall under this behavior.
More precisely:
func checkInputs(ctx c...
This PR is the continuation of the doc: push image to remote repo + EKS/GKE afterward.
- It's still a WIP because I'm waiting for a PR to be merged, to avoid using low level components of Dagger
- It also fixes 2 minor issues on GKE/EKS packages (wrong @dagger.input location)
Signed-off-by: Guillaume de Rouville
This updates to use the latest version of dagger.io/os (change in #File) API.
Problem
Actually, values.yaml has been encrypted with different keys but the user can only fetch one.
Here is the difference
$ ls
helloapp LICENSE Makefile README.md todoapp voteapp
$ cat helloapp/.dagger/env/staging/values.yaml | grep "recipient"
- recipient: age1ez5phfa2l6e9fqt4nnem734jajg4nlcefhv3ydeltzjlele47ags34868h
$ cat todoapp/.dagger/env/s3/values.yaml | grep "recipient"
- recipient: age1gunf55cd2v30j76w4arxgmzks48v2a56pdw0vtn2j2ax6q2yp3wq...
Dagger supports encrypting secrets out of the box. But it does not (yet) support controlling who can access which encrypted secret.
Our underlying crypto framework (AGE and SOPS) provides building blocks for very powerful collaboration workflows. Now we have to assemble these building blocks in a particular way, and provide an outstanding collaboration experience in Dagger :)
Dagger supports encrypting secrets out of the box. But it does not (yet) support controlling who can access which encrypted secret.
Our underlying crypto framework (AGE and SOPS) provides building blocks for very powerful collaboration workflows. Now we have to assemble these building blocks in a particular way, and provide an outstanding collaboration experience in Dagger :)
It would be neat if dagger could optionally launch a companion webapp to monitor and configure an environment. This companion webapp would not implement a specific feature, but rather provide a platform for delivering various features that are more appropriate for a web environment. This would allow the CLI to focus on what it does best, and relax the requirement to do absolutely everything in a POSIX terminal, which is very challenging.
In short: if dagger always has access to 2 modes...
Problems
Actually, the documentation has some bug with universe packages.
Here's the list of current problem I've found :
docker.#Run: concrete value are displayed, inputs from child packages are shown for nothing.ecr.#Credentials: inputs fromaws.#Credentialare displayed twice.- [
ecs](https://devel.docs.dag...
Bumps github.com/spf13/viper from 1.8.0 to 1.8.1.
Release notes
Sourced from github.com/spf13/viper's releases.
v1.8.1
This patch releases fixes two minor issues:
Replace %s with %w when wrapping errors
Fix pflag.StringArray processing
Commits
bd03865 Add a proper processing for pflag.StringArray
3fcad43 update %s to %w
See full diff in compare view
[.
This case is exactly what we do in test...
I tried both the link in README.md and the welcome email: Join the Dagger community on Discord
I saw that docker-compose support was recently added; i suggest to install the newer implementation based on go.
Considering that it is based on the "cli plug-in mechanism" we can add the ability to install external cli plug-ins as packages or wait for it to become part of the base docker cli installation.
When we run dagger doc dagger.io/netlify it throws an error
FTL system | cannot compile code: cannot find package "dagger.io/netlify" for any module.
I tried it with dagger doc alpha.dagger.io/netlify, it was working. Just need to update the doc.
Dagger use OpenTracing to export traces, OpenTelemetry is considered the new version of both OpenTracing and OpenCensus
What IMO is missing from https://docs.dagger.io/vs is a comparison with terraform.
This PR addresses #472 by marking unimplemented sub-commands as hidden.
Signed-off-by: Cornelius Toole
As explained by @aluzzardi , the seed field in the random package is not actually a pseudo-random generator seed. I re-read the comment and still donโt completely understand what it actually isโฆ
I saw a downstream package do something like:
foo: random.#String & { seed: โsome constantโ }
This will probably cause reactions from people also confused by the term โseedโ.
We should either:
A) Better document what seed is and why it makes to call it that, or
B) change ...
Relaying feedback by @amylindburg , thanks Amy!
If you want the user to simply be able to type in the proposed commands to be successful, then there are a few commands where --environment should be specified (because you end up creating several during the tutorial). But not a biggie.
dagger query point --environment="cloudformation"
Relaying feedback from @amylindburg, thank you Amy!
The Plan
"The plan is the deployment code, that includes the logic to deploy the local application to an AWS S3 bucket."
Remove the comma: "The plan is the deployment code that includes the logic to deploy the local application to an AWS S3 bucket."
The Inputs
"The plan can define one or several inputs in order to take some information from the user."
The phrase "take some information from the user" ...
We are deprecating the original method of embedding cue configuration (โthe planโ) inside each environment directory. The recommended method is to write Cue configuration in a regular cue module (for example at the root of the repository, or any sub-directory), then reference that configuration in the environment.
Our tutorials donโt use this method yet: we should change them so that they do.
Creating this as a placeholder, will add details later :) cc @samalba
Signed-off-by: jffarge
I removed the plan.module field of my environment in dagger edit. After that, all commands against that environment failed, including dagger edit. This made it impossible to revert my error, short of running git checkout -f โ values.yaml. I tried editing the file manually but that caused sops errors.
- Calls
netlify buildto support netlify's native features (build plugins, netlify.toml, remote config, etc...) - If there is nothign to do,
netlify buildwon't do anything and can be run safely everytime without slowing down the deployment.
Fixes #696
Changes
It will now be possible to execute CI in parallel
- Fixes English mistakes in docs_101 (using Grammarly)
- Specify
dagger -eeverywheredaggeris being used
Fixes #740
Fixes #739 (even though Kubes part is handled in PR#720)
Signed-off-by: Guillaume de Rouville
Fixes #719
I've commented the docker.#Local tests because it has missing inputs (and it isn't implemented properly yet)
Signed-off-by: Guillaume de Rouville
Bumps prismjs from 1.23.0 to 1.24.0.
Release notes
Sourced from prismjs's releases.
v1.24.0
Release 1.24.0
Changelog
Sourced from prismjs's changelog.
1.24.0 (2021-06-27)
New components
CFScript (#2771) b0a6ec85
ChaiScript (#2706) 3f7d7453
COBOL (#2800) 7e5f78ff
Coq (#2803) 41e25d3c
CSV (#2794) f9b69528
DOT (Graphviz) (#2690) 1f91868e
False (#2802) 99a21dc5
ICU Message Format (#2745) bf4e7ba9
Idris (#2755) e9314415
Jexl (#2764) 7e51b99c
KuMir (ะัะะธั)...
Maven support
- The idea is based on js/yarn
- Tested using a simple spring boot project
- Added a simple documentation page
Signed-off-by: Alvise
- Wording improvement on 102/103 (using Grammarly)
- Clarify some ambiguous sentences
Signed-off-by: Guillaume de Rouville
Bumps google.golang.org/grpc from 1.38.0 to 1.39.0.
Release notes
Sourced from google.golang.org/grpc's releases.
Release 1.39.0
Behavior Changes
csds: return empty response if xds client is not set (#4505)
metadata: convert keys to lowercase in FromContext() (#4416)
New Features
xds: add GetServiceInfo to GRPCServer (#4507)
Special Thanks: @โamenzhinsky
xds: add test-only injection of xds config to client and server (#4476)
server: allow PreparedMsg...
The interface and behavior is identical to S3.
Signed-off-by: Scott Lewis-Kelly
@solomon#4104, I know why @rawkode's push to netlify failed. It's not linked to his key, but because of the naming of his site, which had to be globally unique.
Netlify package currently doesn't print errors properly, which is very very confusing. This made me crazy yesterday while moving packages. This PR fixes it
Signed-off-by: Guillaume de Rouville
Changes
There is a bug in the CI, if a pod has a name longer than 53 chars, he can't run.
I've reduce the number of chars in chart name to avoid that bug.
Taking from the Discord chat , there are few questions as a first time users to Dagger and I think FAQ is a great place for that
- What are Dagger Use cases
- What is not the goal of Dagger
- Dager vs Terraform
- is Dagger a PAAS?
- How to integrate with other cloud providers ?
- Dagger vs Other tools like Ketch, Epinio
- Is Dagger limited to Kubernetes ?
And will keep on adding more relevant questions if there are tutorials then point links to them directly. or if an answer mig...
So after I was able to deploy to Civo Kubernetes (which is K3s based) There was s thought of integration and I am ver well onboard with this.
@TomChv Following #756 issue, same implementation as Andrea's one. Could you please review ?
Signed-off-by: Guillaume de Rouville
[dagger/dagger] Pull request opened: #762 \[Installation\] \- Improve Installation for Windows Users
- What this feature does:
Windows users should be able to use the dagger binary getting a similar experience to the one proposed for Linux in the docs. - What has been changed: the feature implements a PowerShell script similar to
install.shlogic. More specifically I've updatedinstall.mdand addedinstall.ps1
I'm not sure if the URL releases.dagger.io is currently pointing at the content of GH repo or something else so the documented steps may need a review.
**...
Bumps @docusaurus/preset-classic from 2.0.0-beta.0 to 2.0.0-beta.3.
Release notes
Sourced from @โdocusaurus/preset-classic's releases.
v2.0.0-beta.3
2.0.0-beta.3 (2021-06-30)
:rocket: New Feature
docusaurus-theme-classic
#5092 feat(v2): add icon to external footer links (@โlex111)
:bug: Bug Fix
docusaurus-theme-classic
#5080 fix(v2): classic theme - semantic correct anchors links (@โAuHau)
#5081 fi...
Bumps @docusaurus/core from 2.0.0-beta.2 to 2.0.0-beta.3.
Release notes
Sourced from @โdocusaurus/core's releases.
v2.0.0-beta.3
2.0.0-beta.3 (2021-06-30)
:rocket: New Feature
docusaurus-theme-classic
#5092 feat(v2): add icon to external footer links (@โlex111)
:bug: Bug Fix
docusaurus-theme-classic
#5080 fix(v2): classic theme - semantic correct anchors links (@โAuHau)
#5081 fix(v2): restore previous scroll posi...
Dagger has a concept of โcomponentsโ (sometimes also called โrelaysโ, terminology is in flux) to describe the basic building block of a Dagger configuration. Each component corresponds to one tool or service in your delivery workflow, represented as a node in the DAG.
Today these โcomponentsโ are abstract concepts.
- They are not present in the CLI
- They are not present in the Cue APIs
- They are implicitly present in the Dagger source code, but defined simply as โa cue value with a ...
In the past, a killer feature of Dagger (and its early prototypes) was the ability to create micro-staging environments on demand. For example, a CI script could create a separate environment for each pull request, on the fly, without tedious manual intervention. This highlights a natural strength of Dagger, and naturally complements traditional gitops tools and workflow, which are constrained by the static/manual nature of git-driven operations.
To summarize our current approach to on-dem...
link doe not work in readme, is it still active or valid ?
Fixes #699
Still need to update docs
Signed-off-by: Andrea Luzzardi
WIP: universe vendoring
Rather than injecting universe at runtime, this change will vendor
alpha.dagger.io in cue.mod directly.
Fixes #700
Depends on #772
โฏโฏโฏ mkdir foo
โฏโฏโฏ dagger new foo --module foo
โฏโฏโฏ tree foo
foo
โโโ cue.mod
โโโ module.cue
โโโ pkg
โโโ alpha.dagger.io
โโโ alpine
โ โโโ alpine.cue
docker.#Push definition has a check to see if auth is set:
if auth != _|_ {
op.#DockerLogin & {
"target": target
username: auth.username
secret: auth.secret
}
},
However, auth is not optional, which makes this verification obsolete.
It seems to be a useful check: when rewriting the "local build and push of docker images" for the Kubernetes doc, without this PR, the secret and username values have to be set to "". It's very annoying
WARNING: `dock...
Following #772, I moved the plans out of cue.mod (due to a misunderstanding on 102/108. This time, shall be good.
Partially fixes #742. Kubernetes doc will directly enforce it, so no need to change now. Last blocking point on the closure of #742 will be Tiho's doc
Signed-off-by: Guillaume de Rouville
Signed-off-by: jffarge
Signed-off-by: jffarge
Signed-off-by: Alvise
Problems
There is actually a data race condition in the CI on docker.#Push test found in PR #628.
Check the data race below :
# 12:14PM INF TestPush.push.push | completed duration=2s
# 12:14PM INF TestPush.push.ref | computing
# 12:14PM INF TestPush.push.digest | computing
# 12:14PM ERR TestPush.push.ref | failed: failed to solve: rpc error: code = Unknown desc = failed to authorize: failed to fetch oauth token: unexpected status: 401 Unauthorized duration=2.1s
# 1...
Changes
Add yaml for new kubernetes tutorial.
:bulb: Depend on https://github.com/dagger/dagger/pull/720
https://github.com/dagger/dagger/blob/main/docs/learn/101-use.md#the-outputs
The outputs
The plan defines one or several outputs. They can show helpful information at the end of the deployment. That's how we read the deploy url at the end of the deployment. Here is the command to list all inputs:
inputs > outputs
Bumps github.com/spf13/cobra from 1.1.3 to 1.2.1.
Release notes
Sourced from github.com/spf13/cobra's releases.
v1.2.1
Bug fixes
Quickfix for spf13/cobra#1437 after v1.2.0 where parallel use of the cmd.RegisterFlagCompletionFunc() (and subsequent map) now works correctly and flag completions now work again
v1.2.0 - The completions release
:stars: v1.2.0 - The completions release
Welcome to v1.2.0 of Cobra! This release focuses on code completions, several...
There are to many packages that still use the old @dagger(input) tag to specify an input.
We must migrate all inputs from this below
#Def: {
input: string @dagger(input)
optionalInput?: string @dagger(input)
}
to this
#Def: {
input: string & dagger.#Input
optionalInput: string & dagger.#Input | *null
}
According to @shykes, use null instead of ? looks better when you check the input's value.
Eg below
if optionalInput...
TL;DR
- Add a new ssh package to interact with a remote host
- Add
ssh.#Filesdefinition to upload files to remote host - Add volumes management in
docker/compose.#Compose
Changes
It's now possible to uses volumes with #Compose.
Those volumes will be upload to the remote host. This way, the remote docker engine can use it when executing the docker-compose.yaml.
I've add another test to verify that behavior.
To handle volumes, I've also added a new package name...
Needed for internal infra for simplifying the release process (gh #702).
Git package didn't have the keepGitDir option.
However, this option was directly leveraged in the tests using op.FetchGit.
Leveraging the keepGitDir option with the subdir command led to incompatible list lengths (1 and 2) issue.
To fix it, we could either add ... every time we would use op.#FetchGit
#up: [
op.#FetchGit & {
keepGitDir: true
},
... <-- like that
]
...
Fixes #376
Example:
โฏ cat .dagger/env/playground/plan/main.cue
package playground
import (
"alpha.dagger.io/dagger/op"
)
version: {
string
#up: [
op.#FetchHTTP & {
url: "https://releases.dagger.io/dagger/latest_version"
checksum: "sha256:a309e76efa4550350a29cd41e6cbaf434ae94317bb6652297c79b691230e6abd"
mode: 0o600
uid: 1000
gid: 1000
},
op.#Export & {
source: "/latest_version"
},
]
} @dagger(output)
โฏ dagger up
2:32...
https://github.com/accurics/terrascan
Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
500+ Policies for security best practices
Scanning of Terraform (HCL2)
Scanning of Kubernetes (JSON/YAML), Helm v3, and Kustomize v3
Support for AWS, Azure, GCP, Kubernetes and GitHub
Idea to scan dagger application before deploying
we are planning to add cue support (https://github.com/accurics/terra...
Changes
According to @aluzzardi, generate a random tag isn't needed anymore so we remote that part of the 107 doc
Aim of PR:
- Automatic test suite for documentation
- Codeblocs are inlined from cue files
@slumbering, we added the remark-code-import plugin to Docusaurus. Is that ok with you ?
@TomChv, you can directly continue on my branch, let's split 107 to avoid conflict
Signed-off-by: Guillaume de Rouville
Changes
Kustomize has a bug when you replace a digest when both tag and digest.
Eg:
$ cat kustomization.yaml
resources: ["deployment.yaml", "service.yaml"]
images:
- name: "public.ecr.aws/j7f8d3t2/todoapp@sha256:6224c86267a798e98de9bfe5f98eaa3f55a1adfcd6757acc59e593f2ccdb37f2"
newName: "localhost:5000/kind:test-kind-azkestizysbx@sha256:cb8d92518b876a3fe15a23f7c071290dfbad5028...
Bumps color-string from 1.5.3 to 1.5.5.
Release notes
Sourced from color-string's releases.
1.5.5 (Patch/Security Release) - hwb() ReDos patch (low-severity)
Release notes copied verbatim from the commit message, which can be found here: 0789e21284c33d89ebc4ab4ca6f759b9375ac9d3
Discovered by Yeting Li, c/o Colin Ife via Snyk.io.
A ReDos (Regular Expression Denial of Service) vulnerability
was responsibly disclosed to me via email by Colin on
Mar 5 2...
Bumps url-parse from 1.4.7 to 1.5.1.
Commits
eb6d9f5 [dist] 1.5.1
750d8e8 [fix] Fixes relative path resolving #199 #200 (#201)
3ac7774 [test] Make test consistent for browser testing
267a0c6 [dist] 1.5.0
d1e7e88 [security] More backslash fixes (#197)
d99bf4c [ignore] Remove npm-debug.log from .gitignore
422c8b5 [pkg] Replace nyc with c8
933809d [pkg] Move coveralls to dev dependencies
190b216 [pkg] Add .npmrc
ce3783f [test] Do not test on all availa...
A Dagger workspace should be configured by one simple file, instead of a combination of special directories, yaml files and cue modules like today. This requires changing a design change in 3 parts:
- System design: change the contents and lifecycle of workspaces and environments
- CLI design: change
daggersubcommands to reflect the change in system design - Developer experience: change how and when Dagger users are required to become full-blown Cue developers
The desired result...
This PR moves the plan outside of .dagger and fixes the out-of-date stdlib calls for voteapp and hello app.
Integration tests won't be here on this repo but on dagger's doc one.
@shykes, I didn't know where to put the files, so I moved the plan at the root of each example
Signed-off-by: Guillaume de Rouville
Currently most core/ops tests are based off dagger compute. Instead, we should follow the same convention as universe:
- initialize a workspace in
tests - create one environment per test
/cc @TomChv @grouville
Overview
One exciting application of Cue is to generate custom user interfaces. In the context of Dagger, an environment could define a custom control panel, to:
- Prompt user for settings, secrets, and artifacts
- Present additional information and instructions
- Render useful outputs like URL of deployed application, red/green health status..
First prototype
We implemented this feature in an prototype prior to Dagger. Here are a few screenshots.
- The Cue configuration ...
Currently dagger up creates and starts 3 distinct buildkit sessions:
- One for input scanning
- One for environment.Up
- One for output scanning
This forces the copy of the workspace to buildkit 3 times (as well as CUE parsing, universe vendoring, and other heavy operations):
$ cd universe
$ dagger up -e go -l debug
6:17PM DBG [internal] source | #1 Local /Users/al/work/dagger/universe
[...]
6:17PM DBG [internal] source | #2 Local /Users/al/work/dagger/universe
[...]
6...
Bumps sass from 1.35.1 to 1.35.2.
Release notes
Sourced from sass's releases.
Dart Sass 1.35.2
To install Sass 1.35.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Potentially breaking bug fix: Properly throw an error for Unicode ranges that have too many ?s after hexadecimal digits, such as U+12345??.
Potentially breaking bug fix: Fixed a bug where certain local var...
Works, but backward compatibility issue atm because of differences with release versions
@samalba, it's github's automatic revert
Reverts dagger/examples#32
This is a proposal for one particular solution to the problem of state persistence in Dagger.
Problem
Sometimes, a component in the DAG needs to remember what they did earlier - usually so that they can undo it. This feature is called โpersistent stateโ or โstateโ for short. For example, a component which creates Amazon S3 buckets needs persistent state to remember which buckets they created, in case the user wants to destroy them later.
One obvious use of persistent state is the ...
When reviewing the netlify package, I generated a personal token which randomly started with --.
This led to the encounter of this parsing error:
$ dagger input secret site.netlify.account.token "--lyYc_hJ*********************" -e multibucket
failed to execute command: unknown flag: ---lyYc_hJPbP**
- The same happens with all inputs, Viper doesn't seem to parse them properly/doesn't seem to understand that an input is expected
For release, doc entirely checked + updated regarding last plan changes
Signed-off-by: Guillaume de Rouville
This is a WIP about supporting Azure in dagger.
the overall goal of this PR is to support push and delete into Azure Storage accounts.
Other PR incoming later once this one is merged around AKS and so on :)
any feedback highly appreciated
PS: I will to squash I know :)
Signed-off-by: Tihomir Jovicic
This is the initial commit for adding Azure Support as per our discussion here
With this PR the user must be able to:
- Configure an azure account/subscription to which the deployment has to be done.
- Create a resource group.
- Create a storage account.
I don't have the test cases at this time but will be submitting them soon.
Implemented inputs validation:
- Evaluate cue code before persisting inputs (fixes #287)
- Handle wrong input type (fixes #618)
- Handle setting input which does not exist (fixes #617)
- Added integration tests
- Small refacto for using only one buildkit client (fixes #798)
Problem
To access core Dagger features from Cue, I must find and import several different Cue packages across different import locations. It is not clear when I should use which import location, or why they are split the way they are.
This makes it harder to become a proficient Dagger developer.
Solution
- Simplify how core cue packages are organized: reduce the number of import locations if possible, make rules simpler if possible
- Clarify how core cue packages are organi...
Follow-up to PR #808
- Implements validation of
dagger input edit- checks for invalid or wrong types
Follow-up to PR #808 - I broke the no-cache behavior unintentionally. This PR restores the behavior.
Maybe I am missing something, but right now what I see in Dagger is similar to Hashicorp waypoint:
- cli for developers to quickly deploy with minimal fuss
- platform agnostic
- automatic creation of URLs for environments (Saas) version
- opinionated syntax (hcl vs cue)
I think the docs should say what are the pros/cons compared to waypoint.
Another similar project is garden.io which is even more comprehensive as it also has test phases, holds the dependencies between services, ha...
The comparison with CI systems says that dagger can be be used from within CI. But there is no info on how to do that
Maybe a new "dagger ci" command is needed? Or we assume we use the up command?
Also see https://docs.tilt.dev/ci.html
Java developers will be confused as this project already exists
If this is already known, and accepted already, fine be me.
But since the project is now in early stages it is the perfect time to rename it.
A typical problem when developing a new integration for Dagger, is differentiating private and public fields. Currently we use @dagger(input) and @dagger(output) to designate public fields. The remaining fields are considered private. Instead, it would be better to use the standard Cue notation for hidden fields: _foo.
Partially addresses #702
Signed-off-by: Tihomir Jovicic
I have two environments:
-WSL
-Windows 10
I created an empty workspace (no .cue files), did dagger init and dagger new 'myworkplace'
Expected result:
user@laptop:/mnt/c/Users/user/.alefesta/dg-orig$ dagger up
1:46PM FTL system | failed to up environment: plan config: no CUE files in .
on WSL this works fine (Linux binary) on Windows I get:
panic: illegal character U+0073 's' in escape sequence:
1:28
goroutine 44 [running]:
go.dagger.io/dagge...
Context
The current DX of writing dagger configs in CUE and using packages is overall pretty good (of course it needs some cleanup, but it's good enough).
However, when adding code to the mix (as in, when creating a package that contains code), the experience is lacking.
This is an epic issue, will split into more focused issues at some point.
Mixing CUE and Code
Currently the only way to add code to a package is to embed it as a CUE string, which comes with many limitati...
It's pretty hard to write a dagger config from scratch and remember the APIs (e.g. inputs/outputs).
I typically start somewhere (e.g. copy some existing files), then look at the source code of the packages I want to use to figure out what the inputs and outputs are. I never manage to write a config without looking somewhere else (e.g. open source package or use dagger doc).
Having a Language Server would provide:
- Syntax Highlighting, syntax checking, on the fly errors, ...
- Auto ...
When a config works, it's awesome. When it doesn't, the troubleshooting experience is far from perfect.
Partial Run for Debugging
Dagger can only run all or nothing: when one component of the config misbehaves, there's no way to make some tweaks and re-run only that part.
The current experience requires a lot of trial and error: comment out everything but the component you're debugging, get errors about unused imports, fix those, then get errors about undefined identifiers (th...
I love this idea from the Tailscale docs. Each article has a unique ID that is reflected in the URL. This decouples the contents individual articles from the overall structure of the docs. This is a great idea because the overall structure will almost certainly change over time. If the URL of the article is tied to the structure, changing structure is a big problem because you either 1) break URLs or 2) carry confusing and burdensome legacy URLs. On the other hand ...
Signed-off-by: Tihomir Jovicic
Links with a target blank has associate svg. This svg should only appair in the sidebar.
Changes
This package takes an artifact and and zip it.
The zip's name can be set.
:bulb: This package is necessary to develop the lambda package asked in #785.
Our tracking dilemma in a nutshell:
- As open-source developers, we need more data about how our software is used, in order to make it better. Solliciting users directly, for example with live interviews and surveys, is useful but not sufficient: we also need tracking. This need is even more acute in the early stages of development, when the final form of the product is not yet known, and can only be found by a fast-moving feedback loop between product changes and user feedback.
- As op...
Bumps github.com/moby/buildkit from 0.9.0-rc1 to 0.9.0-rc2.
Release notes
Sourced from github.com/moby/buildkit's releases.
v0.9.0-rc2
Welcome to the 0.9.0-rc2 release of buildkit!
This is a pre-release of buildkit
Notable Changes
Fix progress regression in v0.9.0-rc1`#2254
Experimental support for Github Actions remote cache backend via type=gha #1974
Outgoing TCP connections are now limited to 4 per registry. Metadata requests get one extra connection ...
Bumps github.com/moby/buildkit from 0.9.0-rc1 to 0.9.0.
Release notes
Sourced from github.com/moby/buildkit's releases.
v0.9.0
Notable Changes
Builtin Dockerfile frontend defaults to v1.3.0 including support for RUN --network and Here-documents in labs channel. Dockerfile changelog Dockerfile labs changelog
Experimental support for Github Actions remote cache backend via type=gha #1974 Docs
Add support for subdirectories when building from Git sourc...
- automatically detect vendored buildkit version
- move versioning info into the version package
- telemetry support (fixes #832)
I suggest to modify the compose file with the right buildkit version as well
Fixes broken link from โgetting startedโ to โinstallโ.
As reported on Discord, see below:

Link to local markdown file instead of final slug location, so that docusaurus can catch broken links at build.
Signed-off-by: Andrea Luzzardi
Note: this proposal is competitive with #793. It borrows some ideas and adds some new ones.
Overview
The DAG flow is a proposed modification of the Dagger user experience, affecting the following areas:
- System design: change the contents and lifecycle of workspaces and environments
- CLI: change dagger subcommands to reflect the change in system design
- Filesystem layout: change what files and directories are stored on the userโs filesystem
- Developer experience: ch...
Repro
- Clone this repo
- cd todoapp
dagger up- Process emits error that "jq is not installed", process exits
Output: https://gist.github.com/benjaminxscott/c59218cba81a577364d56b44829f0011
Running dagger up a second time results in successful execution and environment deployment
Environment
Linux container on ChromeOS Version 91.0.4472.114 (Official Build) (64-bit)
dagger version
dagger 0.1.0-alpha.20 (8462963) linux/amd64
uname -a
Linux penguin 5.4...
Background
POC to support embedding files in a CUE configuration (see #277)
This is needed for External Code Support #147, which in turn will allow to Support writing code in other languages #824.
This is largely a POC to explore what can be done, the syntax is a placeholder to get started.
Primitive
There's a special dagger.#Artifact named "context" which maps to the CUE package's directory (should have been named dagger.#Context but I run into issues -- right ...
- Add support for buildkit cache export/import
- Enable GHA cache for universe test (using buildkit v0.9 GHA support)
Bumps sass from 1.35.2 to 1.36.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.36.0
To install Sass 1.36.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Dart API
Added compileToResult(), compileStringToResult(), compileToResultAsync(), and compileStringToResultAsync() methods. These are intended to replace the existing compile*() methods, which are now d...
While working with dagger, I felt the need to process some variables inside a shell script, and reinject them into the cue tree.
As of now, it is only possible with the low level op operations, as os.#File only retrieves strings. An os.#Json or os.#Export might be necessary if we want os.#Container to become mainstream
Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.0.0-RC1 to 1.0.0-RC2.
Release notes
Sourced from go.opentelemetry.io/otel/exporters/jaeger's releases.
Release v1.0.0-RC2
Added
Added WithOSDescription resource configuration option to set OS (Operating System) description resource attribute (os.description). (#1840)
Added WithOS resource configuration option to set all OS (Operating System) resource attributes at once. (#1840)
Adde...
Bumps go.opentelemetry.io/otel/sdk from 1.0.0-RC1 to 1.0.0-RC2.
Release notes
Sourced from go.opentelemetry.io/otel/sdk's releases.
Release v1.0.0-RC2
Added
Added WithOSDescription resource configuration option to set OS (Operating System) description resource attribute (os.description). (#1840)
Added WithOS resource configuration option to set all OS (Operating System) resource attributes at once. (#1840)
Added the WithRetry option to ...
Bumps go.opentelemetry.io/otel from 1.0.0-RC1 to 1.0.0-RC2.
Release notes
Sourced from go.opentelemetry.io/otel's releases.
Release v1.0.0-RC2
Added
Added WithOSDescription resource configuration option to set OS (Operating System) description resource attribute (os.description). (#1840)
Added WithOS resource configuration option to set all OS (Operating System) resource attributes at once. (#1840)
Added the WithRetry option to the go.o...
Bumps go.opentelemetry.io/otel/trace from 1.0.0-RC1 to 1.0.0-RC2.
Release notes
Sourced from go.opentelemetry.io/otel/trace's releases.
Release v1.0.0-RC2
Added
Added WithOSDescription resource configuration option to set OS (Operating System) description resource attribute (os.description). (#1840)
Added WithOS resource configuration option to set all OS (Operating System) resource attributes at once. (#1840)
Added the WithRetry option...
Problem
Currently, if you want to import a new package in your Dagger app you have to manually c/p directories in cue.mod/pkg, as explained in https://docs.dagger.io/1010/dev-cue-package/. We are proposing a minimal package manager that can install and any public package.
Design proposal
Plan is to add a new mod command that works similar to Go one:
It can install a package using a git sha or tag:
dagger mod get github.com/me/my-cue-package // uses the latest sha...
Currently whit dagger you can fetch any git repository that is in public by using git.#Repository.
But if you want to fetch a private repository or repository that is on an organization you can't.
So I wonder if it's possible to add the feature to fetch also those repository.
Thank's
When developing a bigger use case using Dagger with @TomChv, we encountered performance related problems.
The aim of this issue to regroup all the hacks we will need to implement until Cue's core team fixes the origin of the lag (cf. https://github.com/cue-lang/cue/issues/803)
- All related issues are happening on a
cue evalcommand and lead to a very long compute time - Definitions are the heart of the problem
- The bug is always related to a field with
multiple values, reducing ...
As seen with @TomChv and @aluzzardi: on big configs, Cue copies the definitions a lot of times, especially when field with multiple options are present.
Here, the PR hacks the op.#Exec definition by replacing "tmpfs" | "cache" | {from: _, path: string | *"/"} | {secret: _} to mount: [string]: { _ ... }
This hack turned a 100s.
cue evalinto a 1s one.
Signed-off-by: Guillaume de Rouville
Changes
Fix typo in CONTRIBUTING.md
Bumps @docusaurus/core from 2.0.0-beta.2 to 2.0.0-beta.4.
Release notes
Sourced from @โdocusaurus/core's releases.
v2.0.0-beta.4
2.0.0-beta.4 (2021-07-28)
:rocket: New Feature
docusaurus-theme-classic
#4912 feat(v2): add back to top button (@โlex111)
docusaurus-init
#5235 feat: docusaurus.new + improve StackBlitz playground integration (@โslorber)
docusaurus-plugin-content-docs, docusaurus-theme-classic, docusaur...
Bumps github.com/docker/buildx from 0.6.0 to 0.6.1.
Release notes
Sourced from github.com/docker/buildx's releases.
v0.6.1
Notable changes
Set ConfigFile to parse compose files with bake (#704)
Duplicated progress env var (#693)
Should ignore nil client (#686)
Contributors
CrazyMax
Devin Bayer
Morlay
Commits
260d07a Merge pull request #704 from crazy-max/use-compose-config-file
9aa8f09 Set ConfigFile to parse compose files with bake
0363b67 Merge ...
Hi there,
I was going through the getting started guide but ran into some issues that I wasn't sure how to debug. Any guidance would be helpful!
3:08PM INF funnyName | computing environment=s3
3:08PM INF source | computing environment=s3
3:08PM INF source | completed environment=s3 duration=0s
3:08PM INF app.source | computing environment=s3
3:08PM INF app.source | completed duration=0s environment=s3
3:08PM INF app.ctr | computing ...
Signed-off-by: Tihomir Jovicic
When creating a package, dagger breaks when it includes a "-" in it's name.
$ dagger edit -e example-code
3:09PM FTL system | invalid input: plan config: import failed: import failed: build constraints exclude all CUE files in github.com/test/aws/secret-manager:
cue.mod/usr/github.com/test/aws/secret-manager/code.cue: package is secret, want secret-manager # <= package implemented here
cue.mod/usr/github.com/test/aws/secret-manager/secret.cue: package is secret, want secret-man...
As seen with @TomChv and @aluzzardi: on big configs, Cue copies the definitions a lot of times, especially when fields with multiple options are present.
Here, the PR hacks the os.#Container definition by replacing image: dagger.#Artifact | *#DefaultImage to image?: dagger.#Artifact
This hack turned a 4s cue eval into a >1s one.
Signed-off-by: Guillaume de Rouville
Bumps sass from 1.36.0 to 1.37.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.37.0
To install Sass 1.37.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Dart API
Potentially breaking bug fix: SassNumber.asSlash, SassNumber.withSlash(), and SassNumber.withoutSlash() have been marked as @internal. They were never intended to be used outside the sass package....
Bumps amplitude-js from 8.3.1 to 8.4.0.
Release notes
Sourced from amplitude-js's releases.
v8.4.0
8.4.0 (2021-07-30)
Features
Add error callback (#413) (c50429d)
Changelog
Sourced from amplitude-js's changelog.
8.4.0 (2021-07-30)
Features
Add error callback (#413) (c50429d)
Commits
564f656 chore(release): 8.4.0 [skip ci]
c50429d feat: Add error callback (#413)
See full diff in compare view
[![Dependabot compatibility sco...
Bumps sass from 1.36.0 to 1.37.2.
Release notes
Sourced from sass's releases.
Dart Sass 1.37.2
To install Sass 1.37.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
No user-visible changes.
See the full changelog for changes in earlier releases.
Dart Sass 1.37.1
To install Sass 1.37.1, download one of the packages below and add it to your PATH, or see the Sass website for...
Bumps sass from 1.36.0 to 1.37.5.
Release notes
Sourced from sass's releases.
Dart Sass 1.37.5
To install Sass 1.37.5, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
No user-visible changes.
See the full changelog for changes in earlier releases.
Dart Sass 1.37.4
To install Sass 1.37.4, download one of the packages below and add it to your PATH, or see the Sass website for...
Request
During a user interview with @grouville, the user told us that it would be cool to give environment variable as input.
I told him to just send it as a string (e.g: dagger input text key "$MY_ENV_VAR") but it wasn't his objective, we wanted to directly use the environment, not a static value.
I think that could be a good idea to add this feature to dagger
What I would like to see
// Cue file
import (
"alpha.dagger.io/dagger"
)
key: dagger.#Input & ...
Request
When we were developing the serverless package with @grouville, we developed definitions with many inputs.
But most of them were already prefilled with default values. However, when we run dagger input list, all those inputs were displayed.
E.g
dagger input list
Input Value Set by user Description
repo dagger.#Artifact ...
This is the initial commit for adding Azure Support as per our discussion here
With this PR the user must be able to:
- Configure an azure account/subscription to which the deployment has to be done.
- Create a resource group.
Bumps path-parse from 1.0.6 to 1.0.7.
Commits
See full diff in compare view
Dependabot will resolve any conflicts...
Here is the automatic test suite for the doc (apart 1009), fully rebased and up-to-date
Basic attempt to integrate ArgoCD with some app commands.
Implementation example:
package main
import (
"alpha.dagger.io/dagger"
"alpha.dagger.io/argocd/app"
)
argocd: {
// ArgoCD server
server: string @dagger(input)
// ArgoCD authentication token
token: dagger.#Secret @dagger(input)
// ArgoCD project
project: "my-project"
}
// ArgoCD application
application: "my-app"
// Get ArgoCD app
get: app.#Get & {
"config": argocd,
"application":...
Problem
I found an issue with dagger input git command.
If we check the usage if input with dagger input git --help, here's the result
$ dagger input git --help
Add a git repository as input artifact
Usage:
dagger input git TARGET REMOTE [REF] [SUBDIR] [flags]
....
We see that we can add aSUBDIR argument. But that arg isn't used in reality.
Reproduce
With the following cue file
package example
import (
"alpha.dagger.io/dagger"
"alp...
This addresses an issue with s3.#Object caching. Right now, when using a cached layer, aws s3 sync does not upload anything, despite the content having changed. This changeset uses cp by default but still optionally support sync.
Bumps amplitude-js from 8.3.1 to 8.5.0.
Release notes
Sourced from amplitude-js's releases.
v8.5.0
8.5.0 (2021-08-13)
Bug Fixes
LGTM return fix for falsy str (#416) (f744fe7)
Features
add sendBeacon support (#412) (0517038)
_v8.5.0
No release notes provided.
v8.4.0
8.4.0 (2021-07-30)
Features
Add error callback (#413) (c50429d)
Changelog
Sourced from amplitude-js's changelog.
8.5.0 (2021-08-13)
Bug Fixes
LGTM return fix for fal...
Currently, dagger's CLI doesn't accept a bool type as input:
โ universe git:(docs-test) โ dagger input
Manage an environment's inputs
Usage:
dagger input [command]
Available Commands:
container Add a container image as input artifact
dir Add a local directory as input artifact
git Add a git repository as input artifact
json Add a JSON input
list List the inputs of an environment
secret Add an encrypted input secret
...
This PR adds support for creating a storage account under a resource group in a specific subscription.
Signed-off-by: Sujay Pillai
Bumps url-parse from 1.5.1 to 1.5.3.
Commits
ad44493 [dist] 1.5.3
c798461 [fix] Fix host parsing for file URLs (#210)
201034b [dist] 1.5.2
2d9ac2c [fix] Sanitize only special URLs (#209)
fb128af [fix] Use 'null' as origin for non special URLs
fed6d9e [fix] Add a leading slash only if the URL is special
94872e7 [fix] Do not incorrectly set the slashes property to true
81ab967 [fix] Ignore slashes after the protocol for special URLs
ee22050 [ci] Use G...
TL;DR
Solve #884
Changes
- Fix subdir issue
- Add test
TL;DR
- solve #874
Changes
Add new argument --show-optional to dagger input list.
Now by default, dagger input list will only show required input.
To get all inputs (including those with default value), you can use
that new argument.
Test has been updated to support changes.
Demo
With the docker-compose test from universe.
# Path
pwd
dagger/universe
# Default input list
dagger -e docker-compose input list
Input ...
Bumps sass from 1.36.0 to 1.38.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.38.0
To install Sass 1.38.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
In expanded mode, emit characters in Unicode private-use areas as escape sequences rather than literal characters.
Fix a bug where quotes would be omitted for an attribute selector whose value was a sing...
Any search term entered is blocked on the spinner, see below:
Purpose
After we created the serverless package with @grouville to deploy lambda functions to AWS.
It would be really nice to create a new package to deploy containerized applications to the cloud.
First, we should create a high-level abstraction on top of AWS App runner.
Requirement
- Deploy application from git repository or image from ECR
- App configuration (port, runtime, environment)
- Config deployment (scaling, res...
This PR closes #587.
This is a backward compatible, full integration of Localstack inside our AWS test suite.
In order to have it backward compatible, I added a new parameter to the aws.#Config definition.
Currently it's a hack, as we don't accept bool input types from the CLI yet (cf. #888).
This implementation is important: we have lots of AWS definitions untested on the CI because of privilege issues.
Everything works, eks has not been ported yet, as I still don't have the Kub...
Restructured the compile logic to happen on the CLI instead of the
BuildKit frontend.
- Avoid uploading the entire workspace to BuildKit on every compilation
- Let the CUE loader scan the files instead of going through the
BuildKit filesystem gRPC APIs.
Signed-off-by: Andrea Luzzardi
Changes
Fix dead links from installation line in the README.
Bumps google.golang.org/grpc from 1.39.0 to 1.40.0.
Release notes
Sourced from google.golang.org/grpc's releases.
Release 1.40.0
Behavior Changes
balancer: client channel no longer connects to idle subchannels that are returned by the pickers; LB policy should call SubConn.Connect instead. (#4579)
This change is in line with existing documentation stating the balancer must call Connect on idle SubConns in order for them to connect, and is preparation for...
Changes
There was a hack in version.go that was hiding unused flag from that command.
The problem is that the effect has spread to all commands.
The original purpose was simply to hide those flags when user tip dagger version --help.
I've removed that trick to correctly display all flags because it's important for users to know how select an environment and configure log format.
Example
Before
dagger input list --help
List the inputs of an environment...
Bumps github.com/containerd/console from 1.0.2 to 1.0.3.
Release notes
Sourced from github.com/containerd/console's releases.
v1.0.3
Notable changes:
Add support for z/OS (#46, thanks to @โnajohnsn)
Stop using pkg/errors (#54, thanks to @โkolyshkin)
Commits
b5cb846 Merge pull request #55 from AkihiroSuda/fix-ci
e700792 Fix CI
05dadd9 Stop using pkg/errors
2298a9c Merge pull request #46 from najohnsn/master
7097449 Console test on z/OS
c4672c3 A...
Changes
Waiting group did not correctly handle in case of error.
By putting wg.Wait() in defer, we will wait until all goroutine has finished before closing the channel.
Request
Extend existing Git integration to have more interactions with a Git repository.
It would be useful to have the ability to create new commits and to push them to a remote repository.
Requirement
Request
Initial ArgoCD implementation with app support.
Requirement
Notes
There is an existing PR (https://github.com/dagger/dagger/pull/883) which will be refactored and moved to a dedicated repository when package manager becomes available.
TL;DR
Solve #873.
Use environment var as input was a feature asked by many users.
It's now possible with the new option env.
You can add an environment var with dagger input env to use it in Dagger.
Changes
- Add
envInputtype as input type - Add input and compile method for
envInput - Update
dager inputCLI to take env as parameter - Add tests on input env
The universe test suite seems to have an env isolation issue between concurrent runs.
Repro case: comment all the universe tests apart
@test "cue-sanity-check" {
dagger -e sanity-check up
}
@test "os" {
dagger -e os up
}
@test "go" {
dagger -e go up
}
@test "js/yarn" {
dagger -e js-yarn up
}
@test "java/maven" {
dagger -e java-maven up
}
@test "alpine" {
dagger -e alpine up
}
@test "os.#Container" {
dagger -e os-container up...
Signed-off-by: Tom Chauveau
Bumps start-server-and-test from 1.12.5 to 1.13.1.
Release notes
Sourced from start-server-and-test's releases.
v1.13.1
1.13.1 (2021-07-26)
Bug Fixes
deps: update dependency wait-on to v6 (#307) (eeaaf92)
v1.13.0
1.13.0 (2021-07-22)
Features
api: adds check for http status 304 (#311) (c0adf51)
v1.12.6
1.12.6 (2021-07-06)
Bug Fixes
deps: update dependency debug to v4.3.2 (3b17fb0)
Commits
eeaaf92 fix(deps): update dependency wait...
Bumps cypress-localstorage-commands from 1.4.5 to 1.5.0.
Release notes
Sourced from cypress-localstorage-commands's releases.
Support Cypress 8.x
Added
chore(#330): Use Cypress v8 in E2E tests. Add Cypress v8.x to peerDependencies
Changed
chore(deps): Update devDependencies
Changelog
Sourced from cypress-localstorage-commands's changelog.
[1.5.0] - 2021-07-21
Added
chore(#330): Use Cypress v8 in E2E tests. Add Cypress v...
Bumps concurrently from 6.2.0 to 6.2.1.
Release notes
Sourced from concurrently's releases.
v6.2.1
Fix hanging issue after using programmatic API to read from stdin (#252, #253)
Big kudos to @โbrandonchinn178 for finding and fixing this! ๐ ๐
Correctly reexport flow controllers (#278)
Commits
0bc490f 6.2.1
c295062 Stop reading from stdin after programmatic API finishes (#253)
07a7de1 Update links to new GH org and remove travis+appveyo...
Bumps cypress from 7.6.0 to 7.7.0.
Release notes
Sourced from cypress's releases.
7.7.0
Released 07/07/2021
Features:
When using experimentalStudio, Cypress Studio can now copy all commands generated to your clipboard. Addressed in #16912.
Bugfixes:
Cypress now respects preventScroll options passed to element.focus() calls within the application under test. Fixes #15294.
Using .contains(0) will now show the zero in the Command Log. Fixes #1119.
Cy...
Bumps github.com/docker/buildx from 0.6.1 to 0.6.2.
Release notes
Sourced from github.com/docker/buildx's releases.
v0.6.2
Notable changes
Fix connection error showing up in some SSH configurations #741
Commits
de7dfb9 Merge pull request #743 from tonistiigi/v0.6-client-ctx
43e51fd use long-running context for client initialization
See full diff in compare view
[ to take longer to fire its load event in some
circumstances....
Signed-off-by: jffarge
TL;DR
Implements & closes #855
Changes
I've added secret management to op.#FetchGit definition to fetch private repository through a PAT.
It's now implemented and tested.
I also did a little refactor to retrieve secret for cue file, it's now a reusable function that should be util in the future.
:warning: Minor issue
It wasn't possible for me to add that test in tests/ops because we are only using dagger compute for those tests but it doesn't handle `dagge...
Bumps @docusaurus/core from 2.0.0-beta.4 to 2.0.0-beta.5.
Release notes
Sourced from @โdocusaurus/core's releases.
v2.0.0-beta.5
2.0.0-beta.5 (2021-08-26)
:rocket: New Feature
docusaurus-init, docusaurus-mdx-loader, docusaurus-plugin-content-blog, docusaurus-plugin-content-docs, docusaurus-theme-bootstrap, docusaurus-theme-classic, docusaurus-utils-validation
#5396 feat(plugin-blog): multi-authors support + authors.ym...
WIP: missing integration tests
Fixes #495
Bumps cypress from 8.3.0 to 8.3.1.
Release notes
Sourced from cypress's releases.
8.3.1
Released 08/27/2021
Performance:
Projects will now open much faster on MacOS Big Sur with improved browser
detection performance. Fixes
#17773.
Bugfixes:
Fixed a regression in 8.3.0 where the
correct exit code would not be issued during cypress run-ct while running in
the Electron browser. Fixes
#17752 and
#17885.
Fixed a regression in 8.3.0 where
Cypress would...
Signed-off-by: jffarge
The command tree is not install by default on Mac or Windows OS (only on Linux).
This branch will be deleted after some tests
Signed-off-by: Guillaume de Rouville
Bumps sass from 1.38.1 to 1.38.2.
Release notes
Sourced from sass's releases.
Dart Sass 1.38.2
To install Sass 1.38.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
No user-visible changes
See the full changelog for changes in earlier releases.
Changelog
Sourced from sass's changelog.
1.38.2
No user-visible changes
Commits
57ea9f1 Expose getters indicating which...
Signed-off-by: Tihomir Jovicic
TL;DR
- Use
dagger.#Secretinop.#PushContainerdefinition
Changes
- Update solver struct to expose
inputStore - Update DockerLogin in
pipeline.goto retrieves secrets - Update
op.#PushContainerto usedagger.#Secret - Update
op.#PushContainertests - Update
dockerpackage to usedagger.#Secret - Update
docker.#Pushtests
:warning: Issues
When I was updating test, I saw that to push to ECR or GCR, we retrieve a token that we send to `op.#P...
Localstack tests were breaking the doc due to: https://github.com/localstack/awscli-local/issues/44.
The current fix is not to use the latest version, and reuse the awslocal-cli 0.14. This PR also includes some changes to implementation of the setup_file bats helper.
Due to the previous fails, the CI timeout-minutes has been set to 20 minutes, to avoid spending too much in case of failure. It currently takes about 13 minutes, so it shouldn't interfere atm
Signed-off-by: Guillaume d...
[dagger/dagger] Pull request opened: #931 localstack tests: convert back str input hack to bool type
LocalStack tests were implemented before the bool input type integration.
We had to find a trick to make it work :
This PR cleans it by converting aws.#Config.localMode from string | *null to bool | *false, and the tests (aws-ecr-localstack,aws-s3-localstack) accordingly.
Signed-off-by: Guillaume de Rouville
Bumps github.com/docker/buildx from 0.6.2 to 0.6.3.
Release notes
Sourced from github.com/docker/buildx's releases.
v0.6.3
Notable changes
Fix buildkit state volume location for Windows clients #751
Commits
266c0ea Merge pull request #752 from tonistiigi/v0.6-mount-path-fix
0b320fa github: fix running ci in version branches
944fd44 container-driver: fix volume destination for cache
See full diff in compare view
[
:rocket: New Feature
docusaurus-plugin-content-blog, docusaurus-theme-classic
#5428 feat: adds blog archive route (@โgabrielcsapo)
docusaurus-theme-classic, docusaurus-theme-common
#5462 feat: on back navigation, close mobile sidebar (@โslorber)
#5445 feat: Add d...
Bumps sass from 1.38.1 to 1.39.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.39.0
To install Sass 1.39.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
JS API
Add a charset option that controls whether or not Sass emits a @charset/BOM for non-ASCII stylesheets.
See the full changelog for changes in earlier releases.
Dart Sass 1.38.2
To install Sass 1.38.2, ...
Sometimes the implicit dependency of the dag is not enough, because a component A does not have any useful output for component B. However A must be executed before B.
In such a scenario, it would be useful to have the ability to define a dependancy explicitly.
Feedback from @benja-M-1
- [ ] The part of the logs that are grayed-out are actually very useful and should be highlighted (e.g. Name of the missing input).
- [ ] Grouping logs by pipeline (#up) instead of displaying them realtime would be more useful. It's a mess to associate each log line to its corresponding pipeline.
- [ ] Auto-collapse logs for a pipeline that was successful, usually only errors are useful.
Because of those issues, JSON logs are often more useful than formatted...
Bumps go.opentelemetry.io/otel/trace from 1.0.0-RC1 to 1.0.0-RC3.
Release notes
Sourced from go.opentelemetry.io/otel/trace's releases.
Release v1.0.0-RC3
1.0.0-RC3 - 2021-09-03
Added
Added ErrorHandlerFunc to use a function as an "go.opentelemetry.io/otel".ErrorHandler. (#2149)
Added "go.opentelemetry.io/otel/trace".WithStackTrace option to add a stack trace when using span.RecordError or when panic is handled in sp...
Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.0.0-RC1 to 1.0.0-RC3.
Release notes
Sourced from go.opentelemetry.io/otel/exporters/jaeger's releases.
Release v1.0.0-RC3
1.0.0-RC3 - 2021-09-03
Added
Added ErrorHandlerFunc to use a function as an "go.opentelemetry.io/otel".ErrorHandler. (#2149)
Added "go.opentelemetry.io/otel/trace".WithStackTrace option to add a stack trace when using span.RecordError or when ...
Bumps go.opentelemetry.io/otel/sdk from 1.0.0-RC1 to 1.0.0-RC3.
Release notes
Sourced from go.opentelemetry.io/otel/sdk's releases.
Release v1.0.0-RC3
1.0.0-RC3 - 2021-09-03
Added
Added ErrorHandlerFunc to use a function as an "go.opentelemetry.io/otel".ErrorHandler. (#2149)
Added "go.opentelemetry.io/otel/trace".WithStackTrace option to add a stack trace when using span.RecordError or when panic is handled in span.E...
This PR adds the ability to create and update secrets in GCP Security Manager.
The command that deals with gcloud is heavily inspired by the AWS implementation made by @grouville on dagger-serverless
Hello dagger team ๐๐ป
When running dagger up with a plan that creates a GCP resource (a cloud run service for example), I wish it enables the service when run for the first time. Otherwise it fails.
This PR provides the possibility to add environment variables to a deployed cloud run service.
If a users correctly sets region to a valid GCP region, a warning would be
presented (but is hidden by -q):
) gcloud config set compute/zone asia-northeast1
Updated property [compute/zone].
WARNING: asia-northeast1 is not a valid zone. Run `gcloud compute zones list` to get all zones.
This makes it consistent with AWS where a region is set. However, an optional
zone field could also be added to gcp.#Config, which would be used to
(conditionally?) set the zone.
...
Changes
- Add a new
urlfield tokubernetes.#Resourcesto deploy an application from remote url - Update kubernetes package with new
dagger.#Inputdefinition - Update test files
The current page 404 for docs.dagger.io is broken :

One of our user encountered breaking CIs with azure because of :
Treating warnings as errors because process.env.CI = true.
Most CI servers set it automatically.
Failed to compile.
./src/App.js
Line 110:7: The element ul has an implicit role of list. Defining this explicitly is redundant and should be avoided jsx-a11y/no-redundant-roles
The CI broke because of this output.
After checking with @slumbering, we can safely remove this role, as it's an example app
Sig...
Signed-off-by: jffarge
Bumps url-parse from 1.5.1 to 1.5.3.
Commits
ad44493 [dist] 1.5.3
c798461 [fix] Fix host parsing for file URLs (#210)
201034b [dist] 1.5.2
2d9ac2c [fix] Sanitize only special URLs (#209)
fb128af [fix] Use 'null' as origin for non special URLs
fed6d9e [fix] Add a leading slash only if the URL is special
94872e7 [fix] Do not incorrectly set the slashes property to true
81ab967 [fix] Ignore slashes after the protocol for special URLs
ee22050 [ci] Use G...
Bumps axios from 0.21.1 to 0.21.4.
Release notes
Sourced from axios's releases.
v0.21.4
0.21.4 (September 6, 2021)
Fixes and Functionality:
Fixing JSON transform when data is stringified. Providing backward compatibility and complying to the JSON RFC standard (#4020)
Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:
Jay
Guillaume Fortaine
Yusuke Kawasaki
Dmitriy Mozgovoy
v0.21....
Bumps go.opentelemetry.io/otel from 1.0.0-RC1 to 1.0.0-RC3.
Release notes
Sourced from go.opentelemetry.io/otel's releases.
Release v1.0.0-RC3
1.0.0-RC3 - 2021-09-03
Added
Added ErrorHandlerFunc to use a function as an "go.opentelemetry.io/otel".ErrorHandler. (#2149)
Added "go.opentelemetry.io/otel/trace".WithStackTrace option to add a stack trace when using span.RecordError or when panic is handled in span.End. (#21...
Bumps filippo.io/age from 1.0.0-rc.3 to 1.0.0.
Release notes
Sourced from filippo.io/age's releases.
age v1.0.0 ๐
ageโpronounced [aษกeฬ], like the Italian โagheโโis a simple, modern and secure file encryption tool, format, and Go library.
It features small explicit keys, no config options, and UNIX-style composability.
$ age-keygen -o key.txt
Public key: age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p
$ tar cvz ~/data | age -r age1ql3z7hj...
Add the cue.mod folder inside the todoapp, to match the new way of initializing environments
Signed-off-by: Guillaume de Rouville
- Change to be merged in parallel to https://github.com/dagger/examples/pull/41
Several users have been confused with the cue init part of the doc's tutorials.
This PR removes them and explains the go-to way of initializing the cue modules : through the dagger init command
Signed-off-by: Guillaume de Rouville
I have been working on #818, as it is a task that doesn't require much reflexion. While porting private fields as hidden cue fields. I realized that some pipeline became partially working.
Here is a simple, failing repro case. To make it work, transform _hash to hash:
package main
import (
"alpha.dagger.io/alpine"
"alpha.dagger.io/dagger"
"alpha.dagger.io/os"
)
TestHiddenValue: {
// Compute a value
ctr: os.#Container & {
image: alpine.#Image
command: #...
Bumps amplitude-js from 8.5.0 to 8.6.0.
Release notes
Sourced from amplitude-js's releases.
v8.6.0
8.6.0 (2021-09-08)
Features
Mobile device model support (#425) (d06f5c6)
Changelog
Sourced from amplitude-js's changelog.
8.6.0 (2021-09-08)
Features
Mobile device model support (#425) (d06f5c6)
Commits
0902896 chore(release): 8.6.0 [skip ci]
d06f5c6 feat: Mobile device model support (#425)
f3f3245 docs: fix docs for clearStorage...
Bumps github.com/rs/zerolog from 1.23.0 to 1.25.0.
Commits
65adfd8 Make Fields method accept both map and slice (#352)
cdd7417 Allow arbitrary negative levels (#350)
fe93100 Make RemoteAddrHandler copy the RemoteAddr untouched (#347)
be6f6fd chore(ci) : update dependencies (#345)
d92a906 Allow user configuration of which logger to return from Ctx() (#343)
fad20d8 docs: sampler typo (#342)
164ec91 Add logr implementation to README and json.RawMessage to Field...
Signed-off-by: Sujay Pillai
Adding support to create an azure static webapp with the source code hosted in a github repo. This would create an azure resource of type Microsoft.Web/staticSites linked to a github repo and github actions configured to it.
Here is the sample test run locally:
dagger up
11:50AM INF TestSuffix.out | computing environment=azstaticwebapp
11:50AM INF TestSuffix.out | completed environment=azstaticwebapp duration=3.5s
11:50AM INF TestRG.ctr | co...
CC @fair salmon @frosty smelt ๐ฅณ
Bumps sass from 1.38.1 to 1.39.2.
Release notes
Sourced from sass's releases.
Dart Sass 1.39.2
To install Sass 1.39.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Fix a bug where configuring with @use ... with would throw an error when that variable was defined in a module that also contained @forward ... with.
See the full changelog for changes in earlier releases.
D...
Overview
There is no Cue schema defining a Dagger environment: any Cue configuration is a valid Dagger configuration. This is both good and bad.
Good: Dagger is fully compatible with the nascent Cue ecosystem, which ensures that as the Cue package ecosystem grows and matures, Dagger developers automatically benefit.
Bad: there is no Cue API for Dagger-specific metadata about an environment. For example:
- environment name and description
- environment version
- runtime requirem...
Example:
image: docker.#Build & {
"source": source,
"args": GENERATE_SOURCEMAP: "true"
}
Added a special case for when the output is a string:
Before:
dagger output list
Output Value Description
ctr1.out """\n I am container 1\n \n """ -
ctr2.out """\n I am container 2\n \n """ -
After:
dagger output list
Output Value Description
ctr1.out I am container 1 -
ctr2.out I am container 2 -
Signed-off-by: Kazumichi Yamamoto
Problem
Dagger has a feature called inputs and outputs which serves several purposes:
-
Identify data produced and consumed by a Dagger environment at runtime. Fields marked as inputs may receive data from external sources. Fields marked as outputs may be sent to external consumers.
-
Provide missing information about the "call convention" of a Cue definition. Just like a Go function has inputs (arguments) and outputs (return values), a Cue definition has inputs (fields set by the "ca...
- Add
dockerfileto#Build - Refactor
#ImageFromDockerfileto use#Build(I don't know if it should be deprecated) - Add missing test for build args on
#Build
The command dagger input dir src xxxx -e prod hangs forever when xxxx doesn't exist.
Fixes #972
Signed-off-by: Guillaume de Rouville
Currently the aws.#Config requires the AWS access and secret keys be provided as dagger.#Secrets, in effect making them "hardcoded" into the dagger workspace/environment. For teams who use long-term credentials directly, at best this will prove inconvenient when rotating credentials, at worst it could create a security issue in that credentials could easily be committed to a repo. For teams with a more advanced workflow that requires temporary credentials based on role assumption or fede...
Bumps sass from 1.38.1 to 1.40.1.
Release notes
Sourced from sass's releases.
Dart Sass 1.40.1
To install Sass 1.40.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Potentially breaking bug fix: min() and max() expressions outside of calculations now behave the same way they did in 1.39.2, returning unquoted strings if they contain no Sass-specific features and callin...
Bumps cypress from 8.3.0 to 8.4.0.
Release notes
Sourced from cypress's releases.
8.4.0
Released 09/13/2021
Features:
When the URL contains non-ASCII characters, you can use the new decode
option of cy.url() to decode it. Addresses
#17399.
Bugfixes:
Cypress now better handles situations where the extension was installed in a
read-only location. Fixes
#3852.
A clearer error message is now thrown for .check() or .uncheck() when
there are no matching...
Dagger tutorials guide you through the use and creation of various Dagger environments. The names we chose for those environments are confusing users.
Currently the names are:
Feedback so far (f...
Temporary fix to allow dagger #Secret on docker.#Build args
Usage example:
// NPM token
npmToken: dagger.#Input & {dagger.#Secret}
image: docker.#Build & {
"source": source,
args: NPM_TOKEN: npmToken
args: FOO: "bar"
}
Update scheduling url in the docs
Bumps sass from 1.38.1 to 1.41.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.41.0
To install Sass 1.41.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Calculation values can now be combined with strings using the + operator. This was an error in 1.40.0, but this broke stylesheets that were relying on $value + "" expressions to generically conve...
When using dagger doc there should be an option to show optional fields. Like --show-optional.
For some packages like alpha.dagger.io/kubernetes/helm, you need to see the optional fields to actually learn how to use the package.
It could also be an additional column to the text/md output. Like:
| Name | Type | Required | Description ...
Placeholder. Accessing a local docker engine in a secure way would be very useful, for onboarding especially.
There is code already merged for this, but not enabled because of unresolved security concerns.
WIP: Still needs more content but wanted to get this into github
Signed-off-by: Richard Jones
Implement the socket primitive. This will allow to accept the docker socket as input to run containers locally.
Summary:
- Add
dagger.#Socketprimitive:thesocket: dagger.#Socket & dagger.#Input - Sockets can be mounted in exec:
mount: "/mysocket.sock": socket: thesocket - Sockets can be passed as inputs in the CLI:
dagger input socket thesocket /var/run/mysocket.sock
Example: Use the primitive to run docker info on the local docker engine
package main
...
This is a minimal rephrasing to emphasize that CI is not a CI system, but instead helps make CI systems portable and more efficient.
When the dagger-buildkitd container is not started, the dagger up is blocking indefinitely and you have to send SIGTERM signals to stop it.
We should check that the buildkit daemon is active and if not stop the command and print an error stating that the server (or the daemon) is not active or is unavailable.
Bumps amplitude-js from 8.6.0 to 8.7.0.
Changelog
Sourced from amplitude-js's changelog.
8.7.0 (2021-09-16)
Features
add cross origin resource policy header (#426) (709078f)
Commits
e010d3e chore(release): 8.7.0 [skip ci]
709078f feat: add cross origin resource policy header (#426)
See full diff in compare view
[ functions in calculations, because they could potentially be replaced with sub-expressions that might need to be parenthesized.
See the full changelog for changes in earli...
If you try to do something like that:
testValue: string & dagger.#Input // value is `hello`
test: {
testMarshal: yaml.Marshal({
"testValue": testValue
})
}
you get hit with this error:
failed to compile inputs: error in call to encoding/yaml.Marshal: yaml: unsupported node "hello" (*ast.BasicLit)
To work around this issue you have to interpolate the input in a string like so:
testValue: string & dagger.#Input // value is `hello`...
Currently kubeconfig in packages are regular strings.
Since kubeconfig contains sensitive information, I think they should be secrets to avoid having to push the kubeconfig in clear text to a git repository.
Bumps cypress from 8.4.0 to 8.4.1.
Release notes
Sourced from cypress's releases.
8.4.1
Released 09/17/2021
Bugfixes:
Cypress will no longer crash when setting up a project to record to the
Dashboard or viewing the runs or record key for a previously set up project.
Fixes #18129.
The branch collected for Drone CI now correctly reflects the source PR branch
for showing in the Cypress Dashboard. Fixes
#17860.
Commits
32b9f93 release 8.4.1 [skip c...
Bumps github.com/spf13/viper from 1.8.1 to 1.9.0.
Release notes
Sourced from github.com/spf13/viper's releases.
v1.9.0
This is a maintenance release primarily containing minor fixes and improvements.
Changes
Added
Experimental new encoding layer
Add support for tfvars files
Fixed
Writing hidden files with no extension
InConfig processing paths
In addition to the above changes, this release comes with tons of minor improvements, documentation changes an...
Bumps prismjs from 1.24.0 to 1.25.0.
Release notes
Sourced from prismjs's releases.
v1.25.0
Release 1.25.0
v1.24.1
Release 1.24.1
Changelog
Sourced from prismjs's changelog.
1.25.0 (2021-09-16)
New components
AviSynth (#3071) 746a4b1a
Avro IDL (#3051) 87e5a376
Bicep (#3027) c1dce998
GAP (CAS) (#3054) 23cd9b65
GN (#3062) 4f97b82b
Hoon (#2978) ea776756
Kusto (#3068) e008ea05
Magma (CAS) (#3055) a1b67ce3
MAXScript (#3060) 4fbdd2f8
Mermaid (#3050) 148c1e...
Overview
Dagger is too complicated to use. All the ingredients are there for a game-changing user experience, but it is buried in layers of incremental trial and error.
This proposal describes an leaner version of the dagger CLI, with the same core features but packaged in a different UI and API.
Objectives
The desired results are:
- a simpler design: less code, less concepts, etc.
- a streamlined user experience: more consistency between the different parts; remove ...
Renamed @dagger(input) and @dagger(output) to dagger.#Input and dagger.#Output respectively.
This removes all @dagger(input) and @dagger(output) attributes in favor of corresponding definitions.
First pull request so feel free to give me feedback about the naming and the code structure.
This pull request will change the way we check for the buildkit as currently we are using the image version of the buildkit container with docker inspect.
Now we keep using the docker inspect but use a more complete format to retrieve multiple information at once (cheaper and more efficient to do this in the same place), then it will be extracted into a BuildkitInformation struct
Then we ...
Bumps sass from 1.41.1 to 1.42.0.
Release notes
Sourced from sass's releases.
Dart Sass 1.42.0
To install Sass 1.42.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
min() and max() expressions are once again parsed as calculations as long as they contain only syntax that's allowed in calculation expressions. To avoid the backwards-compatibility issues that were present...
Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.0.0-RC1 to 1.0.0.
Release notes
Sourced from go.opentelemetry.io/otel/exporters/jaeger's releases.
Release v1.0.0
This is the first stable release for the project.
This release includes an API and SDK for the tracing signal that will comply with the stability guarantees defined by the projects versioning policy.
Added
OTLP trace exporter now sets the SchemaURL field in the exported ...
Signed-off-by: Richard Jones
Bumps tmpl from 1.0.4 to 1.0.5.
Commits
See full diff in compare view
Dependabot will resolve any conflicts with this PR as ...
Signed-off-by: jffarge
TL;DR
Resolves #993
Changes
- Update
kubeconfigtype inkubernetes&helmpackage - Support multi-type for
kubeconfig - Update documentation
Bumps sass from 1.42.0 to 1.42.1.
Release notes
Sourced from sass's releases.
Dart Sass 1.42.1
To install Sass 1.42.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Fix a bug where Sass variables and function calls in calculations weren't being resolved correctly if there was a parenthesized interpolation elsewhere in the file.
See the full changelog for changes in ea...
aws-ecr tests are currently failing because of a typo (type assertion) not triggered by Cue.
localMode: TestConfig.awsConfig.localMode // Bool type
if localMode == null {}
if localMode != null {}
localModeis ofbooltype, and I was doing anullcomparison
It probably didn't break before because of the env isolation issue on the bats test suite.
Signed-off-by: Guillaume de Rouville
Netlify package doesn't have the always:true option set anymore.
It should have been deleted when being ported from up instructions to an os.#Container definition
This PR reverts it.
Signed-off-by: Guillaume de Rouville
This completely removes the term "workspace" in favor of "project"
Bumps amplitude-js from 8.7.0 to 8.8.0.
Release notes
Sourced from amplitude-js's releases.
v8.8.0
add observe tracking plan support
Changelog
Sourced from amplitude-js's changelog.
8.8.0 (2021-09-22)
Features
add observe plan options (#427) (529ad88)
Commits
94da0b6 chore(release): 8.8.0 [skip ci]
529ad88 feat: add observe plan options (#427)
See full diff in compare view
[
balancer: add ExitIdle interface to instruct the balancer to attempt to leave the IDLE state by connecting SubConns if appropriate. (#4673)
NOTICE: This method will be required by the Balancer interface in the future
Behavior Changes
xds: update xdsclient ...
Overview
Dagger requires access to a complete buildkit installation. Most modern CI systems meet this requirement by offering access to a Docker engine, which can be used to bootstrap buildkit.
This means that, in theory, existing CI systems can run Dagger without requiring additional infrastructure. This is an attractive option since it makes it easier to start using Dagger, assuming you already have a CI system.
Alternatives
There are 2 ways to run Dagger from a CI:
- ...
This allows containers to publish ports, modeled after the docker compose short form syntax
Signed-off-by: Richard Jones
Bumps concurrently from 6.2.1 to 6.2.2.
Release notes
Sourced from concurrently's releases.
v6.2.2
Remove read-pkg dependency which had a vulnerability issue (#274)
Commits
105445c 6.2.2
875d375 Fix linting
7263ffe Remove read-pkg
8bcdf7f ci: add missing parallel coverage reporting step
24e51ad Add coveralls badge to readme
b16585f ci: readd coveralls reporting
See full diff in compare view
[ command. Addresses
#757.
Cypress now captures the repository URL on Drone CI. Addresses
#18210.
Bugfixes:
The download of Cypress now respects the NO_PROXY environment variable when
one is set. Fixes
#17702.
When using a custom config file and setting it up to record to the...
Overview
Context
Dagger packages could be summarized as a collection of definitions that receive external informations via inputs, and computes them.
These inputs are being injected inside the Cue tree at runtime.
In order to differenciate an input from a generic key, we specify the ones requiring an external source of information with the @dagger(input) annotation or the dagger.#Input definition.
These Cue keys (the ones marked with annotations) are being converte...
This removed just the environment and inputs, but leaves the s3 code to be used by a new tutorial later
Signed-off-by: Richard Jones
Relaying a pain point with Terraform... that will fail validation late in the process for items which require fetching data from the cloud provider API.
- I'm working on an image_template
- I built an image with packer having a disk size of 250G
- I used TF to create a template using this image and same disk size
- I then decided I wanted a smaller disk
- I TF planned, looked correct, then TF applied
- TF deleted the existing template (expected, it is a replace)
- TF failed on...
Context
In order to benefit from Buildkit's cache, we are using the op.#FetchGit llb instruction to fetch a git repository. However, using this instruction the way we are currently doing, the origin ref links a mounted volume, not the URL provided.
Issue
This is an issue when using git commands using the ref as source (git.#Repository) and incoming ones (listing refs)
Fixes #1032
PS: The PR checks wether the .git is present (the keepgitdir is set to true), otherwise, changing the remote is useless.
Signed-off-by: Guillaume de Rouville
Most of Git packages don't check that the .git is present, leading to unclear error messages.
Most of the packages should test this condition or at least fail cleanly if that's the case.
Packages related to this issue:
#CurrentBranch#Tags#Commit
There are two points of failure, as there are two ways to add a Git repository
- The user inputs a git dir that doesn't have a
.gitinside (generally, that's when a git repo references another git repo) - The user uses th...
Bumps concurrently from 6.2.2 to 6.3.0.
Release notes
Sourced from concurrently's releases.
v6.3.0
Distribute prefix colors correctly when using npm/yarn/pnpm script expansion (#186, #210, #234, #286)
Add new option to programmatic API, prefixColors, which serves as fallback for commands without a prefixColor (#286)
Commits
08eda4f 6.3.0
ed8d792 Fix colors option when using wildcard commands (#286)
See full diff in compare view
[!...
Bumps go.opentelemetry.io/otel/trace from 1.0.0 to 1.0.1.
Changelog
Sourced from go.opentelemetry.io/otel/trace's changelog.
[1.0.1] - 2021-10-01
Fixed
json stdout exporter no longer crashes due to concurrency bug. (#2265)
[Metrics 0.24.0] - 2021-10-01
Changed
NoopMeterProvider is now private and NewNoopMeterProvider must be used to obtain a noopMeterProvider. (#2237)
The Metric SDK Export() function takes a new two-level reader inter...
Bumps go.opentelemetry.io/otel/sdk from 1.0.0 to 1.0.1.
Changelog
Sourced from go.opentelemetry.io/otel/sdk's changelog.
[1.0.1] - 2021-10-01
Fixed
json stdout exporter no longer crashes due to concurrency bug. (#2265)
[Metrics 0.24.0] - 2021-10-01
Changed
NoopMeterProvider is now private and NewNoopMeterProvider must be used to obtain a noopMeterProvider. (#2237)
The Metric SDK Export() function takes a new two-level reader interface...
Bumps github.com/moby/buildkit from 0.9.0 to 0.9.1.
Commits
966bcf4 Merge pull request #2391 from tonistiigi/v0.9-picks-20211004
ba1cf51 don't cast Value when pipe is errored
83f8183 return an error instead of panicking when failing to get edge
9a3c7aa vendor: update go-actions-cache to 4d48f2ff
f5213a5 solver: make sure previous error gets reset
bc42fdd gha: handle missing blob gracefully
121aab0 gha: handle already exist error on save
cf59036 Merge pull...
Bumps go.opentelemetry.io/otel from 1.0.0 to 1.0.1.
Changelog
Sourced from go.opentelemetry.io/otel's changelog.
[1.0.1] - 2021-10-01
Fixed
json stdout exporter no longer crashes due to concurrency bug. (#2265)
[Metrics 0.24.0] - 2021-10-01
Changed
NoopMeterProvider is now private and NewNoopMeterProvider must be used to obtain a noopMeterProvider. (#2237)
The Metric SDK Export() function takes a new two-level reader interface for ite...
Bumps go.opentelemetry.io/otel/exporters/jaeger from 1.0.0 to 1.0.1.
Changelog
Sourced from go.opentelemetry.io/otel/exporters/jaeger's changelog.
[1.0.1] - 2021-10-01
Fixed
json stdout exporter no longer crashes due to concurrency bug. (#2265)
[Metrics 0.24.0] - 2021-10-01
Changed
NoopMeterProvider is now private and NewNoopMeterProvider must be used to obtain a noopMeterProvider. (#2237)
The Metric SDK Export() function takes a new ...
ci: re-enable GHA caching
Reverts #875 since moby/buildkit#2276 is now closed.
This reorganizes docs to put "What is Cue?" under Learn
The new "Getting started" is only working if there is a local registry running. This example starts one from the local dagger config.
Use another cli version to enable other features as follows:
Config: awsConfig: aws.#Config & {
region: "us-east-2"
cliVersion: "2.1.27"
}
Now the guide "Create your first Dagger environment" is redundant with the getting started.
We should remove it from the sidebar without removing the page (so the link still exists). It seems that the only way is to implement the sidebar statically instead of relying on the auto generation. We should keep the autogenerate for the standard library though.
It would be great if Dagger could support building images with Cloud Native Buildpacks. More specifically, I'd like to integrate with Pack, which is both a Command Line Interface and a Go library.
Apart from executing the pack binary from CUE, either directly or via a custom image, there seems to be 2 ways to support this that I can see.
1. Have pack support a...
Bumps cypress from 8.5.0 to 8.6.0.
Release notes
Sourced from cypress's releases.
8.6.0
Released 10/11/2021
Features:
cy.screenshot() now accepts overwrite: true as an option to overwrite
existing screenshots with the same file name. Addresses
#7955.
cy.select([]) can now be used to clear any selected options in a multi-value
select. Addresses #4318.
Using cy.pause() when using cypress run --headed --no-exit will now pause
a test. Addresses #4044.
...
This adds support to loading artifacts (e.g. docker.#Build,
os.#Container, ...) into any arbitrary docker engine (through a
dagger.#Stream for UNIX sockets or SSH for a remote engine)
Implementation:
- Add op.#SaveImage which serializes an artifact into an arbitrary path
(docker tarball format) - Add docker.#Load which uses op.#SaveImage to serialize to disk and
executesdocker loadto load it back
Caveats: Because we're doing this in userspace rather than letting
dagger itself load t...
Using docker.#Load introduced in https://github.com/dagger/dagger/pull/1056 we should be able to simplify the Getting Started and Kubernetes tutorials. No more local registry and no more complex kind setup to allow to talk to the local registry.
/cc @grouville @talentedmrjones @TomChv
Yarn.#Package doesn't permit the safe inclusion of secrets. It is required for the build of our doc inside Dagger.
This PR enables it without breaking the logic of specifying the environment file
Signed-off-by: guillaume