content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# policy write The `policy write` command uploads a policy with name NAME from the contents of a local file PATH or stdin. If PATH is "-", the policy is read from stdin. Otherwise, it is loaded from the file at the given path on the local disk. For details on the policy syntax, please see the [policy documentation](/va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/policy/write.mdx | main | vault | [
0.06979487836360931,
0.05920753628015518,
-0.10036008059978485,
-0.059519942849874496,
0.0006559062749147415,
-0.037666160613298416,
0.05328122153878212,
0.020325973629951477,
0.038408130407333374,
-0.008999990299344063,
-0.00009313318150816485,
0.007477917708456516,
0.06606380641460419,
0... | -0.020157 |
# policy read The `policy read` command prints the contents and metadata of the Vault policy named NAME. If the policy does not exist, an error is returned. ## Examples Read the policy named "my-policy": ```shell-session $ vault policy read my-policy ``` ## Usage The following flags are available in addition to the [st... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/policy/read.mdx | main | vault | [
0.11082202196121216,
0.04381154850125313,
-0.11662313342094421,
-0.02788386307656765,
0.028239529579877853,
-0.04371144622564316,
0.017614325508475304,
0.011194514110684395,
-0.0035521634854376316,
0.01145201362669468,
0.03087701089680195,
-0.012156642973423004,
0.0663798525929451,
-0.0080... | -0.054512 |
# pki verify-sign This command verifies whether the listed issuer has signed the listed issued certificate. This command returns five fields of information: - `signature\_match`: was the key of the issuer used to sign the issued. - `path\_match`: the possible issuer appears in the valid certificate chain of the issued.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/verify-sign.mdx | main | vault | [
-0.054539620876312256,
0.08858524262905121,
-0.04092087224125862,
-0.011580699123442173,
0.05096441134810448,
-0.11714636534452438,
0.038454409688711166,
0.008142529986798763,
0.049680937081575394,
-0.01779438927769661,
0.020670581609010696,
-0.057575345039367676,
0.09031187742948532,
0.05... | 0.025373 |
# pki issue This command creates a intermediate certificate authority certificate signed by the `` in the ``, using the options to determine the fields on that certificate. ## Usage Usage: `vault pki issue [flags] [options]` - `[flags]` are optional arguments described below - `` is the fully qualified path of the Cert... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/issue.mdx | main | vault | [
-0.013908076100051403,
0.05000350624322891,
-0.05750344693660736,
0.011346983723342419,
0.002190516795963049,
-0.0884614959359169,
-0.067073293030262,
-0.001694723847322166,
0.026682697236537933,
-0.021438322961330414,
0.04745056852698326,
-0.04759547859430313,
0.08564461767673492,
0.06186... | -0.111744 |
# pki The `pki` command groups subcommands for interacting with Vault's [PKI Secrets Engine](/vault/docs/secrets/pki). ## Syntax Option flags for a given subcommand are provided after the subcommand, but before the arguments. ## Example health check To [health check](/vault/docs/commands/pki/health-check) a mount, use ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/index.mdx | main | vault | [
-0.0018296792404726148,
0.08653008937835693,
-0.018022483214735985,
-0.031936366111040115,
0.038300469517707825,
-0.12229467183351517,
0.04981415346264839,
0.019348250702023506,
0.012875531800091267,
-0.044192273169755936,
0.07542942464351654,
-0.056197021156549454,
0.03708053007721901,
0.... | 0.031664 |
# pki health-check The `pki health-check` command verifies the health of the given PKI secrets engine mount against an optional configuration. This runs with the permissions of the given token, reading various APIs from the mount and `/sys` against the given Vault server Mounts need to be specified with any namespaces ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/health-check.mdx | main | vault | [
0.028533373028039932,
0.054083116352558136,
-0.08848996460437775,
-0.04201142117381096,
0.02717759646475315,
-0.1306380033493042,
0.03311408683657646,
0.03560579568147659,
-0.006196199916303158,
-0.0373605452477932,
0.050318557769060135,
-0.03168868273496628,
0.034002408385276794,
0.083838... | 0.059647 |
values returned by the health check. An endpoint may occur in more than one health check and is not necessarily guaranteed to exist on the server (e.g., using wildcards to indicate all matching paths have the same result). Tabular form elides the status code, as this is meant to be consumed programatically. These corre... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/health-check.mdx | main | vault | [
0.012653880752623081,
0.025684256106615067,
-0.09393924474716187,
-0.02955538220703602,
-0.007382094860076904,
-0.054720476269721985,
0.006495470181107521,
-0.010079666040837765,
-0.037593692541122437,
0.04948798567056656,
0.046707578003406525,
-0.010058301500976086,
0.010368451476097107,
... | 0.134936 |
write` to enable CRL auto-rebuild: ```shell-session $ vault write /config/crl auto\_rebuild=true ``` ### Hardware-Backed root certificate \*\*Name\*\*: `hardware\_backed\_root` \*\*APIs\*\*: - `LIST /issuers` (unauthenticated) - `READ /issuer/:issuer\_ref` - `READ /key/:key\_ref` \*\*Config Parameters\*\*: - `enabled` ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/health-check.mdx | main | vault | [
0.005047089420258999,
0.04343452304601669,
-0.04238012805581093,
-0.02412956766784191,
-0.001102892099879682,
-0.06987584382295609,
-0.02700338140130043,
0.0027547345962375402,
0.0035409738775342703,
-0.006433290895074606,
0.02692333050072193,
-0.02224724553525448,
0.1218794658780098,
0.01... | -0.039749 |
Use [BYOC revocations](/vault/api-docs/secret/pki#revoke-certificate) to revoke certificates as needed. ### Accessibility of audit information \*\*Name\*\*: `audit\_visibility` \*\*APIs\*\*: - `READ /sys/mounts/:mount/tune` \*\*Config Parameters\*\*: - `ignored\_parameters` `(list: nil)` - a list of parameters to ignor... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/health-check.mdx | main | vault | [
0.018927335739135742,
0.15021811425685883,
-0.05643351376056671,
-0.008383020758628845,
0.0058129108510911465,
-0.054907865822315216,
0.03956502303481102,
-0.05540364608168602,
0.04710771143436432,
-0.009901576675474644,
0.037288568913936615,
-0.013114441186189651,
0.06044742465019226,
0.0... | -0.032353 |
manual run of tidy with `vault write`: ```shell-session $ vault write /tidy \ tidy\_cert\_store=true \ tidy\_revoked\_certs=true \ tidy\_acme=true \ tidy\_revocation\_queue=true \ tidy\_cross\_cluster\_revoked\_certs=true \ tidy\_revoked\_cert\_issuer\_associations=true ``` 1. Review the tidy status endpoint, `vault re... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/health-check.mdx | main | vault | [
0.0004850723489653319,
0.030560506507754326,
-0.016353439539670944,
0.03487028926610947,
-0.052504703402519226,
-0.08858512341976166,
-0.05885317549109459,
-0.012641948647797108,
-0.008421320468187332,
0.018203269690275192,
0.019524525851011276,
-0.10496256500482559,
0.1311749368906021,
0.... | -0.089158 |
# pki list-intermediates This command determines which of a list of certificates were issued by a given parent certificate. ## Usage Usage: `vault pki list-intermediates [flags] [child] [child] [child...` Lists the set of intermediate CAs issued by this parent issuer. - `[flags]` listed below determine the type of matc... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/list-intermediates.mdx | main | vault | [
-0.05219064652919769,
0.07955651730298996,
-0.030554456636309624,
-0.028089938685297966,
0.084147609770298,
-0.12586069107055664,
-0.015376443043351173,
0.003266706829890609,
0.029038073495030403,
-0.029109591618180275,
0.03234953060746193,
-0.03351166099309921,
0.06215252727270126,
0.0530... | 0.015294 |
# pki reissue Frequently, a reissued CA certificate is to be very similar to another. This command enables reissuing a CA, using an existing issuer within Vault as a template, but allowing modifications to the desired attributes. ## Usage Usage: `vault pki reissue [flags] [options]` - `[flags]` are optional arguments d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/commands/pki/reissue.mdx | main | vault | [
-0.044924937188625336,
0.09815900027751923,
-0.00629661837592721,
0.004959183745086193,
0.0006738748052157462,
-0.060942769050598145,
-0.025226468220353127,
-0.019456516951322556,
0.05441693216562271,
-0.043684687465429306,
0.06292185932397842,
0.006356383208185434,
0.04721473529934883,
0.... | -0.055538 |
# Sync secrets from Vault to Vercel Project The Vercel Project sync destination allows Vault to safely synchronize secrets as Vercel environment variables. This is a low footprint option that enables your applications to benefit from Vault-managed secrets without requiring them to connect directly with Vault. This guid... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/vercelproject.mdx | main | vault | [
0.03449035435914993,
-0.023279991000890732,
-0.0908542051911354,
-0.015553779900074005,
-0.029708076268434525,
-0.03180992975831032,
-0.03364047408103943,
0.009938743896782398,
0.04196303337812424,
-0.0474216490983963,
-0.02546243742108345,
-0.06926193833351135,
0.05843261256814003,
0.0388... | -0.123814 |
# Sync secrets from Vault to GCP Secret Manager The Google Cloud Platform (GCP) Secret Manager sync destination allows Vault to safely synchronize secrets to your GCP projects. This is a low footprint option that enables your applications to benefit from Vault-managed secrets without requiring them to connect directly ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/gcpsm.mdx | main | vault | [
-0.029240326955914497,
-0.06239239498972893,
-0.007800400722771883,
-0.04115864634513855,
-0.0671544075012207,
0.017777854576706886,
-0.03577195852994919,
-0.04546387493610382,
0.013071988709270954,
0.06280093640089035,
0.008319156244397163,
-0.03810727596282959,
0.062227725982666016,
-0.0... | -0.098593 |
automatic replication. When specifying regional keys, a key must be set for each region in the replication location list. You must specify GCP key names using the entire resource name. For example, `projects//locations//keyRings//cryptoKeys/`. GCP key names, including the `keyRings` and `cryptoKeys` segments, are case-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/gcpsm.mdx | main | vault | [
-0.010191123932600021,
-0.027460189536213875,
0.0037612474989145994,
-0.05210956186056137,
-0.07742243260145187,
-0.0008836631313897669,
0.0017171911895275116,
-0.05449759587645531,
0.036410145461559296,
0.0444454587996006,
0.019028011709451675,
-0.013457173481583595,
0.104520782828331,
-0... | -0.037788 |
to destroy. ``` 1. Execute an apply to provision the Service Account. ```shell-session $ terraform apply ``` \*\*Output:\*\* ```plaintext (...) Apply complete! Resources: 4 added, 0 changed, 0 destroyed. Outputs: sync\_service\_account\_credentials\_file = "/path/to/credentials/file/gcp-sm-sync-service-account-credenti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/gcpsm.mdx | main | vault | [
-0.06184842437505722,
0.02396032214164734,
0.018584882840514183,
-0.03660772740840912,
-0.02178136445581913,
-0.011732978746294975,
0.02693406119942665,
-0.05262022465467453,
0.02478872425854206,
0.08083351701498032,
-0.008712317794561386,
0.034839898347854614,
0.0883011743426323,
-0.01199... | -0.05704 |
# Sync secrets from Vault to GitHub The GitHub Actions sync destination allows Vault to safely synchronize secrets as GitHub organization, repository, or environment secrets. This is a low footprint option that enables your applications to benefit from Vault-managed secrets without requiring them to connect directly wi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/github.mdx | main | vault | [
0.026357220485806465,
-0.09862185269594193,
-0.10079610347747803,
0.006496077869087458,
-0.054560109972953796,
0.0038490055594593287,
-0.08310474455356598,
0.02455955743789673,
0.03313605114817619,
-0.030904164537787437,
0.031910620629787445,
0.020562972873449326,
0.0829138234257698,
-0.00... | -0.036354 |
you wish to sync with a target GitHub repository for Actions. ```shell-session $ vault kv put -mount='my-kv' my-secret key1='val1' key2='val2' ``` \*\*Output:\*\* ```plaintext ==== Secret Path ==== my-kv/data/my-secret ======= Metadata ======= Key Value --- ----- created\_time custom\_metadata deletion\_time n/a destro... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/github.mdx | main | vault | [
0.01692299172282219,
-0.03872877359390259,
-0.05999625846743584,
-0.025081142783164978,
-0.04348492994904518,
-0.0063485815189778805,
-0.029130728915333748,
-0.010889009572565556,
0.035844214260578156,
-0.0027556654531508684,
0.057320982217788696,
-0.07149075716733932,
0.07344058901071548,
... | -0.048873 |
`sys/sync/destinations/gh` endpoint to configure a GitHub destination that references your new GitHub application: ```shell-session $ vault write sys/sync/destinations/gh/ \ installation\_id= \ repository\_owner= \ repository\_name= \ app\_name= Key Value --- ----- connection\_details map[app\_config:map[app\_name:] in... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/github.mdx | main | vault | [
0.04453103616833687,
-0.05020960047841072,
-0.06731164455413818,
-0.029335590079426765,
-0.029859276488423347,
-0.05761989578604698,
0.021775536239147186,
0.022974632680416107,
-0.005403620190918446,
0.008854889310896397,
0.04363727197051048,
-0.025281913578510284,
0.08138721436262131,
0.0... | 0.005065 |
# Secrets sync @include 'alerts/enterprise-and-hcp.mdx' In certain circumstances, fetching secrets directly from Vault is impossible or impractical. To help with this challenge, Vault can maintain a one-way sync for KVv2 secrets into various destinations that are easier to access for some clients. With this, Vault rema... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/index.mdx | main | vault | [
-0.011927010491490364,
0.02054494619369507,
-0.021048342809081078,
-0.02128540724515915,
0.024655871093273163,
0.0053551471792161465,
-0.06935759633779526,
-0.052867405116558075,
0.08353455364704132,
-0.08753841370344162,
0.02646009996533394,
0.0409349724650383,
0.07837482541799545,
-0.052... | -0.05683 |
the name of synced secrets follows this format: `vault//`. The casing and delimiters may change as they are normalized according to the valid character set of each destination type. This pattern was chosen to prevent accidental name collisions and to clearly identify where the secret is coming from. Every destination a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/index.mdx | main | vault | [
-0.05278782546520233,
0.044541824609041214,
-0.006806102115660906,
-0.004781482741236687,
-0.032486364245414734,
-0.009268008172512054,
-0.012482957914471626,
-0.0744839608669281,
0.08028744906187057,
-0.0892261192202568,
0.04170800745487213,
0.01168864592909813,
0.04498028755187988,
-0.04... | -0.004821 |
the JSON is encoded as a single-value JSON-string. The `secret-key` granularity syncs each Vault key-value pair as a distinct entry at the destination. If the value itself is a list or map it is encoded as a JSON blob. Granularity can be updated. The new granularity only affects secrets newly associated with the destin... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/index.mdx | main | vault | [
-0.014438048005104065,
0.020495934411883354,
-0.06572132557630539,
-0.0006494589615613222,
-0.0010156083153560758,
-0.06620866805315018,
-0.0028720423579216003,
-0.050486452877521515,
0.009774540551006794,
-0.08216354250907898,
0.05124722793698311,
0.08706441521644592,
0.06868869811296463,
... | -0.006901 |
the allowed IP addresses and port numbers used by the sync clients to safeguard against server-side request forgery (SSRF). All special purpose IPs defined at the IANA special-purpose registry for [IPv4](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml) and [IPv6](https://www... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/index.mdx | main | vault | [
-0.06136875972151756,
0.0002426104329060763,
-0.06072331592440605,
-0.11237575858831406,
-0.03799676522612572,
-0.024909857660531998,
-0.07149002701044083,
-0.11087388545274734,
0.059603989124298096,
-0.07187184691429138,
0.007455561310052872,
0.12609802186489105,
0.010191120207309723,
0.0... | 0.053199 |
# Sync secrets from Vault to Azure Key Vault The Azure Key Vault destination enables Vault to sync and unsync secrets of your choosing into an external Azure account. When configured, Vault will actively maintain the state of each externally-synced secret in realtime. This includes sending new secrets, updating existin... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/azurekv.mdx | main | vault | [
-0.01734929531812668,
-0.07342179119586945,
-0.09996785968542099,
0.02572508715093136,
-0.0739828497171402,
0.04406261816620827,
0.007316411938518286,
-0.06605017930269241,
0.0798201635479927,
0.0679195374250412,
0.04315533861517906,
0.0266152061522007,
0.08269807696342468,
0.0156305301934... | -0.099204 |
a separate Azure Key Vault instance for Vault sync destinations. This corresponds with Microsoft's currently-recommended [best practices](https://learn.microsoft.com/en-us/azure/key-vault/general/best-practices) for managing secrets in Key Vault. Maintaining a boundary between Vault-managed secrets and other secrets th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/azurekv.mdx | main | vault | [
-0.011206964030861855,
0.01158324908465147,
-0.07205981761217117,
0.027776459231972694,
-0.04164915531873703,
0.01813729852437973,
0.030134327709674835,
-0.0683174729347229,
0.04772467538714409,
0.04601874202489853,
0.021665211766958237,
0.05976823344826698,
0.08545299619436264,
0.04615481... | -0.072274 |
# Sync secrets from Vault to AWS Secrets Manager The AWS Secrets Manager destination enables Vault to sync and unsync secrets of your choosing into an external AWS account. When configured, Vault will actively maintain the state of each externally-synced secret in near-realtime. This includes sending new secrets, updat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/awssm.mdx | main | vault | [
-0.005739766638725996,
-0.013382021337747574,
-0.08247828483581543,
0.012055748142302036,
-0.008810428902506828,
0.005645946133881807,
-0.022587941959500313,
-0.05551126226782799,
0.04925500601530075,
0.02863263338804245,
0.031233150511980057,
0.01421407051384449,
0.06504085659980774,
-0.0... | 0.003343 |
The previous examples use wildcards for the sake of brevity. We strongly recommend you use the principle of least privilege to restrict actions and resources for each use case to the minimum necessary requirements. ## Tutorial Refer to the [Vault Enterprise Secrets Sync tutorial](/vault/tutorials/enterprise/secrets-syn... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/sync/awssm.mdx | main | vault | [
-0.0006416429532691836,
0.044732823967933655,
-0.06233770772814751,
-0.0008499277173541486,
0.00021106908388901502,
-0.009425784461200237,
-0.02896694652736187,
-0.04700183495879173,
0.028323732316493988,
-0.02094407193362713,
0.006146518047899008,
-0.0007527585257776082,
0.09210020303726196... | -0.0219 |
# GCP secret import source Use the GCP Importer to read secret data from GCP Secrets Manager into your Vault instance. ## Before you start - \*\*You must know the relevant GCP credentials\*\*. You can provide the credentials as environment variables, as explicit arguments, or use dynamic credentials from an existing [G... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/import/gcpsm.mdx | main | vault | [
-0.027449818328022957,
-0.017367273569107056,
-0.04807132109999657,
0.012840797193348408,
-0.06736105680465698,
0.022991720587015152,
0.033014409244060516,
0.03342068940401077,
-0.0019836919382214546,
0.05712621286511421,
-0.008117161691188812,
-0.039056118577718735,
0.07708055526018143,
0... | -0.11801 |
# Secrets import @include 'alerts/enterprise-only.mdx' @include 'alerts/beta.mdx' Distributing sensitive information across multiple external systems creates several challenges, including: - Increased operational overhead. - Increased exposure risk from data sprawl. - Increased risk of outdated and out-of-sync informat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/import/index.mdx | main | vault | [
0.005578964948654175,
0.03422517701983452,
-0.035336364060640335,
-0.05174794793128967,
0.031967323273420334,
0.009683424606919289,
-0.06516958028078079,
0.030904170125722885,
0.014370952732861042,
-0.11676996946334839,
-0.024375079199671745,
-0.04216667264699936,
0.11838920414447784,
-0.0... | -0.020461 |
in subsequent mapping blocks. - `credentials\_file` `(string: )` - Path to a credential file with read permissions for the target system. Depending on the source system, additional information may be required. Refer to the connection documentation for your source system to determine the full set of required fields for ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/import/index.mdx | main | vault | [
-0.04718276113271713,
-0.02966224029660225,
-0.02794148586690426,
-0.062290843576192856,
-0.06105850636959076,
-0.011900684796273708,
0.01538493949919939,
0.004722075071185827,
-0.05523276329040527,
-0.03130082041025162,
-0.0036421690601855516,
-0.11246331036090851,
0.08239631354808807,
-0... | -0.034663 |
# Azure secret import source Use the Azure importer to read secret data from Azure Key Vault into your Vault instance. All secrets including expired ones will imported from the provided Azure Key Vault URI ## Before you start - \*\*You must know the relevant Azure credentials\*\*. You can provide the credentials as env... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/import/azurekv.mdx | main | vault | [
-0.029451297596096992,
-0.007599147967994213,
-0.08442020416259766,
0.027800103649497032,
-0.04689550772309303,
0.04006500542163849,
0.008832013234496117,
0.0014694019919261336,
0.015247376635670662,
0.03973604738712311,
0.004073073621839285,
-0.025936264544725418,
0.11841163784265518,
0.0... | -0.11568 |
# AWS secret import source Use the AWS importer to read secret data from AWS Secret Manager into your Vault instance. ## Before you start - \*\*You must know the relevant AWS credentials\*\*. You can provide the credentials as environment variables, as explicit arguments, or use dynamic credentials from an existing [AW... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/import/awssm.mdx | main | vault | [
-0.03628602996468544,
0.010404511354863644,
-0.11728787422180176,
0.005641331430524588,
-0.029680538922548294,
0.020915500819683075,
0.005412071943283081,
0.07088606059551239,
0.016513435170054436,
0.018331417813897133,
-0.030129076912999153,
-0.07789231836795807,
0.1151450127363205,
-0.01... | -0.100535 |
# Developer quick start This quick start will explore how to use Vault client libraries inside your application code to store and retrieve your first secret value. Vault takes the security burden away from developers by providing a secure, centralized secret store for an application’s sensitive data: credentials, certi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-started/developer-qs.mdx | main | vault | [
-0.005437126848846674,
0.04124012216925621,
-0.13300898671150208,
-0.055137749761343,
-0.017734119668602943,
-0.024681279435753822,
-0.027431420981884003,
0.07567746192216873,
-0.017830781638622284,
-0.06762310862541199,
0.0408063605427742,
0.019061198458075523,
0.06891269236803055,
-0.006... | -0.040447 |
Now, let's add the import statements for the client library to the top of the file. ```Java import org.springframework.vault.authentication.TokenAuthentication; import org.springframework.vault.client.VaultEndpoint; import org.springframework.vault.support.Versioned; import org.springframework.vault.core.VaultTemplate;... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-started/developer-qs.mdx | main | vault | [
-0.004680251702666283,
0.029623091220855713,
-0.07885134220123291,
-0.0935051217675209,
0.023620793595910072,
-0.006942028179764748,
-0.016738057136535645,
0.031188832595944405,
-0.002655068878084421,
-0.07173289358615875,
0.03171328455209732,
0.06845151633024216,
0.08227089047431946,
0.02... | -0.057802 |
secrets is as key-value pairs using the [KV secrets engine (v2)](/vault/docs/secrets/kv/kv-v2). In the code we've just added, `password` is the key in the key-value pair, and `Hashi123` is the value. We also provided the path to our secret in Vault. We will reference this path in a moment when we learn how to retrieve ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-started/developer-qs.mdx | main | vault | [
-0.03484855592250824,
0.03337058052420616,
-0.07324433326721191,
-0.007457044441252947,
-0.03935621678829193,
-0.02902083657681942,
-0.08500857651233673,
0.03643285855650902,
0.033018384128808975,
-0.037438806146383286,
0.020926544442772865,
0.004739972297102213,
0.034037649631500244,
-0.0... | -0.027279 |
# Operations quick start Start Vault in developer mode and authenticate entities, store and retrieve your first key/value secret, and test access control with policies. Running Vault in-memory with `dev` mode is insecure but useful for practicing locally. \*\*Do not use `dev` mode in production\*\*. For help managing a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-started/operations-qs.mdx | main | vault | [
0.10874014347791672,
-0.004904014989733696,
-0.08985763043165207,
-0.01851692795753479,
-0.009202598594129086,
-0.05836937949061394,
-0.048357900232076645,
0.019686995074152946,
-0.016828689724206924,
0.016968710348010063,
0.04223673418164253,
-0.009093315340578556,
0.07415256649255753,
0.... | -0.071933 |
secrets In the previous step, you wrote a password to the `kv` secrets engine using the root token. The use of the root token, and root policy, is not recommended for production environments. You can use Vault policies to control and limit access to plugin data and the operations allowed on plugin data. 1. Create a pol... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/get-started/operations-qs.mdx | main | vault | [
-0.017974643036723137,
0.033530354499816895,
-0.0910884439945221,
-0.004453417379409075,
-0.047938767820596695,
-0.005139645654708147,
-0.056481096893548965,
0.07858899980783463,
0.01703966222703457,
0.023697491735219955,
0.045079804956912994,
-0.06312429159879684,
0.06688527017831802,
0.0... | -0.052501 |
# What is Vault? Vault provides centralized, well-audited privileged access and secret management for mission-critical data whether you deploy systems on-premises, in the cloud, or in a hybrid environment. With a modular design based around a growing plugin ecosystem, Vault lets you integrate with your existing systems... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/what-is-vault.mdx | main | vault | [
0.000566031550988555,
0.009550482966005802,
-0.052847057580947876,
-0.038180410861968994,
0.02454395964741707,
-0.033882491290569305,
-0.03308229148387909,
0.058101072907447815,
0.01893748715519905,
-0.017458420246839523,
-0.018023870885372162,
0.04497348889708519,
0.05133680999279022,
0.0... | 0.027519 |
Vault Dedicated provides a Vault Enterprise cluster without the operational overhead of planning, deploying, and managing a self-hosted Vault cluster. ## How do I get Vault? You can [download Vault as a precompiled binary](http://releases.hashicorp.com/vault), install an official [Community](/vault/install) or [Enterpr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/what-is-vault.mdx | main | vault | [
0.08150119334459305,
-0.010717198252677917,
-0.048944298177957535,
-0.040859952569007874,
-0.010128548368811607,
-0.05544480308890343,
-0.08714675158262253,
-0.0007053722511045635,
0.0249563530087471,
-0.01705515943467617,
0.008661258034408092,
0.02905936725437641,
0.07745248079299927,
-0.... | -0.009561 |
# How Vault works Vault is an identity-based secrets and encryption management system that centralizes secret management, rotates old credentials, generates credentials on demand, audits client interactions, and supports regulatory compliance. It provides encryption services that are gated by authentication and authori... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/how-vault-works.mdx | main | vault | [
-0.01455887220799923,
0.039493393152952194,
-0.0479113906621933,
-0.0395677275955677,
0.004268021788448095,
-0.020659146830439568,
-0.011329533532261848,
0.016365714371204376,
0.08722424507141113,
-0.02089284546673298,
-0.05095430091023445,
0.07538019865751266,
0.04327043145895004,
-0.0053... | 0.056896 |
root key that is stored alongside all other Vault data, but is encrypted by another mechanism: the unseal key. By default, Vault uses [Shamir's Secret Sharing](https://en.wikipedia.org/wiki/Shamir%27s\_Secret\_Sharing) to split the unseal key into a configured number of shards (key shares or unseal keys). A precise num... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/how-vault-works.mdx | main | vault | [
0.004950652364641428,
-0.019756590947508812,
-0.06403284519910812,
0.01811712235212326,
-0.0025564581155776978,
-0.05935249105095863,
-0.06507443636655807,
0.02609734982252121,
0.08212989568710327,
-0.01859872229397297,
0.024253664538264275,
0.09664911031723022,
0.0802670419216156,
-0.0442... | 0.028556 |
returns the secret, the core registers it with the expiration manager and attaches a lease ID. Clients use the lease ID to renew or revoke their secret. The expiration manager automatically revokes the secret if a client allows the lease to expire. The core logs requests and responses to the audit broker, distributing ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/how-vault-works.mdx | main | vault | [
-0.02709568478167057,
0.04880594462156296,
-0.04360365495085716,
0.03494584932923317,
0.06638506799936295,
-0.0025582564994692802,
0.013913299888372421,
-0.027356116101145744,
0.1021018773317337,
0.029962165281176567,
0.042766131460666656,
0.06992000341415405,
0.031069578602910042,
-0.0067... | 0.120205 |
# Manage identities and authentication @include '/why-use-vault/manage-identities-small.mdx' ## Manage identities and entities Vault provides centralized identity management through the identity plugin so clients can use accounts with different identity providers to authenticate to Vault. The identity plugin ties authe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/identities.mdx | main | vault | [
-0.05918215215206146,
0.012665453366935253,
-0.05300267040729523,
-0.008300860412418842,
0.027787422761321068,
-0.020613184198737144,
0.06204686686396599,
-0.0017616989789530635,
0.052482299506664276,
-0.03340896964073181,
0.026301147416234016,
-0.0009896864648908377,
0.09211302548646927,
... | 0.052445 |
# Why use Vault? Modern software works because of \*\*secrets\*\*. Secrets are sensitive, discrete pieces of information like credentials, encryption keys, authentication certificates, and other critical pieces of information your applications need to run consistently and securely. Use Vault to centralizing secret mana... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/index.mdx | main | vault | [
0.027614301070570946,
0.0588151179254055,
-0.058045074343681335,
-0.06745025515556335,
0.06458651274442673,
-0.03944680839776993,
0.010710316710174084,
0.05293021723628044,
-0.04730173200368881,
-0.010405804961919785,
0.022369613870978355,
0.022349705919623375,
0.11098063737154007,
0.02719... | -0.015034 |
# Manage static secrets @include '/why-use-vault/manage-static-secrets-small.mdx' Use the key/value (`kv`) secrets engine to store and version arbitrary static secrets in Vault physical storage. Or use the `cubbyhole` secrets engine to tie an arbitrary secret to an authentication token and store it within the configure... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/static-secrets.mdx | main | vault | [
-0.005523475352674723,
0.05897561460733414,
-0.11249348521232605,
0.029949015006422997,
-0.046679362654685974,
0.005612275563180447,
-0.09495724737644196,
0.05068035051226616,
-0.016626430675387383,
-0.055900689214468,
0.024692917242646217,
-0.051803071051836014,
0.04992248862981796,
0.006... | -0.026369 |
# Secure sensitive data @include '/why-use-vault/secure-sensitive-data-small.mdx' ## Encrypt data Use Vault to deploy \*\*encryption as a service\*\* and move the burden of data encryption/decryption from your applications to Vault. With the transit plugin, Vault can encrypt and decrypt external data, essentially allow... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/sensitive-data.mdx | main | vault | [
0.016314929351210594,
0.03414996713399887,
-0.04893628507852554,
-0.008577350527048111,
0.0005135472747497261,
-0.029689494520425797,
-0.010657187551259995,
0.02592063508927822,
-0.011122229509055614,
0.027072736993432045,
0.020361682400107384,
0.018535524606704712,
0.05763090029358864,
0.... | 0.025971 |
# Support regulatory compliance @include '/why-use-vault/regulatory-compliance-small.mdx' Vault Enterprise supports HSM for devices with PKCS#11 version 2.20+ interfaces with integration libraries for Linux/amd64 platforms. Compliance support includes: - HSM-wrapped root keys - automatic unsealing with the HSM-wrapped ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/regulatory-compliance.mdx | main | vault | [
-0.004649762995541096,
0.022055720910429955,
-0.06740105897188187,
-0.08473376929759979,
0.0503532700240612,
0.011795620433986187,
-0.06685695797204971,
0.0614350400865078,
-0.05518881231546402,
-0.021457213908433914,
0.040005628019571304,
0.02865617536008358,
0.011742996983230114,
-0.0104... | 0.022029 |
# Manage 3rd-party secrets @include '/why-use-vault/manage-3p-secrets-small.mdx' ## Manage DB credentials Use available database plugins to manage static and dynamic database credentials with Vault. Plugins for static credentials map internal Vault roles 1-to-1 to usernames in a database. With static roles, Vault store... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/3rd-party-secrets.mdx | main | vault | [
-0.024229010567069054,
-0.009921061806380749,
-0.12127285450696945,
-0.033030904829502106,
-0.08876778930425644,
0.020606689155101776,
-0.010913019068539143,
0.03057820536196232,
0.02856213040649891,
-0.02414608560502529,
-0.042517486959695816,
0.05489220470190048,
0.082269586622715,
-0.02... | -0.041502 |
# Manage certificates @include '/why-use-vault/manage-certificates-small.mdx' Generate dynamic X.509 certificates without the manual process of generating a private key and CSR, submitting to a CA, and waiting the signing process to complete. Built-in authentication and authorization mechanisms in Vault provide verific... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/about-vault/why-use-vault/certificates.mdx | main | vault | [
-0.0478481650352478,
0.0798669382929802,
-0.016703840345144272,
-0.0036849388852715492,
-0.0092710480093956,
-0.053316790610551834,
-0.024267615750432014,
0.04750958830118179,
0.00461443979293108,
-0.06823386251926422,
0.03256570175290108,
-0.07327137142419815,
0.1300988793373108,
0.029866... | -0.044797 |
# Migrating From Tekton `v1alpha1` to Tekton `v1beta1` - [Changes to fields](#changes-to-fields) - [Changes to input parameters](#changes-to-input-parameters) - [Replacing `PipelineResources` with `Tasks`](#replacing-pipelineresources-with-tasks) - [Replacing a `git` resource](#replacing-a-git-resource) - [Replacing a ... | https://github.com/tektoncd/pipeline/blob/main//docs/migrating-v1alpha1-to-v1beta1.md | main | tekton | [
-0.09094594419002533,
-0.022901486605405807,
-0.021736113354563713,
-0.023135853931307793,
-0.000726774160284549,
-0.09322994202375412,
-0.035160794854164124,
0.015519721433520317,
-0.012221564538776875,
0.001421801745891571,
-0.01773512177169323,
-0.09499919414520264,
-0.01957985945045948,
... | 0.125194 |
# PipelineRuns - [PipelineRuns](#pipelineruns) - [Overview](#overview) - [Configuring a `PipelineRun`](#configuring-a-pipelinerun) - [Specifying the target `Pipeline`](#specifying-the-target-pipeline) - [Tekton Bundles](#tekton-bundles) - [Remote Pipelines](#remote-pipelines) - [Specifying Task-level `ComputeResources`... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.05716581270098686,
0.003962310496717691,
-0.07008496671915054,
-0.009251250885426998,
-0.08005522936582565,
-0.005996618885546923,
0.023944685235619545,
0.051577113568782806,
-0.0637110099196434,
0.03141644224524498,
-0.04536588490009308,
-0.11599607765674591,
0.033121395856142044,
0.03... | 0.032122 |
example](../examples/v1/pipelineruns/pipelinerun-with-pipelinespec.yaml) example displays morning and evening greetings. Once you create and execute it, you can check the logs for its `Pods`: ```bash kubectl logs $(kubectl get pods -o name | grep pipelinerun-echo-greetings-echo-good-morning) Good Morning, Bob! kubectl ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
0.02867220528423786,
0.006627495400607586,
0.021280977874994278,
0.018662070855498314,
-0.02097334899008274,
-0.020133668556809425,
0.000646547763608396,
0.0012527977814897895,
0.0548386313021183,
-0.05130492150783539,
-0.06915420293807983,
-0.07149043679237366,
-0.029250843450427055,
0.00... | 0.140777 |
don't have to go through the complexity of checking each `Pipeline` and providing only the required params. #### Parameter Enums > :seedling: \*\*`enum` is an [alpha](additional-configs.md#alpha-features) feature.\*\* The `enable-param-enum` feature flag must be set to `"true"` to enable this feature. If a `Parameter` ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.019003096967935562,
-0.0017469630111008883,
-0.1060783788561821,
-0.05399200692772865,
-0.022102905437350273,
-0.057654861360788345,
-0.017458273097872734,
0.045480772852897644,
-0.10230877250432968,
-0.006329200230538845,
-0.04543408751487732,
-0.14020909368991852,
0.0024934601970016956,... | 0.089455 |
- name: BYE value: "Bye World!" pipelineSpec: tasks: - name: echo-hello taskSpec: params: - name: HELLO type: string default: "Sasa World!" steps: - name: echo image: ubuntu script: | #!/usr/bin/env bash echo "$(params.HELLO)" ... ``` resolves to ```yaml # Successful execution of the above PipelineRun apiVersion: tekto... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.027228405699133873,
-0.000045432414481183514,
-0.07967717200517654,
-0.002378227422013879,
-0.04146376997232437,
-0.06492156535387039,
-0.00018883672601077706,
0.037515174597501755,
0.033280499279499054,
0.02942369505763054,
-0.034674834460020065,
-0.07577860355377197,
-0.0321522131562233... | 0.068371 |
write-result ``` ### Specifying custom `ServiceAccount` credentials You can execute the `Pipeline` in your `PipelineRun` with a specific set of credentials by specifying a `ServiceAccount` object name in the `serviceAccountName` field in your `PipelineRun` definition. If you do not explicitly specify this, the `TaskRun... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.00331712793558836,
-0.03808286041021347,
-0.02690790221095085,
-0.016354434192180634,
-0.12158133834600449,
-0.013775019906461239,
0.007845975458621979,
0.04149070009589195,
0.053563203662633896,
0.05292966961860657,
-0.09419672191143036,
-0.08297824114561081,
0.031521014869213104,
0.03... | 0.094329 |
executes it as user 1001. {{< tabs >}} {{% tab "v1" %}} ```yaml apiVersion: tekton.dev/v1 kind: Task metadata: name: mytask spec: steps: - name: writesomething image: ubuntu command: ["bash", "-c"] args: ["echo 'foo' > /my-cache/bar"] volumeMounts: - name: my-cache mountPath: /my-cache --- apiVersion: tekton.dev/v1 kin... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
0.051217157393693924,
0.02198909781873226,
-0.03204454481601715,
-0.01615815982222557,
-0.03942403942346573,
-0.06251580268144608,
0.02987501583993435,
0.08225634694099426,
0.012075145728886127,
0.02659549005329609,
-0.012520247139036655,
-0.07237448543310165,
-0.004160245414823294,
0.0276... | 0.010563 |
$(params.arch) tolerations: - key: "environment" operator: "Equal" value: "$(params.env)" effect: "NoSchedule" ``` #### Matrix Support with taskRunSpecs When using [`Matrix`](matrix.md) to fan out `PipelineTasks`, the `taskRunSpecs` can reference matrix parameters for dynamic pod template configuration. Each matrix com... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
0.06572841107845306,
0.021603697910904884,
-0.04599457234144211,
0.007474682759493589,
-0.05009670928120613,
0.01663876324892044,
-0.05851372331380844,
-0.02960139885544777,
0.04756469652056694,
0.02636956237256527,
-0.02508544921875,
-0.06379913538694382,
-0.043125055730342865,
-0.0187655... | 0.067997 |
executing the pipeline run, the workspaces will be interpolated during resolution. ```yaml # Successful execution of the above PipelineRun apiVersion: tekton.dev/v1 # or tekton.dev/v1beta1 kind: PipelineRun metadata: generateName: recipe-time- ... spec: pipelineSpec: ... status: completionTime: "2022-06-02T18:17:02Z" c... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.07933191955089569,
-0.011999338865280151,
-0.02344667911529541,
0.020962847396731377,
-0.05118224024772644,
-0.05884721875190735,
-0.06733006238937378,
0.015309097245335579,
0.004673718474805355,
-0.033359795808792114,
-0.032913364470005035,
-0.10122378170490265,
-0.030669251456856728,
... | 0.018802 |
`Step` at a time from the invoked `Task`, Tekton will request the compute values for CPU, memory, and ephemeral storage for each `Step` based on the [`LimitRange`](https://kubernetes.io/docs/concepts/policy/limit-range/) object(s), if present. Any `Request` or `Limit` specified by the user (on `Task` for example) will ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.03141306713223457,
0.0718575045466423,
-0.025275876745581627,
-0.01280757412314415,
-0.04162786900997162,
-0.02406296320259571,
-0.06507910043001175,
0.03185667842626572,
0.0586661659181118,
0.028400808572769165,
-0.053481027483940125,
-0.038195591419935226,
-0.020058181136846542,
-0.03... | 0.106431 |
} # 4. Uses global default (60m) taskRunSpecs: - pipelineTaskName: task-a timeout: "5m" # 1. Highest priority - overrides 8m Pipeline timeout ``` \*\*Note:\*\* `taskRunSpecs` timeouts cannot exceed pipeline-level constraints and will fail validation if they do. Example timeouts usages are as follows: Combination 1: Set... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.009485539048910141,
0.01849234476685524,
0.004856517072767019,
-0.0022849002853035927,
-0.04477166011929512,
-0.021765386685729027,
-0.07107948511838913,
-0.014603929594159126,
-0.00633638771250844,
-0.026292216032743454,
-0.030001169070601463,
-0.011726265773177147,
-0.05324871465563774,... | 0.035838 |
subfields: - `refSource`: the source from where a remote pipeline definition was fetched. - `featureFlags`: the configuration data of the `feature-flags` configmap. - `finallyStartTime`- The time at which the PipelineRun's `finally` Tasks, if any, began executing, in [RFC3339](https://tools.ietf.org/html/rfc3339) forma... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.018007738515734673,
-0.04353540390729904,
-0.024675549939274788,
0.006821627728641033,
0.032532453536987305,
-0.08012007176876068,
-0.03890182077884674,
-0.002976328134536743,
-0.00902433693408966,
0.020259225741028786,
-0.054943330585956573,
-0.009349699132144451,
-0.03404912352561951,
... | 0.14049 |
have an int suffix with format `--`. The name may vary according the logic of [`kmeta.ChildName`](https://pkg.go.dev/github.com/knative/pkg/kmeta#ChildName). Some examples: | `PipelineRun` Name | `PipelineTask` Name | `TaskRun` Names | |----------------------------------------------------------|------------------------... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.02027709037065506,
0.06818333268165588,
-0.027835214510560036,
-0.009055539965629578,
-0.11246646195650101,
-0.05293360352516174,
0.0011839867802336812,
0.09003419429063797,
-0.019639210775494576,
-0.026328247040510178,
-0.01644245535135269,
-0.10168266296386719,
0.0044052922166883945,
... | 0.074275 |
are completed normally, including executing their `retries`, but no new non-`finally` task is scheduled. `finally` tasks are executed afterwards. For example: ```yaml apiVersion: tekton.dev/v1 # or tekton.dev/v1beta1 kind: PipelineRun metadata: name: go-example-git spec: # […] status: "StoppedRunFinally" ``` ## Pending... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineruns.md | main | tekton | [
-0.038227252662181854,
-0.04359430819749832,
-0.037729233503341675,
-0.010115694254636765,
-0.0316581092774868,
-0.08455932885408401,
-0.07059460133314133,
-0.03145293518900871,
0.028822140768170357,
0.027961891144514084,
0.003720373846590519,
0.024921178817749023,
-0.05889284610748291,
0.... | 0.022793 |
# Debug - [Overview](#overview) - [Debugging TaskRuns](#debugging-taskruns) - [Adding Breakpoints](#adding-breakpoints) - [Breakpoint on Failure](#breakpoint-on-failure) - [Failure of a Step](#failure-of-a-step) - [Halting a Step on failure](#halting-a-step-on-failure) - [Exiting onfailure breakpoint](#exiting-onfailur... | https://github.com/tektoncd/pipeline/blob/main//docs/debug.md | main | tekton | [
-0.08601409196853638,
0.024513842537999153,
-0.014029699377715588,
0.007948801852762699,
0.08367552608251572,
-0.07344475388526917,
-0.019968019798398018,
0.07282797247171402,
-0.02731616608798504,
0.04173418506979942,
0.003071465529501438,
-0.11223625391721725,
-0.004828230943530798,
-0.0... | 0.128674 |
`/tekton/debug/scripts` : Contains scripts which the user can run to mark the step as a success, failure or exit the breakpoint. Shared between all the containers. `/tekton/debug/info/` : Contains information about the step. Single EmptyDir shared between all step containers, but renamed to reflect step number. eg: Ste... | https://github.com/tektoncd/pipeline/blob/main//docs/debug.md | main | tekton | [
-0.0830133780837059,
0.06947013735771179,
-0.00724331708624959,
-0.009533383883535862,
0.06209946051239967,
-0.06357557326555252,
0.0021914870012551546,
0.0905449166893959,
0.020458970218896866,
-0.0018210739362984896,
0.04344805330038071,
-0.1170932725071907,
0.010637498460710049,
-0.0180... | 0.108004 |
# Tekton Pipelines API Specification - [Tekton Pipelines API Specification](#tekton-pipelines-api-specification) - [Abstract](#abstract) - [Background](#background) - [Modifying This Specification](#modifying-this-specification) - [Resource Overview - v1](#resource-overview---v1) - [`Task`](#task) - [`Pipeline`](#pipel... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.049892671406269073,
0.07245632261037827,
-0.055652495473623276,
0.0029631757643073797,
-0.010103278793394566,
-0.0371830090880394,
0.01885800063610077,
0.038991931825876236,
-0.04519687220454216,
-0.03686036169528961,
-0.05361175537109375,
-0.11284112930297852,
-0.0035770528484135866,
0... | 0.103845 |
RECOMMENDED resource fields on the Tekton resource types. Whether a field is REQUIRED or RECOMMENDED is denoted in the "Requirement" column. Additional fields MAY be provided by particular implementations, however it is expected that most extension will be accomplished via the `metadata.labels` and `metadata.annotation... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.10814690589904785,
0.10470569133758545,
-0.048469703644514084,
-0.012581443414092064,
-0.004284742288291454,
-0.042776331305503845,
0.048714034259319305,
0.030246732756495476,
-0.01812211237847805,
-0.030016135424375534,
-0.03668603673577309,
-0.10602786391973495,
-0.010953597724437714,
... | 0.182471 |
identifying the type of resource must be supported. ## Detailed Resource Types - `v1` ### TypeMeta Derived from [Kuberentes Type Meta](https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#TypeMeta) | Field | Type | Notes | |--------------|--------|-------------------------------------------------------------------| ... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.0016253560315817595,
0.08670452237129211,
-0.01800934597849846,
-0.013003954663872719,
-0.02182019129395485,
0.018013998866081238,
-0.00676325336098671,
0.006906123831868172,
0.04397481679916382,
-0.016572019085288048,
-0.037973854690790176,
-0.09775865823030472,
-0.05688071250915527,
0... | 0.120757 |
| | `command` | []string | REQUIRED | | | `workingDir` | []string | REQUIRED | | | `env` | [][`EnvVar`](#envvar) | REQUIRED | | | `script` | string | REQUIRED | | | `securityContext` | [`SecurityContext`](#securitycontext) | REQUIRED | | ### Sidecar Specifies a list of containers to run alongside the Steps in a Task. I... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
0.00420073326677084,
0.03527078405022621,
-0.08427528291940689,
-0.006594862788915634,
-0.0061640008352696896,
0.03277309611439705,
0.0277000330388546,
0.026465119794011116,
-0.0979754626750946,
-0.04108281061053276,
0.0466708168387413,
-0.10352899134159088,
0.03447369113564491,
0.02929547... | 0.068344 |
|--------------|-------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `name` | string | REQUIRED | The name o... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.04216912388801575,
0.002213881816715002,
-0.04598136246204376,
-0.0328545868396759,
-0.0979502946138382,
0.010850106365978718,
-0.0006788154714740813,
0.0432174876332283,
-0.0005784968961961567,
-0.06115328148007393,
0.058617349714040756,
-0.0253260787576437,
-0.03295975551009178,
-0.05... | 0.064896 |
string | REQUIRED | MUST be populated by the implementation, in [RFC3339](https://tools.ietf.org/html/rfc3339). | | `completionTime` | string | REQUIRED | MUST be populated by the implementation, in [RFC3339](https://tools.ietf.org/html/rfc3339). | | `taskSpec` | [`TaskSpec`](#taskspec) | REQUIRED | | | `steps` | [][`S... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.0357380285859108,
0.005396209191530943,
0.004322399850934744,
0.04021862521767616,
-0.0408494733273983,
0.04077763110399246,
0.004950996488332748,
0.06335356086492538,
-0.06360791623592377,
-0.007401783484965563,
-0.03905816748738289,
-0.14498397707939148,
0.02363697625696659,
0.0060130... | 0.048111 |
|----------------|-----------------------------------------|-------------|------------------------------------------| | `params` | [][`Param`](#param) | REQUIRED | | | `pipelineRef` | [`PipelineRef`](#pipelineref) | RECOMMENDED | | | `pipelineSpec` | [`PipelineSpec`](#pipelinespec) | REQUIRED | | | `timeouts` | [`Timeo... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.032244015485048294,
0.02917884849011898,
-0.07377555221319199,
0.033874597400426865,
-0.03011930361390114,
-0.011985761113464832,
-0.0018408015603199601,
0.032692354172468185,
-0.052284013479948044,
-0.05707571282982826,
0.01167997345328331,
-0.05655298009514809,
-0.004959047306329012,
... | 0.015703 |
| Workspace is the name of the workspace declared by the pipeline | ### PipelineWorkspaceDeclaration | Field | Type | Requirement | Notes | |--------|--------|-------------|------------------------------------------------------------------| | `name` | string | REQUIRED | Name is the name of a workspace to be provided b... | https://github.com/tektoncd/pipeline/blob/main//docs/api-spec.md | main | tekton | [
-0.028465352952480316,
-0.0396198146045208,
-0.021162470802664757,
0.05617550015449524,
-0.05569041892886162,
-0.04059603437781334,
0.04132659733295441,
0.046095866709947586,
-0.01962321251630783,
-0.06874805688858032,
0.005657491274178028,
-0.1052807942032814,
-0.025649644434452057,
0.005... | 0.058182 |
## Replacing PipelineResources with Tasks `PipelineResources` remained in alpha while the other resource kinds were promoted to beta. Since then, \*\*`PipelineResources` have been removed\*\*. Read more about the deprecation in [TEP-0074](https://github.com/tektoncd/community/blob/main/teps/0074-deprecate-pipelineresou... | https://github.com/tektoncd/pipeline/blob/main//docs/pipelineresources.md | main | tekton | [
-0.05672143027186394,
-0.021254917606711388,
0.03102198801934719,
-0.02812805585563183,
0.019920065999031067,
-0.04931063950061798,
0.019103601574897766,
-0.023839155212044716,
-0.007202485576272011,
-0.004891699645668268,
-0.05800916999578476,
-0.013297727331519127,
-0.06607412546873093,
... | 0.07517 |
# PipelineResources > :warning: \*\*`PipelineResources` are [deprecated](deprecations.md#deprecation-table).\*\* > > Consider using replacement features instead. Read more in [documentation](migrating-v1alpha1-to-v1beta1.md#replacing-pipelineresources-with-tasks) > and [TEP-0074](https://github.com/tektoncd/community/b... | https://github.com/tektoncd/pipeline/blob/main//docs/resources.md | main | tekton | [
-0.049972884356975555,
-0.023801853880286217,
-0.010257299989461899,
-0.0992240160703659,
0.026124371215701103,
-0.04795265942811966,
-0.03907031565904617,
-0.004063203930854797,
-0.05953821912407875,
-0.01442364975810051,
-0.03863658010959625,
-0.04661896079778671,
-0.05452553182840347,
-... | 0.01655 |
can augment `Task`-only workflows with `PipelineResources` that, without them, can only be done with `Pipelines`. - For example, let's say you want to checkout a git repo for your Task to test. You have two options. First, you could use a `git` PipelineResource and add it directly to your test `Task`. Second, you could... | https://github.com/tektoncd/pipeline/blob/main//docs/resources.md | main | tekton | [
-0.10386817902326584,
-0.08049673587083817,
-0.017283959314227104,
-0.0128549225628376,
-0.048793815076351166,
-0.0661349892616272,
-0.009185616858303547,
0.051686063408851624,
-0.017545180395245552,
0.00022568176791537553,
-0.0680665522813797,
-0.03655282035470009,
-0.012577872723340988,
... | 0.007327 |
# Getting Started with Resolvers ## Introduction This guide will take you from an empty Kubernetes cluster to a functioning Tekton Pipelines installation and a PipelineRun executing with a Pipeline stored in a git repo. ## Prerequisites - A computer with [`kubectl`](https://kubernetes.io/docs/tasks/tools/#kubectl). - A... | https://github.com/tektoncd/pipeline/blob/main//docs/resolution-getting-started.md | main | tekton | [
-0.030141295865178108,
0.028375307098031044,
0.07023154199123383,
-0.028521345928311348,
-0.03592685982584953,
-0.007965846918523312,
-0.060105063021183014,
0.08921878039836884,
0.03268006443977356,
0.04365793615579605,
-0.03646668419241905,
-0.09381146728992462,
-0.004858613479882479,
0.0... | 0.046335 |
# Tekton Controller Performance Configuration Configure ThreadsPerController, QPS and Burst - [Overview](#overview) - [Performance Configuration](#performance-configuration) - [Configure Thread, QPS and Burst](#configure-thread-qps-and-burst) ## Overview --- This document will show us how to configure [tekton-pipeline-... | https://github.com/tektoncd/pipeline/blob/main//docs/tekton-controller-performance-configuration.md | main | tekton | [
-0.07371585816144943,
0.001883464283309877,
-0.11506383121013641,
-0.0234418623149395,
-0.06960459053516388,
-0.016700683161616325,
0.021708225831389427,
0.039540160447359085,
0.06681254506111145,
0.01274320762604475,
0.05999815836548805,
-0.00711901905015111,
-0.011896652169525623,
-0.054... | 0.075709 |
# Tekton Bundle Contract v0.1 When using a Tekton Bundle in a task or pipeline reference, the OCI artifact backing the bundle must adhere to the following contract. ## Contract Only Tekton CRDs (eg, `Task` or `Pipeline`) may reside in a Tekton Bundle used as a Tekton bundle reference. Each layer of the image must map 1... | https://github.com/tektoncd/pipeline/blob/main//docs/tekton-bundle-contracts.md | main | tekton | [
-0.10038014501333237,
0.09070520102977753,
0.012832887470722198,
-0.032872628420591354,
0.04568219929933548,
-0.11042239516973495,
0.022499792277812958,
0.08891454339027405,
0.03382450342178345,
-0.03584485501050949,
-0.009847610257565975,
-0.09315124899148941,
0.02648259699344635,
0.04826... | 0.088015 |
Packages: * [resolution.tekton.dev/v1alpha1](#resolution.tekton.dev%2fv1alpha1) * [resolution.tekton.dev/v1beta1](#resolution.tekton.dev%2fv1beta1) * [tekton.dev/v1](#tekton.dev%2fv1) * [tekton.dev/v1alpha1](#tekton.dev%2fv1alpha1) * [tekton.dev/v1beta1](#tekton.dev%2fv1beta1) ## resolution.tekton.dev/v1alpha1 Resource... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.04752583056688309,
0.05869486182928085,
-0.018650440499186516,
-0.06333309412002563,
-0.008800880052149296,
-0.09798117727041245,
-0.0218813456594944,
0.02532867342233658,
0.05469761788845062,
0.033211931586265564,
-0.04866960272192955,
-0.12634973227977753,
-0.0712260752916336,
-0.0145... | 0.10481 |
| `params` *[[]Param](#tekton.dev/v1.Param)* | *(Optional)* Parameters are the runtime attributes passed to the resolver to help it figure out how to resolve the resource being requested. For example: repo URL, commit SHA, path to file, the kind of authentication to leverage, etc. | | `url` *string* | *(Optional)* URL ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.09176454693078995,
0.04011326655745506,
-0.050829529762268066,
-0.03629504144191742,
-0.014139856211841106,
-0.07292991876602173,
-0.024219853803515434,
0.0165169108659029,
0.010799051262438297,
0.029157424345612526,
-0.052074238657951355,
0.006994310766458511,
-0.01856820099055767,
-0.... | 0.127407 |
`apiVersion` string | `tekton.dev/v1` | | `kind` string | `PipelineRun` | | `metadata` *[Kubernetes meta/v1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#objectmeta-v1-meta)* | *(Optional)* Refer to the Kubernetes API documentation for the fields of the `metadata` field. | | `spec` *[... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
0.018732530996203423,
0.062415409833192825,
-0.014169884845614433,
-0.02203444577753544,
-0.033696696162223816,
-0.026551077142357826,
-0.06196386367082596,
0.02942001074552536,
0.047385573387145996,
0.012069064192473888,
-0.04160180687904358,
-0.11054635792970657,
-0.0926419049501419,
-0.... | 0.082031 |
in a Task are executed; they specify the parameters and resources used to run the steps in a Task. | Field | Description | | --- | --- | | `apiVersion` string | `tekton.dev/v1` | | `kind` string | `TaskRun` | | `metadata` *[Kubernetes meta/v1.ObjectMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
0.01140736136585474,
0.042303793132305145,
-0.03284788504242897,
-0.0006051392410881817,
0.0035735811106860638,
-0.04046590253710747,
-0.03544260561466217,
0.019318079575896263,
0.09364421665668488,
0.04579995945096016,
-0.0675889328122139,
-0.09328492730855942,
-0.044106267392635345,
-0.0... | 0.17971 |
| | | `outputs` *[[]Artifact](#tekton.dev/v1.Artifact)* | | ### ChildStatusReference (*Appears on:*[PipelineRunStatusFields](#tekton.dev/v1.PipelineRunStatusFields)) ChildStatusReference is used to point to the statuses of individual TaskRuns and Runs within this PipelineRun. | Field | Description | | --- | --- | | `na... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.07681062817573547,
0.06161157414317131,
-0.031684085726737976,
0.017300939187407494,
-0.001933719147928059,
-0.06389027088880539,
0.040044352412223816,
0.03639348968863487,
0.008009649813175201,
-0.04684194177389145,
-0.04739692062139511,
-0.0904541090130806,
-0.004722727462649345,
-0.0... | 0.178675 |
by users as inputs on a TaskRun or PipelineRun. | Field | Description | | --- | --- | | `name` *string* | Name declares the name by which a parameter is referenced. | | `type` *[ParamType](#tekton.dev/v1.ParamType)* | *(Optional)* Type is the user-specified type of the parameter. The possible types are currently “strin... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.04205746948719025,
0.03199894353747368,
-0.10147944837808609,
0.03815479949116707,
-0.10130206495523453,
-0.025567233562469482,
0.048643551766872406,
0.10360529273748398,
-0.03556424006819725,
-0.07308675348758698,
-0.06150957569479942,
-0.1226339340209961,
0.030862651765346527,
0.03914... | 0.120379 |
the PipelineRun cancelled by the user This reason may be found with a corev1.ConditionFalse status, if the cancellation was processed successfully This reason may be found with a corev1.ConditionUnknown status, if the cancellation is being processed or failed | | "CancelledRunningFinally" | PipelineRunReasonCancelledRu... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.015325883403420448,
-0.031596653163433075,
-0.04254245012998581,
0.013011544942855835,
0.008196000941097736,
-0.02561948075890541,
-0.04560700058937073,
0.0392971970140934,
-0.016338367015123367,
0.010473160073161125,
-0.004069465212523937,
-0.05275053158402443,
-0.010051071643829346,
-... | 0.033639 |
optional workspace has been passed to a Task that is expecting a non-optional workspace | | "ResolvingPipelineRef" | ReasonResolvingPipelineRef indicates that the PipelineRun is waiting for its pipelineRef to be asynchronously resolved. | | "ResourceVerificationFailed" | ReasonResourceVerificationFailed indicates that ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.04405217617750168,
-0.05137370899319649,
-0.019074006006121635,
0.03631886839866638,
0.04758213087916374,
-0.004392638336867094,
-0.0017511984333395958,
0.007075592875480652,
-0.013850986026227474,
-0.014030136168003082,
-0.0038988215383142233,
-0.05255783721804619,
-0.032658565789461136,... | 0.016976 |
this type.) PipelineRunStatusFields inlines the status fields. | ### PipelineRunStatusFields (*Appears on:*[PipelineRunStatus](#tekton.dev/v1.PipelineRunStatus)) PipelineRunStatusFields holds the fields of PipelineRunStatus’ status. This is defined separately and inlined so that other types can readily consume these fi... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.01782062090933323,
0.06439103186130524,
0.023946477100253105,
-0.010378829203546047,
0.0027851404156535864,
0.00012940647138748318,
-0.05646444112062454,
0.020898886024951935,
0.07522320747375488,
-0.0005542454309761524,
-0.04634011909365654,
-0.04793666675686836,
-0.09529896825551987,
... | 0.131932 |
of this task within the context of a Pipeline. This display name may be used to populate a UI. | | `description` *string* | *(Optional)* Description is the description of this task within the context of a Pipeline. This description may be used to populate a UI. | | `taskRef` *[TaskRef](#tekton.dev/v1.TaskRef)* | *(Opti... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.0721973404288292,
0.05715527385473251,
-0.04831979423761368,
0.04583653435111046,
0.010773756541311741,
-0.055703725665807724,
0.020686406642198563,
0.06576144695281982,
0.01779964007437229,
-0.04764263704419136,
-0.04282793402671814,
-0.09428458660840988,
-0.0005596426199190319,
0.0158... | 0.184946 |
*[[]TaskRunStepSpec](#tekton.dev/v1.TaskRunStepSpec)* | | | `sidecarSpecs` *[[]TaskRunSidecarSpec](#tekton.dev/v1.TaskRunSidecarSpec)* | | | `metadata` *[PipelineTaskMetadata](#tekton.dev/v1.PipelineTaskMetadata)* | *(Optional)* | | `computeResources` *[Kubernetes core/v1.ResourceRequirements](https://kubernetes.io/doc... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.018708428367972374,
0.061710141599178314,
-0.02993745543062687,
-0.012855395674705505,
-0.04027819633483887,
-0.002503749215975404,
-0.022116510197520256,
0.01868543028831482,
0.05988337844610214,
0.015775058418512344,
-0.05977805703878403,
-0.1086081862449646,
-0.06262847781181335,
-0.... | 0.112003 |
a Pipeline or Task in a remote location like a git repo. This feature is in beta and these fields are only available when the beta feature gate is enabled. | Field | Description | | --- | --- | | `resolver` *[ResolverName](#tekton.dev/v1.ResolverName)* | *(Optional)* Resolver is the name of the resolver that should per... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.09384308755397797,
-0.012480847537517548,
-0.0714874342083931,
0.02359733171761036,
-0.027747396379709244,
-0.06179932877421379,
0.01354118064045906,
0.0536680743098259,
0.04567965865135193,
0.0027337204664945602,
-0.06328465789556503,
-0.03319695219397545,
-0.0014545812737196684,
-0.00... | 0.173571 |
informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default “0.0.0.0” address inside a container will be accessible from the network. Cannot be updated. | | `envFrom` *[[]Kubernetes core/v1.EnvFromSource](https://kubernetes.io/docs/reference/genera... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
0.04550919681787491,
0.02653910219669342,
0.014536142349243164,
-0.014890964142978191,
0.0073878224939107895,
-0.009945298545062542,
-0.032053470611572266,
-0.04553763568401337,
-0.022935794666409492,
0.0167141854763031,
0.024761883541941643,
-0.07554832100868225,
-0.020227646455168724,
-0... | 0.01171 |
fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/> | | `stdin` *bool* | *(Optional)* Whether this Sidecar should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
0.07633552700281143,
-0.012441684491932392,
-0.00045145253534428775,
0.012791464105248451,
-0.0067399004474282265,
0.06341206282377243,
0.07747059315443039,
-0.009950324892997742,
0.09334907680749893,
0.009633207693696022,
0.023081613704562187,
-0.013351334258913994,
-0.029434632509946823,
... | 0.134279 |
was skipped because the pipeline run has been gracefully cancelled | | "PipelineRun was gracefully stopped" | GracefullyStoppedSkip means the task was skipped because the pipeline run has been gracefully stopped | | "Results were missing" | MissingResultsSkip means the task was skipped because it’s missing necessary re... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.0037893292028456926,
0.04730509594082832,
0.024728089570999146,
0.06515170633792877,
0.03162967041134834,
-0.021306997165083885,
-0.05713539198040962,
0.026784302666783333,
-0.02175017260015011,
-0.011312257498502731,
-0.007007984910160303,
-0.03984357789158821,
0.011951017193496227,
-0... | 0.03183 |
required by this Step. Cannot be updated. More info: <https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/> | | `volumeMounts` *[[]Kubernetes core/v1.VolumeMount](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#volumemount-v1-core)* | *(Optional)* Volumes to mount into the... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.03700854629278183,
-0.02106926217675209,
0.04311232268810272,
-0.052299898117780685,
0.015182443894445896,
-0.02806825377047062,
-0.06157216057181358,
0.03151592239737511,
0.028016434982419014,
0.05612991750240326,
0.025756338611245155,
-0.07347575575113297,
-0.0007166570867411792,
0.00... | 0.055196 |
| (Members of `ContainerState` are embedded into this type.) | | `name` *string* | | | `container` *string* | | | `imageID` *string* | | | `results` *[[]TaskRunStepResult](#tekton.dev/v1.TaskRunStepResult)* | | | `provenance` *[Provenance](#tekton.dev/v1.Provenance)* | | | `terminationReason` *string* | | | `inputs` *[... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.0304692592471838,
0.108384869992733,
-0.016852129250764847,
0.00206860457547009,
0.05156172811985016,
0.027898985892534256,
0.014919229783117771,
0.07291408628225327,
-0.04459874704480171,
-0.01983301155269146,
-0.04278719797730446,
-0.10488820821046829,
-0.012951637618243694,
0.0090845... | 0.117144 |
`beforeSteps` *[]string* | *(Optional)* | ### TaskKind (`string` alias) (*Appears on:*[TaskRef](#tekton.dev/v1.TaskRef)) TaskKind defines the type of Task used by the pipeline. | Value | Description | | --- | --- | | "Task" | NamespacedTaskKind indicates that the task type has a namespaced scope. | ### TaskRef (*Appear... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.05169355496764183,
0.029889961704611778,
0.011624697595834732,
-0.02476492151618004,
-0.053684622049331665,
-0.023716771975159645,
0.02542276121675968,
0.06583908945322037,
0.04821471869945526,
-0.03152984753251076,
-0.09101565182209015,
-0.10867861658334732,
-0.011348719708621502,
0.02... | 0.111043 |
not being pulled | | "InvalidParamValue" | TaskRunReasonInvalidParamValue indicates that the TaskRun Param input value is not allowed. | | "TaskRunPending" | TaskRunReasonPending is the reason set when the TaskRun is in the pending state | | "PodCreationFailed" | TaskRunReasonPodCreationFailed is the reason set when th... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.015606776811182499,
-0.04762289673089981,
-0.032221414148807526,
0.029212765395641327,
0.017082730308175087,
0.028705768287181854,
0.019070876762270927,
0.0031729629263281822,
0.007100030314177275,
0.057342320680618286,
-0.016318654641509056,
-0.05255477502942085,
0.02878771908581257,
0... | 0.127246 |
the StepSpec will be used. This field is only supported when the alpha feature gate is enabled. | | `sidecarSpecs` *[[]TaskRunSidecarSpec](#tekton.dev/v1.TaskRunSidecarSpec)* | *(Optional)* Specs to apply to Sidecars in this TaskRun. If a field is specified in both a Sidecar and a SidecarSpec, the value from the Sideca... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.03646015003323555,
-0.0015108062652871013,
-0.08290999382734299,
0.01631520316004753,
-0.009645598009228706,
0.020638711750507355,
0.017518412321805954,
0.003960275091230869,
0.013673855923116207,
0.023214682936668396,
-0.05426867678761482,
-0.08056744188070297,
-0.06916085630655289,
-0... | 0.124106 |
a type alias of TaskRunResult ### TaskRunStepSpec (*Appears on:*[PipelineTaskRunSpec](#tekton.dev/v1.PipelineTaskRunSpec), [TaskRunSpec](#tekton.dev/v1.TaskRunSpec)) TaskRunStepSpec is used to override the values of a Step in the corresponding Task. | Field | Description | | --- | --- | | `name` *string* | The name of ... | https://github.com/tektoncd/pipeline/blob/main//docs/pipeline-api.md | main | tekton | [
-0.08121861517429352,
0.045936670154333115,
0.01190988440066576,
-0.004782556556165218,
-0.051945898681879044,
0.0007997315260581672,
-0.005529090762138367,
0.03879978135228157,
0.05428573116660118,
-0.0016639558598399162,
-0.0883038267493248,
-0.07640816271305084,
-0.03534498065710068,
-0... | 0.153872 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.