dagger/tests/core/secrets/invalid/string/string.cue

package testing

import (
	"alpha.dagger.io/dagger/op"
	"alpha.dagger.io/alpine"
)

mySecret: dagger.#Secret

TestString: #up: [
	op.#Load & {
		from: alpine.#Image & {
			package: bash: true
		}
	},

	op.#Exec & {
		mount: "/secret": secret: mySecret
		args: ["true"]
	},
]
buildkit secrets support - Secrets are never exposed in plaintext in the Cue tree. `dagger query` won't dump secrets anymore, Cue errors won't contain them either. - BuildKit-native secrets support through a new `mount` type. This ensures secrets will never be part of containerd layers, buildkit cache and generally speaking will never be saved to disk in plaintext. - Updated netlify as an example - Added tests - Changed the Cue definition of a secret to: ``` @dagger(secret) id: string } ``` This is to ensure both that setting the wrong input type on a secret (e.g. `dagger input text`) will fail, and attempting to misuse the secret (e.g. interpolating, passing as an env variable, etc) will also fail properly. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> 2021-05-26 03:56:16 +02:00			`package testing`

			`import (`
stdlib: move all imports to alpha.dagger.io Signed-off-by: Solomon Hykes <solomon@dagger.io> 2021-06-23 16:31:42 +02:00			`"alpha.dagger.io/dagger/op"`
			`"alpha.dagger.io/alpine"`
buildkit secrets support - Secrets are never exposed in plaintext in the Cue tree. `dagger query` won't dump secrets anymore, Cue errors won't contain them either. - BuildKit-native secrets support through a new `mount` type. This ensures secrets will never be part of containerd layers, buildkit cache and generally speaking will never be saved to disk in plaintext. - Updated netlify as an example - Added tests - Changed the Cue definition of a secret to: ``` @dagger(secret) id: string } ``` This is to ensure both that setting the wrong input type on a secret (e.g. `dagger input text`) will fail, and attempting to misuse the secret (e.g. interpolating, passing as an env variable, etc) will also fail properly. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> 2021-05-26 03:56:16 +02:00			`)`

			`mySecret: dagger.#Secret`

			`TestString: #up: [`
			`op.#Load & {`
			`from: alpine.#Image & {`
Move pined packages to latest distro: core tests Signed-off-by: guillaume <guillaume.derouville@gmail.com> 2022-01-03 17:01:52 +01:00			`package: bash: true`
buildkit secrets support - Secrets are never exposed in plaintext in the Cue tree. `dagger query` won't dump secrets anymore, Cue errors won't contain them either. - BuildKit-native secrets support through a new `mount` type. This ensures secrets will never be part of containerd layers, buildkit cache and generally speaking will never be saved to disk in plaintext. - Updated netlify as an example - Added tests - Changed the Cue definition of a secret to: ``` @dagger(secret) id: string } ``` This is to ensure both that setting the wrong input type on a secret (e.g. `dagger input text`) will fail, and attempting to misuse the secret (e.g. interpolating, passing as an env variable, etc) will also fail properly. Signed-off-by: Andrea Luzzardi <aluzzardi@gmail.com> 2021-05-26 03:56:16 +02:00			`}`
			`},`

			`op.#Exec & {`
			`mount: "/secret": secret: mySecret`
			`args: ["true"]`
			`},`
			`]`