content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
inputs are missing: Storage.TF\_VAR\_AWS\_S3\_BUCKET\_ARN => TF\_VAR\_AWS\_S3\_BUCKET\_ARN ``` !!! note We enabled output uploading to our backend on August 21 2023. If your stack produced an output before that date, you will need to rerun it to make the output available for references. ##### Imported outputs If you ha... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-dependencies.md | main | spacelift | [
-0.02707068622112274,
-0.08421987295150757,
-0.030479231849312782,
-0.0007079272763803601,
0.02337648533284664,
0.010123113170266151,
-0.05779688060283661,
-0.09129109233617783,
0.05093502998352051,
0.06961905211210251,
-0.004598353523761034,
-0.09364525973796844,
0.03679906204342842,
-0.0... | -0.070551 |
will start a run immediately and queue up `PaymentService` and `CartService`. When `Network` finishes running, those two will start running. Since `PaymentService` and `CartService` do not depend on each other, they can run in parallel. `BaseInfra` remains untouched, as we never go \_up\_ in the dependency graph. #### ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-dependencies.md | main | spacelift | [
-0.07438364624977112,
-0.032773375511169434,
-0.04012519493699074,
-0.054845940321683884,
-0.028332054615020752,
-0.017905201762914658,
-0.03125154227018356,
-0.01588446833193302,
-0.02878424897789955,
-0.0047166915610432625,
0.054156046360731125,
0.030449725687503815,
0.02310830168426037,
... | 0.036688 |
stack, you need to delete all of its downstream dependencies first. However, if a stack only has upstream dependencies (parent stacks that it depends on), it can be deleted without any issues. ## Ordered Stack creation and deletion Stack dependencies do not handle the lifecycle of the stacks. Ordering the creation and ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-dependencies.md | main | spacelift | [
-0.05876878648996353,
-0.032623376697301865,
0.06539341062307358,
-0.017578834667801857,
-0.03392499312758446,
-0.0682203471660614,
-0.028422564268112183,
-0.1311907023191452,
0.04506216570734978,
0.04492293670773506,
0.02233496494591236,
-0.021837934851646423,
-0.003227951703593135,
0.033... | -0.041567 |
# Stack settings Many settings can be configured directly on the stack to influence how [runs](../run/README.md) and [tasks](../run/task.md) within a stack are processed. Other factors that influence runs and tasks include: - [Environment variables](../configuration/environment.md) - Attached [contexts](../configuratio... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.002150867832824588,
-0.1646432727575302,
-0.05326841399073601,
0.010916421189904213,
-0.05399702861905098,
-0.022825509309768677,
-0.06821756809949875,
0.047651153057813644,
-0.040876779705286026,
-0.023764945566654205,
-0.028512155637145042,
0.0027341675013303757,
-0.005043174605816603,
... | 0.032202 |
workflows can be customized by adding extra commands to be executed before and after specific phases: - [Initialization](../run/README.md#initializing) (`before\_init` and `after\_init`) - [Planning](../run/proposed.md#planning) (`before\_plan` and `after\_plan`) - [Applying](../run/tracked.md#applying) (`before\_apply... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.05674775317311287,
0.011009608395397663,
0.023464404046535492,
-0.020390929654240608,
0.03138744458556175,
-0.09021800011396408,
-0.06260640919208527,
-0.013435372151434422,
0.03043629601597786,
0.0046545700170099735,
-0.05062292516231537,
0.06434942036867142,
0.005165799520909786,
-0.0... | 0.085553 |
Hooks from manually and auto-attached contexts can only be edited from their respective views. In the \_before\_ phase, hook priorities work as follows: - context hooks (based on set priorities) - context auto-attached hooks (reversed alphabetically) - stack hooks In the \_after\_ phase, hook priorities work as follows... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.02567683346569538,
-0.10119599848985672,
-0.0006771518383175135,
0.008375633507966995,
-0.051612284034490585,
0.0494089275598526,
0.031460389494895935,
-0.034392718225717545,
-0.009482945315539837,
-0.007545203436166048,
-0.0025191782042384148,
-0.08681292831897736,
-0.0316520631313324,
... | -0.007842 |
optional \_description\_ is completely free-form and it supports [Markdown](https://daringfireball.net/projects/markdown/){: rel="nofollow"}. This is a good place for a thorough explanation of the purpose of the stack and a link or two. !!! tip Based on the original \_name\_, Spacelift generates an immutable slug that ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.12557323276996613,
-0.008584622293710709,
0.01646893471479416,
0.04852375388145447,
0.009644475765526295,
-0.01289784163236618,
0.04568995535373688,
-0.022705120965838432,
0.03283142298460007,
-0.07593274861574173,
-0.01389257237315178,
-0.04085070267319679,
0.025500716641545296,
-0.024... | 0.108494 |
cares about. In the absence of push policies, any changes made to the project root and any paths specified by project globs will trigger Spacelift runs. !!! warning Project globs do not mount the files or directories in your project root. They are used primarily for triggering your stack when, for example, there are ch... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.0940340906381607,
-0.12129239737987518,
0.002165593206882477,
0.017972808331251144,
-0.00031946602393873036,
-0.05002313107252121,
-0.008871967904269695,
0.057643722742795944,
0.048413679003715515,
-0.01461920328438282,
0.057892024517059326,
0.014156438410282135,
-0.0036795353516936302,
... | 0.010289 |
about [git push policies](../policy/push-policy/README.md#git-push-policy-and-tracked-branch), tracked branches, and head commits. Results of both tracked and proposed runs are displayed in the source control provider using their specific APIs. Refer to our [GitHub](../../integrations/source-control/github.md) and [Git... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/stack-settings.md | main | spacelift | [
-0.10522689670324326,
-0.011147863231599331,
0.015084095299243927,
0.019535349681973457,
0.018769707530736923,
-0.07665364444255829,
-0.01106408890336752,
0.0345311313867569,
0.030381981283426285,
0.01688767410814762,
-0.030597258359193802,
-0.017110956832766533,
0.06084665283560753,
-0.04... | 0.055346 |
# Drift detection {% if is\_saas() %} !!! Info This feature is only available on the Starter+ plan and above. Please check out our [pricing page](https://spacelift.io/pricing){: rel="nofollow"} for more information. {% endif %} ## Drift happens In \_infrastructure-as-code\_, the concept of \_drift\_ represents the diff... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/drift-detection.md | main | spacelift | [
-0.049268048256635666,
0.01450351532548666,
0.030741995200514793,
0.021214870736002922,
0.0755787268280983,
-0.05046207085251808,
0.016887053847312927,
-0.12117425352334976,
0.058000028133392334,
0.06305530667304993,
0.03621677681803703,
-0.10124462842941284,
0.05525766313076019,
-0.047463... | 0.078055 |
a numeric limit\*\*: Specify the maximum number of concurrent drift detection runs  #### Behavior When drift detection run limits are configured: - \*\*Default Behavior\*\*: Without limits, drift detection runs have no concurrency restrictions - \*\*With Numeric Li... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/drift-detection.md | main | spacelift | [
-0.13336597383022308,
0.03498123213648796,
-0.046761687844991684,
0.0025049045216292143,
0.05262911692261696,
-0.05305333435535431,
0.06991486251354218,
-0.0694003477692604,
-0.03943232074379921,
-0.010860550217330456,
0.008110666647553444,
-0.044644080102443695,
0.05564095452427864,
-0.00... | 0.248932 |
# Scheduling stack actions {% if is\_saas() %} !!! Info This feature is only available on the Business plan and above. Please check out our [pricing page](https://spacelift.io/pricing){: rel="nofollow"} for more information. {% endif %} If you are using [private workers](../../concepts/worker-pools/README.md#private-wo... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/scheduling.md | main | spacelift | [
-0.1304657906293869,
-0.09234210103750229,
-0.04331415519118309,
0.08056033402681351,
-0.03207138180732727,
-0.03400445356965065,
0.004938645754009485,
-0.11720973253250122,
0.0289952103048563,
0.02394689992070198,
-0.014111676253378391,
-0.0016112382290884852,
0.012278219684958458,
0.0192... | 0.019096 |
# Organize stacks Depending on the complexity of your infrastructure, the size of your team, your particular needs, and your preferred way of working, you may end up managing a lot of stacks. Spacelift offers several options for searching through your stacks, from basic [query-based searching](organizing-stacks.md#quer... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/organizing-stacks.md | main | spacelift | [
-0.04167434945702553,
-0.09205268323421478,
-0.07962112873792648,
0.07181952893733978,
0.0032566923182457685,
0.0925724133849144,
0.005452208686619997,
0.0323583260178566,
-0.08733829855918884,
0.022510532289743423,
0.015813305974006653,
0.020679526031017303,
0.013235114514827728,
0.028460... | -0.023343 |
filter view as default](<../../assets/screenshots/stack/filter-views-default.png>) 5. Click \*\*Save\*\*. If you set a filter view as your default, the next time you log in or navigate to the \_Stacks\_ tab, your personal default view will be applied. ### Shared views Filter views can be private (default for new views)... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/organizing-stacks.md | main | spacelift | [
-0.05214933305978775,
-0.12042631208896637,
0.0037151530850678682,
0.04306475818157196,
-0.011451603844761848,
0.061137061566114426,
0.030016357079148293,
-0.04948582127690315,
-0.015130812302231789,
-0.02887992188334465,
0.018769972026348114,
-0.057648953050374985,
-0.037469927221536636,
... | -0.026465 |
# Stack If you're managing your infrastructure in Spacelift, you're managing them with stacks. A stack is a combination of source code, the current state of the managed infrastructure (e.g. OpenTofu/Terraform state file) and the configuration ([environment](../configuration/environment.md) variables and mounted files).... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/README.md | main | spacelift | [
-0.08136588335037231,
-0.08288809657096863,
-0.00448262644931674,
0.017519144341349602,
-0.022674383595585823,
-0.06594087183475494,
-0.0658908411860466,
-0.01884792558848858,
0.017527500167489052,
0.06911781430244446,
0.0175381638109684,
-0.07388836145401001,
0.027145685628056526,
-0.0126... | 0.038931 |
# Create, delete, and lock stacks ## Create a stack in Spacelift [Creating a stack](../../concepts/stack/creating-a-stack.md) involves 9 steps, most of which are optional. Required tasks are marked with an asterisk here: 1. \*[Name, describe, and label](#1-stack-details) the stack. 2. \*[Create a link](#2-connect-to-so... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/creating-a-stack.md | main | spacelift | [
-0.10090269148349762,
-0.16727742552757263,
-0.023605698719620705,
0.012035118415951729,
-0.009104211814701557,
-0.02959415502846241,
-0.04724867269396782,
-0.026641616597771645,
-0.0131949782371521,
0.07525083422660828,
0.010280727408826351,
-0.07059819251298904,
0.017587989568710327,
-0.... | -0.012276 |
AWS region your stack will be located in (e.g. `us-east-2`). 2. \*\*Stack name\*\*: Enter the name of the corresponding CloudFormation stack. 3. \*\*Entry template file\*\*: Enter the path to the template file in your repo describing the root CloudFormation stack. 4. \*\*Template bucket\*\*: Enter the location of the S... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/creating-a-stack.md | main | spacelift | [
-0.0395948551595211,
-0.09395184367895126,
0.009636870585381985,
-0.03838896378874779,
-0.05689254403114319,
0.016849927604198456,
-0.08942053467035294,
-0.04679010808467865,
0.056107047945261,
0.03092455491423607,
-0.04892575368285179,
-0.11752955615520477,
-0.037528373301029205,
-0.07689... | 0.05569 |
Attach policies If you're just following the LaunchPad steps, you won't have any [policies](../../concepts/policy/README.md) yet. If you did configure policies, you will be able to attach them here: - [Approval](../../concepts/policy/approval-policy.md): Who can approve or reject a run and how a run can be approved. - ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/stack/creating-a-stack.md | main | spacelift | [
-0.02581004798412323,
-0.06848233938217163,
0.03329307213425636,
-0.020184343680739403,
0.05528463050723076,
-0.053150005638599396,
0.034910622984170914,
-0.03816462308168411,
0.005517164245247841,
0.10886245220899582,
0.023843474686145782,
-0.012915017083287239,
0.019659727811813354,
0.01... | 0.037694 |
# Pull Request Comments ## Pull Request Plan Commenting ### Via Notification policy We have a nice example in our [Notification policy](../policy/notification-policy.md#complex-example-adding-a-comment-to-a-pull-request-about-changed-resources) documentation that shows how to add a comment to a pull request about chang... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/pull-request-comments.md | main | spacelift | [
-0.14059528708457947,
-0.03175140172243118,
0.06057870388031006,
0.04505947232246399,
0.06141287460923195,
-0.010019220411777496,
0.04442513734102249,
0.02264978550374508,
0.045014623552560806,
0.016293169930577278,
-0.03277526795864105,
-0.025095483288168907,
0.01231219619512558,
0.048634... | 0.047566 |
# Module test case Module test cases are special types of runs that are executed not on [Stacks](../stack/README.md) but on Spacelift-managed [OpenTofu/Terraform modules](../../vendors/terraform/module-registry.md). Note that this article does not cover modules specifically - for that please refer directly to [their do... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/test-case.md | main | spacelift | [
-0.06468535214662552,
-0.0022280418779700994,
0.01794268935918808,
0.07260778546333313,
0.0512431375682354,
-0.0797002986073494,
-0.05207087844610214,
-0.03472917526960373,
0.007227355148643255,
0.003539041383191943,
0.04072163626551628,
0.04113797843456268,
0.023705944418907166,
0.0049860... | 0.104227 |
# Tracked run (deployment) Tracked runs represent the actual changes to your infrastructure caused by changes to your infrastructure definitions and/or configuration. In that sense, they can be also called deployments. Tracked runs are effectively an extension of proposed runs - instead of stopping at the [planning](pr... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/tracked.md | main | spacelift | [
-0.05311474949121475,
-0.011470668017864227,
0.013028299435973167,
0.013365587219595909,
0.1333184689283371,
-0.07627462595701218,
-0.027895085513591766,
-0.05729121342301369,
0.03162306174635887,
-0.021796293556690216,
0.03080485388636589,
0.029023239389061928,
0.043082281947135925,
-0.05... | 0.117188 |
is required, a tracked run will transition from the [planning](proposed.md#planning) state to \_unconfirmed\_. At that point the worker node encrypts uploads the entire workspace to a dedicated Amazon S3 location and finishes its involvement with the run. The resulting changes are shown to the user for the final approv... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/tracked.md | main | spacelift | [
-0.06837745755910873,
0.000959964410867542,
-0.04535922780632973,
0.04359520226716995,
0.1226041167974472,
-0.06531338393688202,
0.010817204602062702,
-0.08266066759824753,
0.06231750175356865,
0.07410770654678345,
0.0030256181489676237,
0.016701215878129005,
0.04684596508741379,
-0.047138... | 0.069212 |
applying phase succeeds, the run transitions to the [finished](./README.md#finished) state. On the other hand, if anything goes wrong, the run is marked as [failed](./README.md#failed). ## Reporting The results of tracked runs are reported in multiple ways: - as deployments in VCS unless the change is a [no-op](tracked... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/tracked.md | main | spacelift | [
-0.046837374567985535,
-0.038177739828825,
0.023275427520275116,
0.0303990188986063,
0.04998711869120598,
-0.08739648014307022,
-0.038435619324445724,
-0.03603414073586464,
0.043536361306905746,
0.02661575935781002,
-0.012073194608092308,
-0.017636029049754143,
0.06602097302675247,
-0.0198... | 0.029226 |
# Run Promotion ## What is Run Promotion? As a quick summary of the differences between the two types of runs: [proposed](proposed.md) runs only display changes to be made, while [tracked](tracked.md) runs apply (deploy) the proposed changes. Promoting a proposed run is triggering a tracked run for the same Git commit.... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/run-promotion.md | main | spacelift | [
-0.047742124646902084,
-0.10933788120746613,
-0.0018575782887637615,
-0.03948237746953964,
0.06589239835739136,
0.02851782739162445,
-0.08271042257547379,
-0.002948730019852519,
-0.011000766418874264,
0.05582766234874725,
0.04489641264081001,
-0.007775327656418085,
0.019545376300811768,
0.... | 0.015322 |
# User-Provided Metadata Occasionally you might want to add additional information to your Runs which isn’t handled on a first-class basis by Spacelift. You can attach this kind of information using the run metadata parameter, which is available through [spacectl](https://github.com/spacelift-io/spacectl){: rel="nofoll... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/user-provided-metadata.md | main | spacelift | [
-0.09562311321496964,
-0.007151763886213303,
-0.03548616170883179,
0.06156519800424576,
-0.10705327987670898,
-0.04986443743109703,
0.005491373594850302,
0.020139597356319427,
-0.09504543244838715,
0.0033823195844888687,
-0.013550153002142906,
-0.050457969307899475,
0.026574978604912758,
-... | 0.044333 |
# Proposed run (preview) Proposed runs are previews of changes that would be applied to your infrastructure if the new code was to somehow become canonical, for example by pushing it to the [tracked branch](../stack/stack-settings.md#vcs-integration-and-repository). Proposed runs are generally triggered by Git push eve... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/proposed.md | main | spacelift | [
-0.03439660742878914,
-0.05234815180301666,
0.02177174761891365,
0.008360644802451134,
0.06550651043653488,
-0.09370454400777817,
-0.1394113302230835,
0.01878965273499489,
0.00888174120336771,
0.044084399938583374,
-0.04207977280020714,
0.03973796218633652,
-0.02905767410993576,
-0.0450228... | 0.053378 |
# Run Every job that can touch your Spacelift-managed infrastructure is called a Run. There are four main types of runs, and each of them warrants a separate section. Three of them are children of [Stacks](../stack/README.md): - [task](task.md), which is a freeform command you can execute on your infrastructure; - [pro... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/README.md | main | spacelift | [
-0.07743363827466965,
-0.036155425012111664,
-0.016862941905856133,
0.035250645130872726,
0.015085550025105476,
-0.11388500034809113,
-0.05180395022034645,
-0.058282773941755295,
-0.010964852757751942,
0.028032731264829636,
-0.031209422275424004,
0.02517676167190075,
0.01638607308268547,
-... | 0.17181 |
run even if it's ready for processing, transitioning it to the terminal [Discarded](#discarded) state. ### Discarded Discarded state means that the user has manually stopped a [Queued](#queued) run or task even before it had the chance to be picked up by the worker. Discarded is a \_passive state\_ meaning no operation... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/README.md | main | spacelift | [
-0.06853174418210983,
-0.020755967125296593,
0.004747163504362106,
0.050831109285354614,
0.011575603857636452,
-0.0782310962677002,
0.07260509580373764,
-0.0440116822719574,
0.00976874865591526,
0.01836821436882019,
-0.0005815153708681464,
0.07134280353784561,
-0.003123064525425434,
-0.041... | 0.184106 |
List of Potential Run States NONE - The stack is created but no initial runs have been triggered. This is not offically a run state but is listed in the UI for informational purposes. QUEUED - The run is queued and is either waiting for an available worker or for the stack lock to be released by another run. CANCELED -... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/README.md | main | spacelift | [
-0.10075201839208603,
-0.030926410108804703,
0.011453740298748016,
0.06004791334271431,
0.01698179915547371,
-0.030188648030161858,
-0.007121734786778688,
-0.03129458427429199,
0.03227464109659195,
0.08570236712694168,
0.0016011159168556333,
0.011032487265765667,
-0.020793640986084938,
-0.... | 0.124892 |
setting for your account. ## Important Considerations Changing the retention period will not retroactively apply to existing runs. The new retention period will only take effect for runs created after the change has been made. Previously created runs will continue to follow the retention period that was active when the... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/README.md | main | spacelift | [
-0.04160770773887634,
-0.041825249791145325,
0.040895748883485794,
0.0049871476367115974,
0.06105409935116768,
-0.04391423612833023,
-0.03656220808625221,
-0.08756683021783829,
0.09455130994319916,
0.03925022482872009,
-0.020324015989899635,
0.006496950052678585,
0.02856532298028469,
-0.03... | 0.010469 |
# Task {% if is\_saas() %} !!! Info This feature is only available to paid Spacelift accounts. Please check out our [pricing page](https://spacelift.io/pricing){: rel="nofollow"} for more information. {% endif %}  While tasks enjoy the privilege of having their own GUI sc... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/task.md | main | spacelift | [
-0.08265402168035507,
-0.023272117599844933,
-0.04773800075054169,
0.02415510080754757,
0.014936459250748158,
-0.03428060561418533,
0.03440495580434799,
0.02216336876153946,
0.012061663903295994,
0.0684392899274826,
-0.008326280862092972,
-0.03501223027706146,
0.06552945077419281,
0.012980... | 0.109148 |
your infrastructure. ## Performing a task Apart from the common run phases described in the general run documentation, tasks have just one extra state - performing. That's when the arbitrary user-supplied command is executed, wrapped in `sh -c` to support all the shell goodies we all love to abuse. In particular, you c... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/task.md | main | spacelift | [
-0.01748533733189106,
0.01266434695571661,
0.050796374678611755,
-0.03508400171995163,
0.07211007177829742,
-0.07611282914876938,
-0.03799695521593094,
-0.043305814266204834,
-0.033899664878845215,
0.07553193718194962,
-0.06017191335558891,
-0.053681813180446625,
0.042126499116420746,
0.00... | 0.014606 |
# Ignored run warnings Ignored run warnings will help you identify why a run has not been triggered when a commit is pushed to your repository. A run can be ignored because of the following reasons: - A change has been made outside of the project root. - A tag is pushed. - The default push policy is disabled, and no cu... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/ignored-triggers.md | main | spacelift | [
-0.021051350980997086,
-0.04539310187101364,
-0.03450874239206314,
0.10910920798778534,
0.08785789459943771,
-0.01003165915608406,
-0.023704083636403084,
-0.04049219563603401,
0.03330765292048454,
0.0015492303064092994,
0.03966478630900383,
-0.026717735454440117,
0.05467437952756882,
-0.03... | 0.046618 |
# AI Spacelift now provides a way to harvest the power of AI to summarize failed runs. By clicking the `Explain` button in the runs history page, Saturnhead will use an advanced LLM to digest the logs of your failed runs and provide useful insights into what went wrong. ## Enabling Saturnhead features {% if is\_saas() ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/run/ai.md | main | spacelift | [
-0.02496282383799553,
-0.0156745333224535,
0.0539950393140316,
0.03583427891135216,
0.04013865813612938,
0.06476826220750809,
-0.02842090278863907,
0.0786813423037529,
-0.03730202093720436,
0.021324723958969116,
-0.06313148885965347,
-0.05208657309412956,
0.000007243999334605178,
0.0106503... | 0.121284 |
# API key role bindings [API keys](./../../integrations/api.md#spacelift-api-key) can receive roles through three methods: - \*\*Direct assignment\*\*: Assign roles directly to the API key. - \*\*IdP group assignment\*\*: Associate API keys with IdP groups to inherit group-based role assignment. - \*\*Login policy assi... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-api-keys.md | main | spacelift | [
-0.12851117551326752,
-0.020663170143961906,
-0.013474216684699059,
0.0041460758075118065,
-0.031592193990945816,
-0.03675435855984688,
0.054154884070158005,
-0.015848467126488686,
-0.05259143188595772,
0.02124570868909359,
0.006244225427508354,
-0.016187364235520363,
0.07133042812347412,
... | 0.047976 |
"reader-role-id" if { endswith(input.session.login, "-monitoring") } ``` === "Rego v0" ```opa package spacelift allow { input.session.member } # Assign roles based on key naming patterns roles["production"]["deployer-role-id"] { startswith(input.session.login, "ci-cd-") } roles["monitoring"]["reader-role-id"] { endswit... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-api-keys.md | main | spacelift | [
0.004760028328746557,
0.05748189985752106,
0.014693391509354115,
-0.03806942328810692,
0.020169176161289215,
-0.06573007255792618,
0.10910556465387344,
-0.007545980624854565,
-0.03836580738425255,
0.04988086596131325,
0.012752793729305267,
-0.09687638282775879,
0.05700048804283142,
0.03806... | 0.020659 |
API keys restricted to specific networks roles["production"] contains "secure-deployer-role-id" if { secure\_keys := {"production-deploy", "critical-automation"} secure\_keys[input.session.login] # Only allow from secure networks is\_secure\_network } is\_secure\_network if { secure\_cidrs := { "10.0.0.0/8", # Corporat... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-api-keys.md | main | spacelift | [
-0.038386598229408264,
0.07773683220148087,
-0.04232882335782051,
-0.046382930129766464,
0.011690478771924973,
-0.03195331618189812,
0.0837974026799202,
-0.022158585488796234,
-0.01752442494034767,
0.023269714787602425,
0.02228708006441593,
-0.05123791843652725,
0.0268547423183918,
0.09877... | 0.040374 |
If using login policies, verify syntax and logic, use the sample and simulate feature. ## Related Topics - \*\*[Assigning Roles to Users](assigning-roles-users.md)\*\*: Individual user role assignment - \*\*[Assigning Roles to IdP Groups](assigning-roles-groups.md)\*\*: Group-based role assignment - \*\*[RBAC System](r... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-api-keys.md | main | spacelift | [
-0.08236764371395111,
-0.031029732897877693,
-0.05213627964258194,
0.009721492417156696,
-0.08933772891759872,
-0.0006061328458599746,
0.06304221600294113,
-0.006589157972484827,
-0.09024079889059067,
0.0319412536919117,
-0.023224789649248123,
-0.02886383794248104,
0.11672984808683395,
0.0... | 0.04924 |
# IdP group role bindings IdP groups can receive roles through direct group assignment. Assign roles to the entire group, which automatically applies to all members of that group. ## Assign roles ### Assign roles to IdP groups using the web UI !!! info "Permission Scope" - \*\*Root Space Admins\*\* can create/modify/de... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-groups.md | main | spacelift | [
-0.024424714967608452,
-0.09119359403848648,
-0.01646208018064499,
0.027070941403508186,
-0.03319259732961655,
-0.0330551341176033,
0.09261108189821243,
-0.017845219001173973,
-0.04246269911527634,
0.017394380643963814,
0.027512459084391594,
-0.041321832686662674,
0.0415564626455307,
0.032... | 0.035987 |
input.session.teams[\_] == "Frontend" } roles["space-id"]["platform-engineer-role-slug"] { input.session.teams[\_] == "DevOps" } # Assign admin role for root space roles["root"]["space-admin-role-slug"] { input.session.teams[\_] == "Admin" } ``` If a user is logged in, their access levels will not change, so newly adde... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-groups.md | main | spacelift | [
-0.03252578154206276,
0.04890458658337593,
-0.027407895773649216,
0.04881496727466583,
-0.03875088319182396,
-0.04748421907424927,
0.07533427327871323,
0.0018580126343294978,
0.06598078459501266,
-0.0032474284525960684,
-0.024516737088561058,
-0.014161027036607265,
0.0131883155554533,
0.00... | 0.058941 |
roles["project-alpha"] contains "developer-role-id" if { some team in input.session.teams team == "Project-Alpha-Team" } roles["project-beta"] contains "developer-role-id" if { some team in input.session.teams team == "Project-Beta-Team" } # Functional role overlays roles["infrastructure"] contains "platform-role-id" i... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-groups.md | main | spacelift | [
0.0006405022577382624,
0.1030573695898056,
-0.03566696494817734,
0.010839291848242283,
0.024923983961343765,
-0.01831001415848732,
0.13517804443836212,
-0.0033016065135598183,
0.0056588053703308105,
-0.04270818829536438,
-0.03666343912482262,
-0.06600021570920944,
0.026814671233296394,
0.0... | 0.035821 |
# Authorization & RBAC Spacelift provides a comprehensive \*\*Role-Based Access Control (RBAC)\*\* system designed for enterprise infrastructure teams. RBAC enables fine-grained, customizable permissions giving you precise control over who can access what resources and perform which actions. ## Evolution from legacy sy... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/README.md | main | spacelift | [
-0.05199701711535454,
-0.049921438097953796,
-0.11901868134737015,
0.02161448448896408,
-0.07025732100009918,
0.0010939424391835928,
0.07607293874025345,
0.02035670541226864,
-0.022697295993566513,
0.03423024341464043,
-0.07167863100767136,
0.02308228239417076,
0.062051206827163696,
0.0134... | 0.220839 |
level. ## Next steps Dive deeper into RBAC with these guides: - \*\*[RBAC System](rbac-system.md)\*\*: Detailed explanation of Spacelift's RBAC implementation. ## Related Topics - \*\*[User Management](../user-management/README.md)\*\*: Invite and manage team members. - \*\*[Spaces](../spaces/README.md)\*\*: Organize r... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/README.md | main | spacelift | [
-0.056362323462963104,
-0.07071205228567123,
-0.10696320235729218,
-0.017160924151539803,
-0.05331983044743538,
0.04305288568139076,
0.09653724730014801,
0.03674919530749321,
-0.054261546581983566,
0.030036192387342453,
-0.056571658700704575,
0.05094355344772339,
0.09541366994380951,
-0.02... | 0.140576 |
# User role bindings Users can get permissions from three sources: - \*\*Direct Role Assignment\*\*: Assign roles directly to individual users. - \*\*IdP Group Assignment\*\*: Assign roles based on group memberships defined in your identity provider. - \*\*Login Policy\*\*: Use Open Policy Agent (OPA) policies to dynam... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-users.md | main | spacelift | [
-0.09198909252882004,
-0.04318055137991905,
-0.003173575736582279,
0.057242706418037415,
-0.03869340941309929,
-0.026674091815948486,
0.12948541343212128,
-0.03386038541793823,
-0.04145677760243416,
0.003347293706610799,
-0.0013980683870613575,
-0.0548623725771904,
0.056159857660532,
0.054... | 0.034089 |
to see new spaces they're granted access to. However, the space's creator immediately has access to it. #### Individual user assignment === "Rego v1" ```opa package spacelift allow if input.session.member # Assign platform engineer role to specific user roles["infrastructure"] contains "platform-engineer-role-id" if { ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-users.md | main | spacelift | [
-0.030975138768553734,
0.011394279077649117,
-0.005184760317206383,
-0.009519443847239017,
-0.05389411002397537,
-0.06677107512950897,
0.1258215755224228,
-0.005622418597340584,
0.019182734191417694,
0.012628637254238129,
-0.01765020564198494,
-0.06533349305391312,
-0.02729308232665062,
0.... | 0.017795 |
rule for office network is\_office\_network { office\_networks := { "192.168.1.0/24", "10.0.0.0/8" } office\_networks[network] net.cidr\_contains(network, input.request.remote\_ip) } ``` ### Assigning roles to users via IdP groups See [IdP Group Role Bindings](assigning-roles-groups.md) for details on how to assign rol... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-users.md | main | spacelift | [
-0.08047886937856674,
0.015197807922959328,
0.06322985142469406,
0.021325692534446716,
-0.03390220180153847,
0.04201005399227142,
0.08979387581348419,
-0.031082676723599434,
0.004517719615250826,
0.006165746133774519,
-0.02083762362599373,
0.03491588309407234,
0.006474649533629417,
0.05152... | -0.0067 |
# Stack role bindings Stacks can receive role bindings to perform operations with elevated permissions, similar to how users, API keys, and IdP groups receive permissions through [Spacelift's RBAC system](rbac-system.md). Stack role attachments replace the deprecated [Administrative](../stack/stack-settings.md#administ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-stacks.md | main | spacelift | [
-0.08184592425823212,
-0.09399160742759705,
-0.04139122739434242,
0.031957488507032394,
-0.034870684146881104,
-0.029728982597589493,
0.0008417755598202348,
0.040863048285245895,
-0.027806289494037628,
0.010755813680589199,
0.04564555734395981,
0.016026094555854797,
0.02329414151608944,
0.... | 0.102052 |
the above scenario, the `devops\_admin` stack will have the `Stack creator` role effective in the `dev` space, allowing it to create and manage stacks within that space. For more information, see the [Spacelift Terraform provider documentation](https://search.opentofu.org/provider/spacelift-io/spacelift/latest/docs/res... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-stacks.md | main | spacelift | [
-0.03403516858816147,
-0.08469080924987793,
0.05394074693322182,
0.06561639904975891,
-0.01849287562072277,
-0.09793927520513535,
-0.04222757741808891,
-0.030759774148464203,
0.010502210818231106,
0.02216372638940811,
0.06568482518196106,
-0.06398212164640427,
-0.01291934959590435,
0.06462... | -0.031654 |
resource "spacelift\_role\_attachment" "space\_writer" { stack\_id = spacelift\_stack.consumer.id role\_id = data.spacelift\_role.space\_writer.id space\_id = spacelift\_stack.provider.space\_id } resource "spacelift\_stack" "provider" { # Properties are omitted for brevity terraform\_external\_state\_access = true } `... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-stacks.md | main | spacelift | [
-0.06356863677501678,
-0.055801358073949814,
0.04279708489775658,
0.04326706379652023,
0.018358765169978142,
-0.08171254396438599,
0.0008314465521834791,
-0.0674615129828453,
-0.025968747213482857,
0.042482681572437286,
0.05201839283108711,
-0.022223660722374916,
0.014473053626716137,
0.01... | 0.016535 |
stacks are not allowed" if { stack := input.spacelift.stack stack.administrative == true } # Would become: deny contains "Administrative stacks are not allowed" if { some role in input.spacelift.stack.roles role.id == "space-admin" # (1) } ``` === "Rego v0" ```rego # Old policy: deny["Administrative stacks are not allo... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/assigning-roles-stacks.md | main | spacelift | [
-0.08730936050415039,
-0.018004484474658966,
0.02290394902229309,
0.05856506526470184,
-0.01283335778862238,
-0.04404808208346367,
-0.016762200742959976,
-0.03245590999722481,
-0.026950763538479805,
-0.05848574638366699,
0.07369344681501389,
-0.04850060120224953,
0.05119891092181206,
-0.01... | 0.00207 |
# Role-Based Access Control (RBAC) Up until recently, Spacelift used \*\*legacy system roles\*\* with broad roles (Reader, Writer, Admin) to manage user permissions. This approach worked for many organizations but lacked the granularity and flexibility needed for modern infrastructure management. With the introduction ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
-0.036380358040332794,
-0.06410080194473267,
-0.05948883295059204,
0.03864641115069389,
-0.05407172814011574,
-0.00440385052934289,
0.030421607196331024,
0.008783966302871704,
-0.05869433283805847,
0.027935946360230446,
-0.05028938874602318,
0.0214704517275095,
0.052813414484262466,
0.0495... | 0.138959 |
can assume roles to manage resources programmatically inside Spacelift via the [Spacelift Terraform Provider](https://search.opentofu.org/provider/spacelift-io/spacelift/latest){: rel="nofollow"}. For more information, see [Assigning Roles to Stacks](./assigning-roles-stacks.md). ### Actions: the building blocks of per... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
-0.03030194155871868,
-0.055345505475997925,
0.013926638290286064,
0.07350368052721024,
-0.016889244318008423,
-0.06049105152487755,
0.0062750037759542465,
-0.036659568548202515,
-0.037927690893411636,
-0.027504511177539825,
0.014502528123557568,
-0.014633788727223873,
0.019827628508210182,
... | 0.012618 |
stack | Admin | | `stack:lock` | Lock a stack for exclusive use | Writer | | `stack:manage` | Manage stacks in a given space | Admin | | `stack:managed-state-import` | Import managed state for a stack | Admin | | `stack:managed-state-rollback`| Rollback managed state for a stack | Admin | | `stack:reslug` | Re-slug sta... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
-0.11298578232526779,
-0.14008593559265137,
-0.07663138955831528,
0.0411398708820343,
-0.03981953486800194,
-0.023425735533237457,
-0.016569845378398895,
-0.02270629070699215,
-0.023154357448220253,
0.08738772571086884,
0.07028348743915558,
0.04070194810628891,
0.020713360980153084,
-0.078... | 0.121384 |
Writer | | `terraform-provider-version:update` | Update Terraform provider version | Writer | #### Intent actions Intent actions are used for managing [Intent-based infrastructure](../intent/README.md). | Action | Description | Legacy Fallback | | ----------------------------------------------- | ----------------------... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
-0.005696407984942198,
-0.04458334296941757,
0.03358324617147446,
-0.015816787257790565,
-0.015314479358494282,
0.016282271593809128,
0.010709555819630623,
-0.03964152932167053,
0.01661502756178379,
0.1215452253818512,
0.00006317135557765141,
-0.04310717061161995,
0.008930010721087456,
0.0... | 0.053355 |
Platform team management. - Application team read access. - Cross-team coordination requirements. #### Policy access patterns \*\*Centralized Governance\*\*: - Security team manages all policies. - Consistent rules across the organization. - Limited policy creation permissions. \*\*Federated Governance\*\*: - Teams man... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
0.020439786836504936,
-0.055603694170713425,
-0.09695453196763992,
-0.03882743790745735,
0.008058763109147549,
-0.035789284855127335,
0.045525290071964264,
0.015456946566700935,
-0.020337358117103577,
0.02570389211177826,
-0.04080243036150932,
-0.021985942497849464,
0.07863602042198181,
0.... | 0.143984 |
- Delete ### Custom roles #### Create custom roles using the web UI 1. Go to \*\*Organization Settings\*\* → \*\*Access Control Center\*\* → \*\*Roles\*\*. 2. Click \*\*Create Role\*\* to start defining a new role. 3. \*\*Define Role Properties\*\*: - \*\*Name\*\*: Descriptive role name (e.g., "Infrastructure Developer... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/authorization/rbac-system.md | main | spacelift | [
-0.025874584913253784,
0.009655080735683441,
-0.01592108979821205,
0.0322890430688858,
-0.028265513479709625,
-0.03411960229277611,
0.040563613176345825,
-0.06879158318042755,
-0.012758851051330566,
0.08585691452026367,
-0.03465624153614044,
-0.08375990390777588,
0.06132335215806961,
0.050... | 0.021339 |
# Task policy !!! warning Task run policies are deprecated. Use [approval policies](./approval-policy.md) instead for a more flexible, powerful way to control which tasks are allowed to proceed. Existing users with task run policies should migrate as soon as possible using our [migration guide](#migration-guide). Space... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/task-run-policy.md | main | spacelift | [
-0.07097356021404266,
-0.020056264474987984,
0.02094286121428013,
-0.0005143607268109918,
0.01288068201392889,
-0.05807463824748993,
0.026196543127298355,
-0.06709949672222137,
-0.0373544842004776,
0.08351346850395203,
-0.015431256964802742,
-0.027184665203094482,
0.049735020846128464,
0.0... | 0.062997 |
data: | Alias | Source | | --------- | --------------- | | `request` | `input.request` | | `session` | `input.session` | | `stack` | `input.stack` | ## Examples This example blocks non-admins from running tasks: === "Rego v1" ```opa package spacelift deny contains "only admins can run tasks" if not input.session.admin ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/task-run-policy.md | main | spacelift | [
-0.09726721793413162,
0.0408051460981369,
0.011510921642184258,
0.015757853165268898,
-0.007599823642522097,
-0.07551456987857819,
0.030259110033512115,
-0.05785524100065231,
-0.01395032275468111,
0.07715334743261337,
-0.01699656806886196,
-0.0413174033164978,
0.06125734746456146,
0.021342... | 0.068406 |
# Approval policy Approval policies allow organizations to create sophisticated run review and approval flows that reflect their preferred workflow, security goals, and business objectives. Without an explicit approval policy, \*\*anyone with write access\*\* to a stack can create a [run](../run/README.md) or [task](..... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/approval-policy.md | main | spacelift | [
-0.07465431839227676,
-0.0006393936346285045,
0.0012501007877290249,
0.013723749667406082,
0.06181233748793602,
-0.07083320617675781,
0.040685512125492096,
-0.04895169287919998,
0.03246218338608742,
0.10538635402917862,
-0.03443126007914543,
-0.03480174392461777,
0.016482751816511154,
0.00... | 0.075058 |
given job; the first review is not supposed to set the `approve` value to `true`. !!! info Users must have [`write`](./stack-access-policy.md#writers) or [`admin`](./login-policy.md#rbac-role-assignment) access to the stack to be able to approve changes. ### How it works When a user reviews the run, Spacelift persists ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/approval-policy.md | main | spacelift | [
-0.12612290680408478,
-0.025863077491521835,
-0.0516381673514843,
0.02808421105146408,
-0.019400672987103462,
-0.020566659048199654,
0.07274319976568222,
-0.05120919644832611,
-0.026967257261276245,
0.03438869118690491,
-0.009657533839344978,
0.02711922489106655,
0.03990990296006203,
0.011... | 0.044863 |
username of the creator", "name": "string - full name of the creator", "teams": ["string - names of teams the creator was a member of"], "machine": "boolean - whether the run was initiated by a human or a machine" }, "drift\_detection": "boolean - is this a drift detection run", "flags": ["string - list of flags set on... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/approval-policy.md | main | spacelift | [
-0.05427822843194008,
0.0016568631399422884,
-0.01832214929163456,
0.015377208590507507,
0.05634114891290665,
-0.05141915753483772,
0.04614396020770073,
-0.048744890838861465,
0.013775336556136608,
0.050998374819755554,
0.008206380531191826,
-0.08097490668296814,
0.038165539503097534,
-0.0... | 0.122923 |
v0" ```opa package spacelift approve { input.run.state != "UNCONFIRMED" } approve { count(input.reviews.current.approvals) > 1 count(input.reviews.current.rejections) == 0 } ``` ### Two to approve, two to reject This is a variation of the above policy that will automatically fail any run that receives more than one rej... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/approval-policy.md | main | spacelift | [
-0.0835084468126297,
0.017151620239019394,
0.01647702418267727,
0.05510376766324043,
-0.0020838489290326834,
-0.03537262603640556,
0.04962543770670891,
0.004490126855671406,
0.00807920377701521,
0.02728392370045185,
0.00942503847181797,
-0.07156197726726532,
0.05269981548190117,
-0.0387235... | 0.069165 |
team in approval.session.teams team == "Director" } devops\_approval if { some approval in approvals some team in approval.session.teams team == "DevOps" } security\_approval if { some approval in approvals some team in approval.session.teams team == "Security" } # Approve when a single Director approves: approve if di... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/approval-policy.md | main | spacelift | [
-0.04457692801952362,
0.08926520496606827,
0.0059646558947861195,
0.009968128055334091,
0.004809147212654352,
-0.09048512578010559,
0.12336226552724838,
-0.0017124773003160954,
-0.006276353262364864,
0.0491579994559288,
0.009888730943202972,
-0.07878504693508148,
0.006967461667954922,
0.04... | 0.100648 |
# Login policy ## Purpose Login policies provide policy-as-code authorization for Spacelift, allowing users to log in and assign [RBAC roles](../authorization/README.md) programmatically. Unlike all other policy types, login policies are global and can't be attached to individual stacks. They take effect immediately on... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/login-policy.md | main | spacelift | [
-0.07312680780887604,
-0.06260620802640915,
-0.03564182668924332,
-0.03903452306985855,
-0.01954123005270958,
0.008393497206270695,
0.0744246244430542,
-0.012011440470814705,
-0.014197424054145813,
0.04475817829370499,
0.021513681858778,
0.04311962053179741,
0.08882147073745728,
0.01048473... | 0.077108 |
is necessary, grant users \_limited\_ admin access using the \*\*space\_admin\*\* rule. ## Data input Each policy request will receive this data input: !!! tip "Official Schema Reference" For the most up-to-date and complete schema definition, please refer to the [official Spacelift policy contract schema](https://app.... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/login-policy.md | main | spacelift | [
-0.06126506254076958,
0.01100398600101471,
-0.0030543541070073843,
0.01793266087770462,
-0.023937128484249115,
-0.02081788331270218,
0.05751441419124603,
0.013175204396247864,
-0.02112642489373684,
0.0027040487620979548,
0.05212346091866493,
-0.06961922347545624,
0.034558046609163284,
0.04... | 0.021206 |
assignment](#rbac-role-assignment) section above. Copy the role slug from this input or from \*\*Organization Settings\*\* → \*\*Access Control Center\*\* → \*\*Roles\*\* to use in your policy. ## Login policy examples !!! abstract "Example Policies Library" We maintain a [library of example policies](https://github.co... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/login-policy.md | main | spacelift | [
-0.048333968967199326,
-0.04865777865052223,
-0.04417386278510094,
0.0029300828464329243,
-0.02511078491806984,
0.027652084827423096,
0.12010642141103745,
-0.03160841763019562,
-0.058928947895765305,
0.006952343508601189,
-0.039239611476659775,
0.007494464050978422,
0.052751291543245316,
0... | 0.03803 |
addresses managed by Google to grant access to Spacelift. === "Rego v1" ```rego package spacelift admins := {"alice@example.com"} login := input.session.login admin if admins[login] allow if endswith(input.session.login, "@example.com") deny if { not admins[login]; not allow } ``` === "Rego v0" ```rego package spacelif... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/login-policy.md | main | spacelift | [
-0.06447320431470871,
0.017506493255496025,
0.03007022850215435,
-0.044077832251787186,
-0.0054931300692260265,
-0.062279485166072845,
0.08900953829288483,
-0.10129661858081818,
-0.020357312634587288,
0.007373160682618618,
-0.016878537833690643,
0.024372920393943787,
0.05671022832393646,
0... | -0.003233 |
teams, so if it evaluates to a non-empty collection, it will \*\*replace\*\* the original list of teams in the session. In the above example, the `Superwriter` role will become the only team for the evaluated user session. If you want to retain the original list of teams, you can modify the above example: === "Rego v1"... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/login-policy.md | main | spacelift | [
-0.08158683031797409,
0.07453000545501709,
0.011682442389428616,
0.035929013043642044,
0.009006082080304623,
-0.015664082020521164,
0.06647655367851257,
-0.01580853946506977,
-0.007684977259486914,
0.04800151288509369,
-0.0024676737375557423,
-0.01632007770240307,
-0.0011063681449741125,
0... | 0.015077 |
# Policy {% if is\_saas() %} !!! Info This feature is only available to paid Spacelift accounts. Please check out our [pricing page](https://spacelift.io/pricing){: rel="nofollow"} for more information. {% endif %} Policy-as-code is the idea of expressing rules using a high-level programming language and treating them ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.09217441827058792,
-0.00677470350638032,
-0.0430690199136734,
-0.0168195441365242,
-0.013354187831282616,
-0.01417030580341816,
0.0809016078710556,
-0.029533958062529564,
-0.021638523787260056,
0.04386267066001892,
0.004064653534442186,
-0.011491312645375729,
0.05612943693995476,
-0.030... | 0.066844 |
that receive some JSON-formatted input (the data needed to make a decision) and are allowed to produce an output in a predefined form. Each policy type exposes slightly different data, so please refer to their respective schemas for more information. [Login policies](./login-policy.md) are global. All other policy type... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.08801566064357758,
0.01698390394449234,
0.004588690586388111,
-0.03866840898990631,
0.0484282523393631,
-0.06128372624516487,
0.0880824625492096,
-0.034321852028369904,
0.026692967861890793,
0.013834573328495026,
0.0452222004532814,
0.06361652910709381,
0.06584267318248749,
0.0335513576... | 0.071374 |
[start](../run/README.md#initializing) | Negative | `set` | `deny` | | [Notification](notification-policy.md) | Routes and filters notifications | Positive | `map` | `inbox`, `slack`, `webhook` | | [Plan](terraform-plan-policy.md) | Gives feedback on [runs](../run/README.md) after [planning](../run/proposed.md#planning... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.027484998106956482,
0.015764933079481125,
0.03887561708688736,
-0.0027011996135115623,
0.061723120510578156,
-0.08060614764690399,
0.029607508331537247,
-0.041035693138837814,
0.022333433851599693,
0.09354879707098007,
-0.01616171933710575,
-0.04215298220515251,
0.05522099509835243,
-0.... | 0.121654 |
creating a custom notification: === "Rego v1" ```opa package spacelift inbox contains { "title": "Tracked run finished!", "body": sprintf("Run ID: %s", [run.id]), "severity": "INFO", } if { run := input.run\_updated.run run.type == "TRACKED" run.state == "FINISHED" } ``` === "Rego v0" ```opa package spacelift inbox[{ "... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.04333055764436722,
0.05516214296221733,
0.037759602069854736,
0.05741409584879875,
-0.014028722420334816,
0.009648843668401241,
0.053774524480104446,
0.05504710599780083,
-0.006419057957828045,
-0.01872406154870987,
-0.021283062174916267,
-0.04370226338505745,
-0.017596250399947166,
0.0... | 0.123145 |
that "flag" will be a set. flag contains "never" if { false } ``` === "Rego v0" ```opa package spacelift # This is what Spacelift will query for when evaluating policies. result = { "approve": approve, "reject": reject, "flag": flag, "sample": sample, } # Default to ensure that "approve" is defined. default approve = f... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.07022977620363235,
0.07501302659511566,
-0.02906975895166397,
0.03786107152700424,
0.0033009075559675694,
-0.04299795627593994,
0.11874537914991379,
0.0025886017829179764,
-0.04987309128046036,
-0.023259194567799568,
0.03950507193803787,
-0.03249809890985489,
-0.01799841783940792,
-0.01... | 0.024162 |
[task](task-run-policy.md) policy): === "Rego v1" ```opa sample if count(deny) == 0 ``` === "Rego v0" ```opa sample { count(deny) == 0 } ``` You can also sample a certain percentage of policy evaluations. Given that we don't generally allow nondeterministic evaluations, you'd need to depend on a source of randomness in... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.09725607931613922,
0.03225069120526314,
-0.036838021129369736,
0.01621953770518303,
-0.028277646750211716,
-0.08408178389072418,
0.018781496211886406,
0.029800288379192352,
0.0062996442429721355,
0.027507783845067024,
-0.05614301189780235,
-0.05783797800540924,
0.0006934161647222936,
-0... | 0.091326 |
workbench (including access to previous inputs) is only available to \*\*Spacelift account administrators\*\*. ## Policy library OPA can be difficult to learn, especially if you are just starting out with it. [The policy workbench](#policy-workbench) is great for helping you get policies right, but with the policy libr... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.09710612148046494,
0.0238550566136837,
-0.016041167080402374,
-0.011788228526711464,
-0.019002823159098625,
0.08053577691316605,
0.08833538740873337,
0.005467024631798267,
-0.03673271834850311,
0.006465318612754345,
-0.028251677751541138,
-0.031378667801618576,
0.014419835060834885,
-0.... | 0.002988 |
=== "Rego v1" ```opa title="deny-sandbox.rego" package spacelift deny contains sprintf("don't push to %s", [branch]) if { branch := input.commit.branch branch == "sandbox" } ``` === "Rego v0" ```opa title="deny-sandbox.rego" package spacelift deny[sprintf("don't push to %s", [branch])] { branch := input.commit.branch b... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.015585810877382755,
0.0918983742594719,
0.04769963026046753,
0.024617651477456093,
0.03220469132065773,
-0.05394267663359642,
0.05062926560640335,
-0.031234625726938248,
-0.006375676486641169,
-0.02371237799525261,
0.03231033682823181,
-0.051541611552238464,
0.028105756267905235,
0.0013... | 0.082113 |
=== "Rego v0" ```rego title="network-review.rego" package spacelift network\_review\_required { input.run.flags[\_] == "review:network" } approve { not network\_review\_required } approve { input.reviews.current.approvals[\_].session.teams[\_] == "DBA" } ``` There are a few things worth knowing about flags: - They are ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/README.md | main | spacelift | [
-0.07875507324934006,
0.04495861753821373,
-0.02784147299826145,
0.01540094893425703,
0.03044896386563778,
-0.002420186996459961,
0.0967995896935463,
-0.06690908223390579,
-0.042849574238061905,
0.022776909172534943,
-0.015856606885790825,
-0.06059218570590019,
0.004136351868510246,
0.0153... | 0.076378 |
# Plan policy ## Purpose Plan policies are evaluated during a planning phase after a vendor-specific change preview command (e.g. `terraform plan`) executes successfully. The body of the change is exported to JSON and parts of it are combined with Spacelift metadata to form the data input to the policy. Plan policies a... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.07780175656080246,
0.09179554879665375,
0.062414057552814484,
0.001784048043191433,
0.05166754126548767,
-0.06593991070985794,
-0.019422125071287155,
-0.05762387439608574,
-0.01449725590646267,
0.101203054189682,
-0.025529049336910248,
-0.021109476685523987,
0.011410892009735107,
0.0034... | 0.082516 |
"message": "string - commit message" }, "created\_at": "number - creation Unix timestamp in nanoseconds", "drift\_detection": "boolean - is this a drift detection run", "flags" : ["string - list of flags set on the run by other policies" ], "id": "string - the run ID", "runtime\_config": { "before\_init": ["string - co... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.006097002420574427,
0.03191317245364189,
0.002210161881521344,
0.016245340928435326,
0.06986898183822632,
-0.061763085424900055,
0.014402513392269611,
-0.02354397065937519,
0.05186503753066063,
0.10214648395776749,
-0.011176549829542637,
-0.0954316183924675,
0.03250676766037941,
-0.0313... | 0.107007 |
"message": "string - commit message" }, "worker\_pool": { "id": "string - the worker pool ID, if it is private", "labels": ["string - list of arbitrary, user-defined selectors, if the worker pool is private"], "name": "string - name of the worker pool, if it is private", "public": "boolean - is the worker pool public" ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.050645776093006134,
0.06068280339241028,
0.01984199695289135,
0.038232993334531784,
0.03080233559012413,
-0.06484704464673996,
0.09328309446573257,
-0.12242476642131805,
0.07080469280481339,
0.09737497568130493,
-0.013819513842463493,
-0.0996832326054573,
0.06638306379318237,
0.01909273... | 0.049196 |
modules are used to provision resources, add this command to the list of [`after\_plan` hooks](../stack/stack-settings.md#customizing-workflow): ```bash terraform show -json spacelift.plan | jq -c '.configuration' > configuration.custom.spacelift.json ``` The data will be available in the policy input as `input.third\_... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.052512027323246,
0.06486544758081436,
0.011963988654315472,
0.03389982879161835,
0.01945646107196808,
-0.046092793345451355,
-0.03876429423689842,
-0.0247474517673254,
0.008463644422590733,
0.01566624827682972,
-0.018863653764128685,
-0.057158179581165314,
0.06127360463142395,
0.0137172... | 0.048318 |
input.terraform.resource\_changes[\_] resource.change.actions[\_] == "create" # This is what decides whether the rule captures a resource. # There may be an arbitrary number of conditions, and they all must # succeed for the rule to take effect. resource.type == "aws\_iam\_access\_key" } ``` This slightly more sophisti... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.04951558634638786,
0.05120573937892914,
0.036845654249191284,
0.011363095603883266,
0.035793885588645935,
-0.07655072212219238,
0.025478890165686607,
-0.11922074109315872,
0.05832904949784279,
0.10091078281402588,
0.008057632483541965,
-0.01448039896786213,
0.0733855739235878,
-0.005197... | 0.041657 |
violations, but when this approach is taken to an extreme it can make your life difficult. We suggest that you \_at most\_ \*\*deny\*\* when the run is \_PROPOSED\_, which will send a failure status to the GitHub commit, then give the reviewer a chance to approve the change anyways. If you want a human to take another ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.09585925936698914,
0.08801265805959702,
0.02232322469353676,
-0.006741139106452465,
0.03986067324876785,
-0.04674558341503143,
0.03322836384177208,
-0.016773905605077744,
-0.021044686436653137,
0.05172737315297127,
-0.002701399615034461,
-0.048410478979349136,
0.05828256532549858,
-0.01... | 0.064946 |
"charlie"} not allowlisted[author] } ``` === "Rego v0" ```opa package spacelift warn[sprintf(message, [author])] { message := "%s is not on the allowlist - human review required" author := input.spacelift.commit.author allowlisted := { "alice", "bob", "charlie" } not allowlisted[author] } ``` ### Require commits to be ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.06749030202627182,
0.07203737646341324,
0.03729395568370819,
0.0407056026160717,
0.04211888462305069,
-0.048531703650951385,
0.04578842967748642,
-0.05130375549197197,
-0.032089270651340485,
0.11489646136760712,
-0.027994349598884583,
-0.062221381813287735,
0.025299176573753357,
-0.0009... | 0.03328 |
multipliers. blasts\_radii\_by\_type := { "aws\_ecs\_cluster": 20, "aws\_ecs\_user": 10, "aws\_ecs\_role": 5 } # By default, blast radius has a value of 1. blast\_radius\_for\_type(type) = 1 { not blasts\_radii\_by\_type[type] } blast\_radius\_for\_type(type) = ret { blasts\_radii\_by\_type[type] = ret } ``` ### Cost m... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/terraform-plan-policy.md | main | spacelift | [
-0.04362819343805313,
0.11432193964719772,
-0.04546583443880081,
0.013365537859499454,
0.07833296805620193,
-0.10538012534379959,
0.0617755651473999,
0.024916086345911026,
0.028660161420702934,
0.07490701973438263,
0.041568074375391006,
-0.1184605285525322,
0.04926762357354164,
-0.00460566... | 0.101532 |
# Trigger policy !!! tip While trigger policies are still available, [stack dependencies](../stack/stack-dependencies.md) are a simpler, more intuitive way to define dependencies between stacks. Often, infrastructure consists of a number of interconnected projects (which we call [stacks](../stack/README.md)). Some proj... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/trigger-policy.md | main | spacelift | [
-0.043016575276851654,
-0.09727045893669128,
0.03286103531718254,
-0.05023292079567909,
0.0933774933218956,
-0.051499366760253906,
-0.010505489073693752,
-0.02067522704601288,
0.01869463548064232,
0.023371275514364243,
0.0023997488897293806,
0.05066162347793579,
0.025857582688331604,
0.004... | 0.099752 |
triggered the run, if applicable", "type": "string - type of the run", "updated\_at": "number - last update Unix timestamp in nanoseconds", "user\_provided\_metadata": [ "string - blobs of metadata provided using spacectl or the API when interacting with this run" ] }, "stack": { "administrative": "boolean - is the sta... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/trigger-policy.md | main | spacelift | [
-0.047194089740514755,
-0.02923036739230156,
-0.06193350628018379,
0.023439999669790268,
-0.030160291120409966,
-0.05238509923219681,
0.0701807364821434,
0.0385727733373642,
0.007748309522867203,
0.026297489181160927,
0.03708887845277786,
-0.061288829892873764,
0.020828058943152428,
-0.059... | 0.132887 |
both is the same. ### Triggered by new module version When triggered by a \_new module version\_, each policy request will receive this data input schema: ```json { "module": { // Module for which the new version was released "administrative": "boolean - is the stack administrative", "branch": "string - tracked branch ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/trigger-policy.md | main | spacelift | [
-0.04522917419672012,
-0.006498026195913553,
-0.01724061369895935,
-0.022691605612635612,
0.04741203039884567,
-0.04507598280906677,
0.021306244656443596,
-0.05216389521956444,
0.047804269939661026,
0.04160149395465851,
0.07812757790088654,
0.005552968941628933,
0.04784391075372696,
-0.023... | 0.061153 |
be explicitly added to the list. To fix those issues in the policy, we'll use stack [labels](../stack/stack-settings.md#labels). Labels are completely arbitrary strings that you can attach to individual stacks, and we can use them to have "client" stacks subscribe to "parent" ones. ```opa package spacelift trigger[stac... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/trigger-policy.md | main | spacelift | [
-0.0964609831571579,
-0.05318361520767212,
0.019487706944346428,
0.021931836381554604,
-0.03367513045668602,
-0.010789573192596436,
0.06697732955217361,
0.012523590587079525,
-0.05737386271357536,
-0.016809266060590744,
-0.0027401032857596874,
-0.03818443790078163,
-0.0000672142268740572,
... | 0.070615 |
version to be used. This simple policy will trigger a run on all stacks that use the latest version of the module when a new version is released: ```opa package spacelift trigger[stack.id] { stack := input.stacks[\_] } ``` Auto-updates will only affect the stacks the trigger policy has access to (via inheritance or dir... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/trigger-policy.md | main | spacelift | [
-0.0686715617775917,
-0.07985135167837143,
-0.003553894115611911,
0.03462974354624748,
-0.021977761760354042,
-0.06014643982052803,
-0.013224046677350998,
-0.01364528201520443,
-0.02819806896150112,
-0.05367681384086609,
0.06254933029413223,
0.035010192543268204,
-0.06820820271968842,
-0.0... | 0.019833 |
# Initialization policy !!! warning Initialization policies are deprecated. Use [approval policies](./approval-policy.md) instead for a more flexible, powerful way to control which runs are allowed to proceed. Existing users with initialization policies should migrate as soon as possible using our [migration guide](#mi... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/run-initialization-policy.md | main | spacelift | [
-0.0362948440015316,
0.002685737796127796,
0.03954499959945679,
-0.010251816362142563,
0.07570482790470123,
-0.06609880179166794,
-0.009317160584032536,
-0.041259102523326874,
-0.024510804563760757,
0.1375027894973755,
-0.0278188306838274,
0.00243940157815814,
0.037371162325143814,
-0.0058... | 0.054003 |
or trigger policy who triggered the run, if applicable", "type": "string - PROPOSED or TRACKED", "updated\_at": "number - last update Unix timestamp in nanoseconds", "user\_provided\_metadata": [ "string - blobs of metadata provided using spacectl or the API when interacting with this run" ] }, "stack": { "administrati... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/run-initialization-policy.md | main | spacelift | [
-0.054093655198812485,
-0.03328479453921318,
-0.055161625146865845,
0.0005633282125927508,
-0.009468047879636288,
-0.028011223301291466,
0.08308058232069016,
0.024257240816950798,
0.004605812486261129,
0.06027102842926979,
0.027757292613387108,
-0.04988270252943039,
0.012695906683802605,
-... | 0.126965 |
One of the above examples explicitly allowlisted an OpenTofu/Terraform formatting check. This example policy ensures that command always gets executed first. Per the [Anna Karenina principle](https://en.wikipedia.org/wiki/Anna\_Karenina\_principle){: rel="nofollow"}, this check is most elegantly defined as a \_negation... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/run-initialization-policy.md | main | spacelift | [
-0.027750259265303612,
0.09728258103132248,
0.031012075021862984,
0.03919214755296707,
0.03998057544231415,
-0.07251623272895813,
0.04095975682139397,
-0.06931353360414505,
0.006648980546742678,
0.049970705062150955,
-0.000756586785428226,
-0.0583789199590683,
-0.00006602924986509606,
0.02... | 0.053956 |
# Notification policy ## Purpose Notification policies can filter, route, and adjust the body of notification messages sent by Spacelift. The policy works at the [space level](../spaces/README.md), meaning that it does not need to be attached to a specific [stack](../stack/README.md). Notification policices always veri... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.01804071106016636,
-0.10915576666593552,
0.04018564522266388,
0.029216155409812927,
0.03797213360667229,
-0.018642740324139595,
0.0738680362701416,
-0.013819477520883083,
0.013922430574893951,
0.03384600952267647,
-0.024481337517499924,
-0.021607721224427223,
0.02904294803738594,
0.0316... | 0.102583 |
on the vendor" }, "phase": "string enum - plan | apply" } ], "command": "string", "commit": { "author": "string", "branch": "string", "created\_at": "number (timestamp in nanoseconds)", "hash": "string", "message": "string", "url": "string" }, "created\_at": "number (timestamp in nanoseconds)", "creator\_session": { "a... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.005315251648426056,
0.047193825244903564,
-0.1050746887922287,
0.011886714026331902,
0.026566047221422195,
-0.05243441462516785,
0.038350656628608704,
-0.0014266632497310638,
0.04678570106625557,
0.07187726348638535,
0.02396446466445923,
-0.04439108446240425,
0.03768416494131088,
-0.034... | 0.155187 |
check any policies in that space, including policies inherited from other spaces. === "Internal errors" Most internal errors will check for notification policies inside of the root space. However if the policy is reporting about a component that belongs to a certain space (and can determine which space it is), then it ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.0370602160692215,
-0.05561074614524841,
0.06643316894769669,
0.00464793061837554,
0.060829710215330124,
-0.04077732190489769,
0.0853210985660553,
-0.04259705916047096,
0.055363234132528305,
0.02476482093334198,
-0.0006952693802304566,
-0.0732242614030838,
0.08632966876029968,
-0.0084597... | 0.029837 |
contains { "channel\_id": "C0000000000", "message": sprintf("http://example.app.spacelift.io/stack/%s/run/%s is trying to attach a policy!", [stack.id, run.id]), } if { stack := input.run\_updated.stack run := input.run\_updated.run run.type == "TRACKED" run.state == "UNCONFIRMED" some change in run.changes change.phas... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.018489977344870567,
0.04064352437853813,
0.02663056179881096,
0.03454530984163284,
0.021824246272444725,
-0.040245670825242996,
0.04262169823050499,
0.03551347553730011,
0.02678811177611351,
0.027997365221381187,
0.027276040986180305,
-0.08897606283426285,
-0.009814762510359287,
0.01183... | 0.112711 |
to use when sending the request. #### Filtering webhook requests Filter and select webhooks using the received input data. You can create rules where only specific actions trigger a webhook being sent. For example, we could define a rule to allow a webhook to be sent about any drift detection run: === "Rego v1" ```opa ... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.12481186538934708,
0.052621714770793915,
-0.0007874667644500732,
0.0042476714588701725,
0.02318434603512287,
-0.0858524739742279,
0.06993149220943451,
-0.024728961288928986,
-0.003685389179736376,
-0.015372546389698982,
-0.02713419310748577,
-0.14748609066009521,
-0.005635686218738556,
... | 0.136801 |
making Discord webhooks, follow their [official webhook guide](https://support.discord.com/hc/en-us/articles/228383668){: rel="nofollow"}. After creating the webhook on both Discord and Spacelift, you will need to define a new webhook rule like this: === "Rego v1" ```opa # Send updates about tracked runs to discord. we... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.07154954969882965,
-0.03174055367708206,
0.016443731263279915,
0.0368959978222847,
0.005922903772443533,
-0.06189023330807686,
-0.022944455966353416,
-0.021874435245990753,
0.022106941789388657,
-0.01062893308699131,
-0.01684359833598137,
-0.10827954858541489,
0.021360140293836594,
-0.0... | 0.095826 |
has finished", [input.account.name, stack.id, run.id]), } if { stack := input.run\_updated.stack run := input.run\_updated.run run.state == "FINISHED" } ``` === "Rego v0" ```opa package spacelift import future.keywords.contains import future.keywords.if pull\_request contains { "commit": run.commit.hash, "body": sprint... | https://github.com/spacelift-io/user-documentation/blob/main/docs/concepts/policy/notification-policy.md | main | spacelift | [
-0.062140241265296936,
-0.011156653985381126,
0.014295781962573528,
-0.008639277890324593,
-0.06070346012711525,
-0.06699855625629425,
0.03759082779288292,
0.053054142743349075,
0.02457285486161709,
0.017420373857021332,
-0.006596207153052092,
-0.06141921132802963,
0.0013985965633764863,
-... | 0.084645 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.