✔️ Deploy Preview for devel-docs-dagger-io ready!

🔨 Explore the source changes: c2a09f8ab1b7a4584d9f7694f4c96a690694011b

🔍 Inspect the deploy log: https://app.netlify.com/sites/devel-docs-dagger-io/deploys/61f43b020a7a62000792faf8

😎 Browse the preview: https://deploy-preview-1509--devel-docs-dagger-io.netlify.app

@aluzzardi @shykes I believe this is ready to 🚢

I agree the names could be better. "Decodes" kind of makes sense: you're What's really happening is that a #Secret that contains the JSON/YAML encoding of (likely) multiple secrets, is being unmarshaled into a map ( #Secret | {[string]: #Secret} // recursively

Considering that we also have other related definitions like #TransformSecrets I think it might make more sense if we had dagger.io/dagger/secrets

package secrets

import (
  "encoding/json"
)

#FromJSON: engine.#TransformSecret & {
  // engine.#TransformSecret already defines input: engine.#Secret
  #function: {
    input:  _
    output: json.Unmarshal(input)
  }
}

#FromYAML: engine.#TransformSecret & {
  #function: {
    input:  _
    output: yaml.Unmarshal(input)
  }
}

Then the use becomes:

actions: awsCreds: secrets.#FromJSON & {
 input: secrets.awsVault.contents
}

☝🏻 it actually reads plainly "secrets from json"

It says “secrets” plural, where does the “plural” part comes into action? Maybe it’s a container for grouping several secrets together? Not immediately obvious that it’s an operation that produces multiple secrets

Generally speaking if you're using something like sops or aws-vault you will likely have multiple secrets returned by a single command. Every implementation of sops I've ever seen places dozens of secrets in a single file, potentially nested several objects deep. If by chance a sops file contains a single secret you dont need this, you can exec with sops -d file.yaml echo $mySecretKey and just get the 1 secret. So its plural because that's the use case it's really needed (especially for nested secrets common in sops)

@shykes can we ?

@aluzzardi what’s our policy on squashing? This one has 7 commits.