@pulumiverse/vercel 4.6.0 → 5.0.0-alpha.1782928871
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/accessGroup.d.ts +3 -2
- package/accessGroup.js +3 -2
- package/accessGroup.js.map +1 -1
- package/accessGroupProject.d.ts +4 -3
- package/accessGroupProject.js +4 -3
- package/accessGroupProject.js.map +1 -1
- package/attackChallengeMode.d.ts +4 -4
- package/attackChallengeMode.js +4 -4
- package/blobObject.d.ts +177 -0
- package/blobObject.js +89 -0
- package/blobObject.js.map +1 -0
- package/blobProjectConnection.d.ts +144 -0
- package/blobProjectConnection.js +105 -0
- package/blobProjectConnection.js.map +1 -0
- package/blobStore.d.ts +159 -0
- package/blobStore.js +100 -0
- package/blobStore.js.map +1 -0
- package/bulkRedirects.d.ts +135 -0
- package/bulkRedirects.js +114 -0
- package/bulkRedirects.js.map +1 -0
- package/customEnvironment.d.ts +7 -9
- package/customEnvironment.js +7 -9
- package/customEnvironment.js.map +1 -1
- package/deployment.d.ts +36 -0
- package/deployment.js +27 -0
- package/deployment.js.map +1 -1
- package/dnsRecord.d.ts +8 -12
- package/dnsRecord.js +8 -12
- package/dnsRecord.js.map +1 -1
- package/edgeConfig.d.ts +7 -9
- package/edgeConfig.js +7 -9
- package/edgeConfig.js.map +1 -1
- package/edgeConfigItem.d.ts +6 -10
- package/edgeConfigItem.js +6 -10
- package/edgeConfigItem.js.map +1 -1
- package/edgeConfigSchema.d.ts +6 -8
- package/edgeConfigSchema.js +6 -8
- package/edgeConfigSchema.js.map +1 -1
- package/edgeConfigToken.d.ts +7 -11
- package/edgeConfigToken.js +7 -11
- package/edgeConfigToken.js.map +1 -1
- package/featureFlagConfig.d.ts +167 -0
- package/featureFlagConfig.js +131 -0
- package/featureFlagConfig.js.map +1 -0
- package/featureFlagDefinition.d.ts +160 -0
- package/featureFlagDefinition.js +111 -0
- package/featureFlagDefinition.js.map +1 -0
- package/featureFlagSdkKey.d.ts +160 -0
- package/featureFlagSdkKey.js +120 -0
- package/featureFlagSdkKey.js.map +1 -0
- package/featureFlagSegment.d.ts +191 -0
- package/featureFlagSegment.js +126 -0
- package/featureFlagSegment.js.map +1 -0
- package/firewallBypass.d.ts +3 -2
- package/firewallBypass.js +3 -2
- package/firewallBypass.js.map +1 -1
- package/firewallConfig.d.ts +2 -0
- package/firewallConfig.js +2 -0
- package/firewallConfig.js.map +1 -1
- package/getBlobObject.d.ts +100 -0
- package/getBlobObject.js +32 -0
- package/getBlobObject.js.map +1 -0
- package/getBlobProjectConnections.d.ts +91 -0
- package/getBlobProjectConnections.js +64 -0
- package/getBlobProjectConnections.js.map +1 -0
- package/getBlobStore.d.ts +104 -0
- package/getBlobStore.js +54 -0
- package/getBlobStore.js.map +1 -0
- package/getBlobStoreSecrets.d.ts +80 -0
- package/getBlobStoreSecrets.js +54 -0
- package/getBlobStoreSecrets.js.map +1 -0
- package/getBlobStores.d.ts +63 -0
- package/getBlobStores.js +48 -0
- package/getBlobStores.js.map +1 -0
- package/getBulkRedirects.d.ts +97 -0
- package/getBulkRedirects.js +60 -0
- package/getBulkRedirects.js.map +1 -0
- package/getFeatureFlag.d.ts +121 -0
- package/getFeatureFlag.js +60 -0
- package/getFeatureFlag.js.map +1 -0
- package/getFeatureFlagSdkKey.d.ts +100 -0
- package/getFeatureFlagSdkKey.js +60 -0
- package/getFeatureFlagSdkKey.js.map +1 -0
- package/getFeatureFlagSegment.d.ts +113 -0
- package/getFeatureFlagSegment.js +60 -0
- package/getFeatureFlagSegment.js.map +1 -0
- package/getFile.d.ts +9 -0
- package/getFile.js.map +1 -1
- package/getPrebuiltProject.d.ts +51 -0
- package/getPrebuiltProject.js +42 -0
- package/getPrebuiltProject.js.map +1 -1
- package/getProject.d.ts +14 -4
- package/getProject.js.map +1 -1
- package/getProjectDirectory.d.ts +47 -0
- package/getProjectDirectory.js +38 -0
- package/getProjectDirectory.js.map +1 -1
- package/getProjectRoutes.d.ts +89 -0
- package/getProjectRoutes.js +62 -0
- package/getProjectRoutes.js.map +1 -0
- package/index.d.ts +63 -0
- package/index.js +88 -2
- package/index.js.map +1 -1
- package/logDrain.d.ts +6 -8
- package/logDrain.js +6 -8
- package/logDrain.js.map +1 -1
- package/microfrontendGroup.d.ts +4 -5
- package/microfrontendGroup.js +4 -5
- package/microfrontendGroup.js.map +1 -1
- package/microfrontendGroupMembership.d.ts +4 -7
- package/microfrontendGroupMembership.js +4 -7
- package/microfrontendGroupMembership.js.map +1 -1
- package/package.json +2 -2
- package/project.d.ts +75 -38
- package/project.js +53 -14
- package/project.js.map +1 -1
- package/projectCrons.d.ts +6 -7
- package/projectCrons.js +6 -7
- package/projectCrons.js.map +1 -1
- package/projectDeploymentRetention.d.ts +12 -4
- package/projectDeploymentRetention.js +12 -4
- package/projectDeploymentRetention.js.map +1 -1
- package/projectDomain.d.ts +6 -8
- package/projectDomain.js +6 -8
- package/projectDomain.js.map +1 -1
- package/projectEnvironmentVariable.d.ts +24 -20
- package/projectEnvironmentVariable.js +23 -16
- package/projectEnvironmentVariable.js.map +1 -1
- package/projectEnvironmentVariables.d.ts +18 -5
- package/projectEnvironmentVariables.js +18 -5
- package/projectEnvironmentVariables.js.map +1 -1
- package/projectMembers.d.ts +6 -0
- package/projectMembers.js +6 -0
- package/projectMembers.js.map +1 -1
- package/projectProtectionBypass.d.ts +171 -0
- package/projectProtectionBypass.js +119 -0
- package/projectProtectionBypass.js.map +1 -0
- package/projectRoute.d.ts +219 -0
- package/projectRoute.js +148 -0
- package/projectRoute.js.map +1 -0
- package/sharedEnvironmentVariable.d.ts +28 -9
- package/sharedEnvironmentVariable.js +27 -5
- package/sharedEnvironmentVariable.js.map +1 -1
- package/teamConfig.d.ts +3 -2
- package/teamConfig.js +3 -2
- package/teamConfig.js.map +1 -1
- package/teamMember.d.ts +3 -1
- package/teamMember.js +3 -1
- package/teamMember.js.map +1 -1
- package/types/input.d.ts +324 -4
- package/types/output.d.ts +705 -2
- package/userToken.d.ts +186 -0
- package/userToken.js +115 -0
- package/userToken.js.map +1 -0
package/deployment.js
CHANGED
|
@@ -5,6 +5,33 @@ Object.defineProperty(exports, "__esModule", { value: true });
|
|
|
5
5
|
exports.Deployment = void 0;
|
|
6
6
|
const pulumi = require("@pulumi/pulumi");
|
|
7
7
|
const utilities = require("./utilities");
|
|
8
|
+
/**
|
|
9
|
+
* Provides a Deployment resource.
|
|
10
|
+
*
|
|
11
|
+
* A Deployment is the result of building your Project and making it available through a live URL.
|
|
12
|
+
*
|
|
13
|
+
* When making deployments, the Project will be uploaded and transformed into a production-ready output through the use of a Build Step.
|
|
14
|
+
*
|
|
15
|
+
* Once the build step has completed successfully, a new, immutable deployment will be made available at the preview URL. Deployments are retained indefinitely unless deleted manually.
|
|
16
|
+
*
|
|
17
|
+
* > In order to provide files to a deployment, you'll need to use the `vercel.getFile` or `vercel.getProjectDirectory` data sources.
|
|
18
|
+
*
|
|
19
|
+
* > If you are creating Deployments through terraform and intend to use both preview and production
|
|
20
|
+
* deployments, you may wish to 'layer' your terraform, creating the Project with a different set of
|
|
21
|
+
* terraform to your Deployment.
|
|
22
|
+
*
|
|
23
|
+
* ## Example Usage
|
|
24
|
+
*
|
|
25
|
+
* ```typescript
|
|
26
|
+
* import * as pulumi from "@pulumi/pulumi";
|
|
27
|
+
* import * as vercel from "@pulumiverse/vercel";
|
|
28
|
+
*
|
|
29
|
+
* // In this example, we are assuming that a nextjs UI
|
|
30
|
+
* // exists in a `ui` directory and any terraform exists in a `terraform` directory.
|
|
31
|
+
* // E.g.
|
|
32
|
+
* // ```
|
|
33
|
+
* ```
|
|
34
|
+
*/
|
|
8
35
|
class Deployment extends pulumi.CustomResource {
|
|
9
36
|
/**
|
|
10
37
|
* Get an existing Deployment resource's state with the given name, ID, and optional extra
|
package/deployment.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"deployment.js","sourceRoot":"","sources":["../deployment.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC,MAAa,UAAW,SAAQ,MAAM,CAAC,cAAc;IACjD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAuB,EAAE,IAAmC;QACrH,OAAO,IAAI,UAAU,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACjE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,UAAU,CAAC,YAAY,CAAC;IAC3D,CAAC;
|
|
1
|
+
{"version":3,"file":"deployment.js","sourceRoot":"","sources":["../deployment.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,MAAa,UAAW,SAAQ,MAAM,CAAC,cAAc;IACjD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAuB,EAAE,IAAmC;QACrH,OAAO,IAAI,UAAU,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACjE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,UAAU,CAAC,YAAY,CAAC;IAC3D,CAAC;IA+DD,YAAY,IAAY,EAAE,WAA8C,EAAE,IAAmC;QACzG,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAA0C,CAAC;YACzD,cAAc,CAAC,qBAAqB,CAAC,GAAG,KAAK,EAAE,mBAAmB,CAAC;YACnE,cAAc,CAAC,iBAAiB,CAAC,GAAG,KAAK,EAAE,eAAe,CAAC;YAC3D,cAAc,CAAC,SAAS,CAAC,GAAG,KAAK,EAAE,OAAO,CAAC;YAC3C,cAAc,CAAC,aAAa,CAAC,GAAG,KAAK,EAAE,WAAW,CAAC;YACnD,cAAc,CAAC,OAAO,CAAC,GAAG,KAAK,EAAE,KAAK,CAAC;YACvC,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,WAAW,CAAC,GAAG,KAAK,EAAE,SAAS,CAAC;YAC/C,cAAc,CAAC,iBAAiB,CAAC,GAAG,KAAK,EAAE,eAAe,CAAC;YAC3D,cAAc,CAAC,KAAK,CAAC,GAAG,KAAK,EAAE,GAAG,CAAC;YACnC,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;YACzC,cAAc,CAAC,KAAK,CAAC,GAAG,KAAK,EAAE,GAAG,CAAC;SACtC;aAAM;YACH,MAAM,IAAI,GAAG,WAAyC,CAAC;YACvD,IAAI,IAAI,EAAE,SAAS,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC5C,MAAM,IAAI,KAAK,CAAC,uCAAuC,CAAC,CAAC;aAC5D;YACD,cAAc,CAAC,qBAAqB,CAAC,GAAG,IAAI,EAAE,mBAAmB,CAAC;YAClE,cAAc,CAAC,iBAAiB,CAAC,GAAG,IAAI,EAAE,eAAe,CAAC;YAC1D,cAAc,CAAC,aAAa,CAAC,GAAG,IAAI,EAAE,WAAW,CAAC,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC;YAChG,cAAc,CAAC,OAAO,CAAC,GAAG,IAAI,EAAE,KAAK,CAAC;YACtC,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,WAAW,CAAC,GAAG,IAAI,EAAE,SAAS,CAAC;YAC9C,cAAc,CAAC,iBAAiB,CAAC,GAAG,IAAI,EAAE,eAAe,CAAC;YAC1D,cAAc,CAAC,KAAK,CAAC,GAAG,IAAI,EAAE,GAAG,CAAC;YAClC,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;YACxC,cAAc,CAAC,SAAS,CAAC,GAAG,SAAS,CAAC,OAAO,CAAC;YAC9C,cAAc,CAAC,KAAK,CAAC,GAAG,SAAS,CAAC,OAAO,CAAC;SAC7C;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,MAAM,UAAU,GAAG,EAAE,uBAAuB,EAAE,CAAC,aAAa,CAAC,EAAE,CAAC;QAChE,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,IAAI,EAAE,UAAU,CAAC,CAAC;QAC7C,KAAK,CAAC,UAAU,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IAC/D,CAAC;;AAlIL,gCAmIC;AArHG,gBAAgB;AACO,uBAAY,GAAG,oCAAoC,CAAC"}
|
package/dnsRecord.d.ts
CHANGED
|
@@ -82,25 +82,21 @@ import * as outputs from "./types/output";
|
|
|
82
82
|
*
|
|
83
83
|
* ## Import
|
|
84
84
|
*
|
|
85
|
-
*
|
|
85
|
+
* The `pulumi import` command can be used, for example:
|
|
86
86
|
*
|
|
87
|
+
* If importing into a personal account, or with a team configured on
|
|
87
88
|
* the provider, simply use the record id.
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
91
|
-
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
89
|
+
* - recordId can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
90
|
+
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
92
91
|
*
|
|
93
92
|
* ```sh
|
|
94
93
|
* $ pulumi import vercel:index/dnsRecord:DnsRecord example rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
95
94
|
* ```
|
|
96
95
|
*
|
|
97
|
-
* Alternatively, you can import via the
|
|
98
|
-
*
|
|
99
|
-
* -
|
|
100
|
-
*
|
|
101
|
-
* - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
102
|
-
*
|
|
103
|
-
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
96
|
+
* Alternatively, you can import via the teamId and record_id.
|
|
97
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
98
|
+
* - recordId can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
99
|
+
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
104
100
|
*
|
|
105
101
|
* ```sh
|
|
106
102
|
* $ pulumi import vercel:index/dnsRecord:DnsRecord example team_xxxxxxxxxxxxxxxxxxxxxxxx/rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/dnsRecord.js
CHANGED
|
@@ -86,25 +86,21 @@ const utilities = require("./utilities");
|
|
|
86
86
|
*
|
|
87
87
|
* ## Import
|
|
88
88
|
*
|
|
89
|
-
*
|
|
89
|
+
* The `pulumi import` command can be used, for example:
|
|
90
90
|
*
|
|
91
|
+
* If importing into a personal account, or with a team configured on
|
|
91
92
|
* the provider, simply use the record id.
|
|
92
|
-
*
|
|
93
|
-
*
|
|
94
|
-
*
|
|
95
|
-
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
93
|
+
* - recordId can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
94
|
+
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
96
95
|
*
|
|
97
96
|
* ```sh
|
|
98
97
|
* $ pulumi import vercel:index/dnsRecord:DnsRecord example rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
99
98
|
* ```
|
|
100
99
|
*
|
|
101
|
-
* Alternatively, you can import via the
|
|
102
|
-
*
|
|
103
|
-
* -
|
|
104
|
-
*
|
|
105
|
-
* - record_id can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
106
|
-
*
|
|
107
|
-
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
100
|
+
* Alternatively, you can import via the teamId and record_id.
|
|
101
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
102
|
+
* - recordId can be taken from the network tab inside developer tools, while you are on the domains page,
|
|
103
|
+
* or can be queried from the Vercel API directly (https://vercel.com/docs/rest-api/endpoints/dns#list-existing-dns-records).
|
|
108
104
|
*
|
|
109
105
|
* ```sh
|
|
110
106
|
* $ pulumi import vercel:index/dnsRecord:DnsRecord example team_xxxxxxxxxxxxxxxxxxxxxxxx/rec_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/dnsRecord.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"dnsRecord.js","sourceRoot":"","sources":["../dnsRecord.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"dnsRecord.js","sourceRoot":"","sources":["../dnsRecord.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AAGzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoGG;AACH,MAAa,SAAU,SAAQ,MAAM,CAAC,cAAc;IAChD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAsB,EAAE,IAAmC;QACpH,OAAO,IAAI,SAAS,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IAChE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,SAAS,CAAC,YAAY,CAAC;IAC1D,CAAC;IAsDD,YAAY,IAAY,EAAE,WAA4C,EAAE,IAAmC;QACvG,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAyC,CAAC;YACxD,cAAc,CAAC,SAAS,CAAC,GAAG,KAAK,EAAE,OAAO,CAAC;YAC3C,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;YACzC,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,KAAK,CAAC,GAAG,KAAK,EAAE,GAAG,CAAC;YACnC,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;YACzC,cAAc,CAAC,KAAK,CAAC,GAAG,KAAK,EAAE,GAAG,CAAC;YACnC,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,OAAO,CAAC,GAAG,KAAK,EAAE,KAAK,CAAC;SAC1C;aAAM;YACH,MAAM,IAAI,GAAG,WAAwC,CAAC;YACtD,IAAI,IAAI,EAAE,MAAM,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACzC,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;aACzD;YACD,IAAI,IAAI,EAAE,IAAI,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACvC,MAAM,IAAI,KAAK,CAAC,kCAAkC,CAAC,CAAC;aACvD;YACD,cAAc,CAAC,SAAS,CAAC,GAAG,IAAI,EAAE,OAAO,CAAC;YAC1C,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;YACxC,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,KAAK,CAAC,GAAG,IAAI,EAAE,GAAG,CAAC;YAClC,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;YACxC,cAAc,CAAC,KAAK,CAAC,GAAG,IAAI,EAAE,GAAG,CAAC;YAClC,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,OAAO,CAAC,GAAG,IAAI,EAAE,KAAK,CAAC;SACzC;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,SAAS,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IAC9D,CAAC;;AAlHL,8BAmHC;AArGG,gBAAgB;AACO,sBAAY,GAAG,kCAAkC,CAAC"}
|
package/edgeConfig.d.ts
CHANGED
|
@@ -21,8 +21,8 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
21
21
|
* targets: [
|
|
22
22
|
* "production",
|
|
23
23
|
* "preview",
|
|
24
|
-
* "development",
|
|
25
24
|
* ],
|
|
25
|
+
* sensitive: true,
|
|
26
26
|
* key: "EDGE_CONFIG",
|
|
27
27
|
* value: exampleEdgeConfigToken.connectionString,
|
|
28
28
|
* });
|
|
@@ -30,21 +30,19 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
30
30
|
*
|
|
31
31
|
* ## Import
|
|
32
32
|
*
|
|
33
|
-
*
|
|
33
|
+
* The `pulumi import` command can be used, for example:
|
|
34
34
|
*
|
|
35
|
+
* If importing into a personal account, or with a team configured on
|
|
35
36
|
* the provider, simply use the edge config id.
|
|
36
|
-
*
|
|
37
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
37
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
38
38
|
*
|
|
39
39
|
* ```sh
|
|
40
40
|
* $ pulumi import vercel:index/edgeConfig:EdgeConfig example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
41
41
|
* ```
|
|
42
42
|
*
|
|
43
|
-
* Alternatively, you can import via the
|
|
44
|
-
*
|
|
45
|
-
* -
|
|
46
|
-
*
|
|
47
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
43
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
44
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
45
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
48
46
|
*
|
|
49
47
|
* ```sh
|
|
50
48
|
* $ pulumi import vercel:index/edgeConfig:EdgeConfig example team_xxxxxxxxxxxxxxxxxxxxxxxx/ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/edgeConfig.js
CHANGED
|
@@ -27,8 +27,8 @@ const utilities = require("./utilities");
|
|
|
27
27
|
* targets: [
|
|
28
28
|
* "production",
|
|
29
29
|
* "preview",
|
|
30
|
-
* "development",
|
|
31
30
|
* ],
|
|
31
|
+
* sensitive: true,
|
|
32
32
|
* key: "EDGE_CONFIG",
|
|
33
33
|
* value: exampleEdgeConfigToken.connectionString,
|
|
34
34
|
* });
|
|
@@ -36,21 +36,19 @@ const utilities = require("./utilities");
|
|
|
36
36
|
*
|
|
37
37
|
* ## Import
|
|
38
38
|
*
|
|
39
|
-
*
|
|
39
|
+
* The `pulumi import` command can be used, for example:
|
|
40
40
|
*
|
|
41
|
+
* If importing into a personal account, or with a team configured on
|
|
41
42
|
* the provider, simply use the edge config id.
|
|
42
|
-
*
|
|
43
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
43
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
44
44
|
*
|
|
45
45
|
* ```sh
|
|
46
46
|
* $ pulumi import vercel:index/edgeConfig:EdgeConfig example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
47
47
|
* ```
|
|
48
48
|
*
|
|
49
|
-
* Alternatively, you can import via the
|
|
50
|
-
*
|
|
51
|
-
* -
|
|
52
|
-
*
|
|
53
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
49
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
50
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
51
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
54
52
|
*
|
|
55
53
|
* ```sh
|
|
56
54
|
* $ pulumi import vercel:index/edgeConfig:EdgeConfig example team_xxxxxxxxxxxxxxxxxxxxxxxx/ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/edgeConfig.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"edgeConfig.js","sourceRoot":"","sources":["../edgeConfig.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"edgeConfig.js","sourceRoot":"","sources":["../edgeConfig.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AACH,MAAa,UAAW,SAAQ,MAAM,CAAC,cAAc;IACjD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAAuB,EAAE,IAAmC;QACrH,OAAO,IAAI,UAAU,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACjE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,UAAU,CAAC,YAAY,CAAC;IAC3D,CAAC;IAmBD,YAAY,IAAY,EAAE,WAA8C,EAAE,IAAmC;QACzG,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAA0C,CAAC;YACzD,cAAc,CAAC,MAAM,CAAC,GAAG,KAAK,EAAE,IAAI,CAAC;YACrC,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;SAC5C;aAAM;YACH,MAAM,IAAI,GAAG,WAAyC,CAAC;YACvD,cAAc,CAAC,MAAM,CAAC,GAAG,IAAI,EAAE,IAAI,CAAC;YACpC,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;SAC3C;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,UAAU,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IAC/D,CAAC;;AA3DL,gCA4DC;AA9CG,gBAAgB;AACO,uBAAY,GAAG,oCAAoC,CAAC"}
|
package/edgeConfigItem.d.ts
CHANGED
|
@@ -32,24 +32,20 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
32
32
|
*
|
|
33
33
|
* ## Import
|
|
34
34
|
*
|
|
35
|
-
*
|
|
35
|
+
* The `pulumi import` command can be used, for example:
|
|
36
36
|
*
|
|
37
|
+
* If importing into a personal account, or with a team configured on
|
|
37
38
|
* the provider, simply use the edge config id and the key of the item to import.
|
|
38
|
-
*
|
|
39
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
40
|
-
*
|
|
39
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
41
40
|
* - key is the key of teh item to import.
|
|
42
41
|
*
|
|
43
42
|
* ```sh
|
|
44
43
|
* $ pulumi import vercel:index/edgeConfigItem:EdgeConfigItem example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/example_key
|
|
45
44
|
* ```
|
|
46
45
|
*
|
|
47
|
-
* Alternatively, you can import via the team_id,
|
|
48
|
-
*
|
|
49
|
-
* -
|
|
50
|
-
*
|
|
51
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
52
|
-
*
|
|
46
|
+
* Alternatively, you can import via the team_id, edgeConfigId and the key of the item to import.
|
|
47
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
48
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
53
49
|
* - key is the key of the item to import.
|
|
54
50
|
*
|
|
55
51
|
* ```sh
|
package/edgeConfigItem.js
CHANGED
|
@@ -38,24 +38,20 @@ const utilities = require("./utilities");
|
|
|
38
38
|
*
|
|
39
39
|
* ## Import
|
|
40
40
|
*
|
|
41
|
-
*
|
|
41
|
+
* The `pulumi import` command can be used, for example:
|
|
42
42
|
*
|
|
43
|
+
* If importing into a personal account, or with a team configured on
|
|
43
44
|
* the provider, simply use the edge config id and the key of the item to import.
|
|
44
|
-
*
|
|
45
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
46
|
-
*
|
|
45
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
47
46
|
* - key is the key of teh item to import.
|
|
48
47
|
*
|
|
49
48
|
* ```sh
|
|
50
49
|
* $ pulumi import vercel:index/edgeConfigItem:EdgeConfigItem example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/example_key
|
|
51
50
|
* ```
|
|
52
51
|
*
|
|
53
|
-
* Alternatively, you can import via the team_id,
|
|
54
|
-
*
|
|
55
|
-
* -
|
|
56
|
-
*
|
|
57
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
58
|
-
*
|
|
52
|
+
* Alternatively, you can import via the team_id, edgeConfigId and the key of the item to import.
|
|
53
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
54
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
59
55
|
* - key is the key of the item to import.
|
|
60
56
|
*
|
|
61
57
|
* ```sh
|
package/edgeConfigItem.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"edgeConfigItem.js","sourceRoot":"","sources":["../edgeConfigItem.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"edgeConfigItem.js","sourceRoot":"","sources":["../edgeConfigItem.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG;AACH,MAAa,cAAe,SAAQ,MAAM,CAAC,cAAc;IACrD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAA2B,EAAE,IAAmC;QACzH,OAAO,IAAI,cAAc,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACrE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,cAAc,CAAC,YAAY,CAAC;IAC/D,CAAC;IA+BD,YAAY,IAAY,EAAE,WAAsD,EAAE,IAAmC;QACjH,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAA8C,CAAC;YAC7D,cAAc,CAAC,cAAc,CAAC,GAAG,KAAK,EAAE,YAAY,CAAC;YACrD,cAAc,CAAC,KAAK,CAAC,GAAG,KAAK,EAAE,GAAG,CAAC;YACnC,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;YACzC,cAAc,CAAC,OAAO,CAAC,GAAG,KAAK,EAAE,KAAK,CAAC;YACvC,cAAc,CAAC,WAAW,CAAC,GAAG,KAAK,EAAE,SAAS,CAAC;SAClD;aAAM;YACH,MAAM,IAAI,GAAG,WAA6C,CAAC;YAC3D,IAAI,IAAI,EAAE,YAAY,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC/C,MAAM,IAAI,KAAK,CAAC,0CAA0C,CAAC,CAAC;aAC/D;YACD,IAAI,IAAI,EAAE,GAAG,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACtC,MAAM,IAAI,KAAK,CAAC,iCAAiC,CAAC,CAAC;aACtD;YACD,cAAc,CAAC,cAAc,CAAC,GAAG,IAAI,EAAE,YAAY,CAAC;YACpD,cAAc,CAAC,KAAK,CAAC,GAAG,IAAI,EAAE,GAAG,CAAC;YAClC,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;YACxC,cAAc,CAAC,OAAO,CAAC,GAAG,IAAI,EAAE,KAAK,CAAC;YACtC,cAAc,CAAC,WAAW,CAAC,GAAG,IAAI,EAAE,SAAS,CAAC;SACjD;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,cAAc,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACnE,CAAC;;AAnFL,wCAoFC;AAtEG,gBAAgB;AACO,2BAAY,GAAG,4CAA4C,CAAC"}
|
package/edgeConfigSchema.d.ts
CHANGED
|
@@ -27,21 +27,19 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
27
27
|
*
|
|
28
28
|
* ## Import
|
|
29
29
|
*
|
|
30
|
-
*
|
|
30
|
+
* The `pulumi import` command can be used, for example:
|
|
31
31
|
*
|
|
32
|
+
* If importing into a personal account, or with a team configured on
|
|
32
33
|
* the provider, simply use the edge config id.
|
|
33
|
-
*
|
|
34
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
34
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
35
35
|
*
|
|
36
36
|
* ```sh
|
|
37
37
|
* $ pulumi import vercel:index/edgeConfigSchema:EdgeConfigSchema example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
38
38
|
* ```
|
|
39
39
|
*
|
|
40
|
-
* Alternatively, you can import via the
|
|
41
|
-
*
|
|
42
|
-
* -
|
|
43
|
-
*
|
|
44
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
40
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
41
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
42
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
45
43
|
*
|
|
46
44
|
* ```sh
|
|
47
45
|
* $ pulumi import vercel:index/edgeConfigSchema:EdgeConfigSchema example team_xxxxxxxxxxxxxxxxxxxxxxxx/ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/edgeConfigSchema.js
CHANGED
|
@@ -33,21 +33,19 @@ const utilities = require("./utilities");
|
|
|
33
33
|
*
|
|
34
34
|
* ## Import
|
|
35
35
|
*
|
|
36
|
-
*
|
|
36
|
+
* The `pulumi import` command can be used, for example:
|
|
37
37
|
*
|
|
38
|
+
* If importing into a personal account, or with a team configured on
|
|
38
39
|
* the provider, simply use the edge config id.
|
|
39
|
-
*
|
|
40
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
40
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
41
41
|
*
|
|
42
42
|
* ```sh
|
|
43
43
|
* $ pulumi import vercel:index/edgeConfigSchema:EdgeConfigSchema example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
|
44
44
|
* ```
|
|
45
45
|
*
|
|
46
|
-
* Alternatively, you can import via the
|
|
47
|
-
*
|
|
48
|
-
* -
|
|
49
|
-
*
|
|
50
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
46
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
47
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
48
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
51
49
|
*
|
|
52
50
|
* ```sh
|
|
53
51
|
* $ pulumi import vercel:index/edgeConfigSchema:EdgeConfigSchema example team_xxxxxxxxxxxxxxxxxxxxxxxx/ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
|
package/edgeConfigSchema.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"edgeConfigSchema.js","sourceRoot":"","sources":["../edgeConfigSchema.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"edgeConfigSchema.js","sourceRoot":"","sources":["../edgeConfigSchema.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6CG;AACH,MAAa,gBAAiB,SAAQ,MAAM,CAAC,cAAc;IACvD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAA6B,EAAE,IAAmC;QAC3H,OAAO,IAAI,gBAAgB,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACvE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,gBAAgB,CAAC,YAAY,CAAC;IACjE,CAAC;IAmBD,YAAY,IAAY,EAAE,WAA0D,EAAE,IAAmC;QACrH,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAAgD,CAAC;YAC/D,cAAc,CAAC,YAAY,CAAC,GAAG,KAAK,EAAE,UAAU,CAAC;YACjD,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;SAC5C;aAAM;YACH,MAAM,IAAI,GAAG,WAA+C,CAAC;YAC7D,IAAI,IAAI,EAAE,UAAU,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC7C,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;aAC7D;YACD,cAAc,CAAC,YAAY,CAAC,GAAG,IAAI,EAAE,UAAU,CAAC;YAChD,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;SAC3C;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,KAAK,CAAC,gBAAgB,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACrE,CAAC;;AA9DL,4CA+DC;AAjDG,gBAAgB;AACO,6BAAY,GAAG,gDAAgD,CAAC"}
|
package/edgeConfigToken.d.ts
CHANGED
|
@@ -23,8 +23,8 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
23
23
|
* targets: [
|
|
24
24
|
* "production",
|
|
25
25
|
* "preview",
|
|
26
|
-
* "development",
|
|
27
26
|
* ],
|
|
27
|
+
* sensitive: true,
|
|
28
28
|
* key: "EDGE_CONFIG",
|
|
29
29
|
* value: exampleEdgeConfigToken.connectionString,
|
|
30
30
|
* });
|
|
@@ -32,24 +32,20 @@ import * as pulumi from "@pulumi/pulumi";
|
|
|
32
32
|
*
|
|
33
33
|
* ## Import
|
|
34
34
|
*
|
|
35
|
-
*
|
|
35
|
+
* The `pulumi import` command can be used, for example:
|
|
36
36
|
*
|
|
37
|
+
* If importing into a personal account, or with a team configured on
|
|
37
38
|
* the provider, simply use the edge config id and token value.
|
|
38
|
-
*
|
|
39
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
40
|
-
*
|
|
39
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
41
40
|
* - token can be found in the Vercel UI under Storage, Edge Config, the specific Edge Config, Tokens.
|
|
42
41
|
*
|
|
43
42
|
* ```sh
|
|
44
43
|
* $ pulumi import vercel:index/edgeConfigToken:EdgeConfigToken example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
|
|
45
44
|
* ```
|
|
46
45
|
*
|
|
47
|
-
* Alternatively, you can import via the
|
|
48
|
-
*
|
|
49
|
-
* -
|
|
50
|
-
*
|
|
51
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
52
|
-
*
|
|
46
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
47
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
48
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
53
49
|
* - token can be found in the Vercel UI under Storage, Edge Config, the specific Edge Config, Tokens.
|
|
54
50
|
*
|
|
55
51
|
* ```sh
|
package/edgeConfigToken.js
CHANGED
|
@@ -29,8 +29,8 @@ const utilities = require("./utilities");
|
|
|
29
29
|
* targets: [
|
|
30
30
|
* "production",
|
|
31
31
|
* "preview",
|
|
32
|
-
* "development",
|
|
33
32
|
* ],
|
|
33
|
+
* sensitive: true,
|
|
34
34
|
* key: "EDGE_CONFIG",
|
|
35
35
|
* value: exampleEdgeConfigToken.connectionString,
|
|
36
36
|
* });
|
|
@@ -38,24 +38,20 @@ const utilities = require("./utilities");
|
|
|
38
38
|
*
|
|
39
39
|
* ## Import
|
|
40
40
|
*
|
|
41
|
-
*
|
|
41
|
+
* The `pulumi import` command can be used, for example:
|
|
42
42
|
*
|
|
43
|
+
* If importing into a personal account, or with a team configured on
|
|
43
44
|
* the provider, simply use the edge config id and token value.
|
|
44
|
-
*
|
|
45
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
46
|
-
*
|
|
45
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
47
46
|
* - token can be found in the Vercel UI under Storage, Edge Config, the specific Edge Config, Tokens.
|
|
48
47
|
*
|
|
49
48
|
* ```sh
|
|
50
49
|
* $ pulumi import vercel:index/edgeConfigToken:EdgeConfigToken example ecfg_xxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
|
|
51
50
|
* ```
|
|
52
51
|
*
|
|
53
|
-
* Alternatively, you can import via the
|
|
54
|
-
*
|
|
55
|
-
* -
|
|
56
|
-
*
|
|
57
|
-
* - edge_config_id can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
58
|
-
*
|
|
52
|
+
* Alternatively, you can import via the teamId and edge_config_id.
|
|
53
|
+
* - teamId can be found in the team `settings` tab in the Vercel UI.
|
|
54
|
+
* - edgeConfigId can be found by navigating to the Edge Config in the Vercel UI. It should begin with `ecfg_`.
|
|
59
55
|
* - token can be found in the Vercel UI under Storage, Edge Config, the specific Edge Config, Tokens.
|
|
60
56
|
*
|
|
61
57
|
* ```sh
|
package/edgeConfigToken.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"edgeConfigToken.js","sourceRoot":"","sources":["../edgeConfigToken.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC
|
|
1
|
+
{"version":3,"file":"edgeConfigToken.js","sourceRoot":"","sources":["../edgeConfigToken.ts"],"names":[],"mappings":";AAAA,sEAAsE;AACtE,iFAAiF;;;AAEjF,yCAAyC;AACzC,yCAAyC;AAEzC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoDG;AACH,MAAa,eAAgB,SAAQ,MAAM,CAAC,cAAc;IACtD;;;;;;;;OAQG;IACI,MAAM,CAAC,GAAG,CAAC,IAAY,EAAE,EAA2B,EAAE,KAA4B,EAAE,IAAmC;QAC1H,OAAO,IAAI,eAAe,CAAC,IAAI,EAAO,KAAK,EAAE,EAAE,GAAG,IAAI,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAC;IACtE,CAAC;IAKD;;;OAGG;IACI,MAAM,CAAC,UAAU,CAAC,GAAQ;QAC7B,IAAI,GAAG,KAAK,SAAS,IAAI,GAAG,KAAK,IAAI,EAAE;YACnC,OAAO,KAAK,CAAC;SAChB;QACD,OAAO,GAAG,CAAC,cAAc,CAAC,KAAK,eAAe,CAAC,YAAY,CAAC;IAChE,CAAC;IA+BD,YAAY,IAAY,EAAE,WAAwD,EAAE,IAAmC;QACnH,IAAI,cAAc,GAAkB,EAAE,CAAC;QACvC,IAAI,GAAG,IAAI,IAAI,EAAE,CAAC;QAClB,IAAI,IAAI,CAAC,EAAE,EAAE;YACT,MAAM,KAAK,GAAG,WAA+C,CAAC;YAC9D,cAAc,CAAC,kBAAkB,CAAC,GAAG,KAAK,EAAE,gBAAgB,CAAC;YAC7D,cAAc,CAAC,cAAc,CAAC,GAAG,KAAK,EAAE,YAAY,CAAC;YACrD,cAAc,CAAC,OAAO,CAAC,GAAG,KAAK,EAAE,KAAK,CAAC;YACvC,cAAc,CAAC,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,CAAC;YACzC,cAAc,CAAC,OAAO,CAAC,GAAG,KAAK,EAAE,KAAK,CAAC;SAC1C;aAAM;YACH,MAAM,IAAI,GAAG,WAA8C,CAAC;YAC5D,IAAI,IAAI,EAAE,YAAY,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBAC/C,MAAM,IAAI,KAAK,CAAC,0CAA0C,CAAC,CAAC;aAC/D;YACD,IAAI,IAAI,EAAE,KAAK,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE;gBACxC,MAAM,IAAI,KAAK,CAAC,mCAAmC,CAAC,CAAC;aACxD;YACD,cAAc,CAAC,cAAc,CAAC,GAAG,IAAI,EAAE,YAAY,CAAC;YACpD,cAAc,CAAC,OAAO,CAAC,GAAG,IAAI,EAAE,KAAK,CAAC;YACtC,cAAc,CAAC,QAAQ,CAAC,GAAG,IAAI,EAAE,MAAM,CAAC;YACxC,cAAc,CAAC,kBAAkB,CAAC,GAAG,SAAS,CAAC,OAAO,CAAC;YACvD,cAAc,CAAC,OAAO,CAAC,GAAG,SAAS,CAAC,OAAO,CAAC;SAC/C;QACD,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,SAAS,CAAC,oBAAoB,EAAE,EAAE,IAAI,CAAC,CAAC;QACnE,MAAM,UAAU,GAAG,EAAE,uBAAuB,EAAE,CAAC,kBAAkB,EAAE,OAAO,CAAC,EAAE,CAAC;QAC9E,IAAI,GAAG,MAAM,CAAC,YAAY,CAAC,IAAI,EAAE,UAAU,CAAC,CAAC;QAC7C,KAAK,CAAC,eAAe,CAAC,YAAY,EAAE,IAAI,EAAE,cAAc,EAAE,IAAI,CAAC,CAAC;IACpE,CAAC;;AArFL,0CAsFC;AAxEG,gBAAgB;AACO,4BAAY,GAAG,8CAA8C,CAAC"}
|
|
@@ -0,0 +1,167 @@
|
|
|
1
|
+
import * as pulumi from "@pulumi/pulumi";
|
|
2
|
+
import * as inputs from "./types/input";
|
|
3
|
+
import * as outputs from "./types/output";
|
|
4
|
+
/**
|
|
5
|
+
* Provides a Feature Flag Config resource.
|
|
6
|
+
*
|
|
7
|
+
* This resource manages the simplified static rollout shape for a flag across `production`, `preview`, and `development`.
|
|
8
|
+
*
|
|
9
|
+
* Use this resource together with `vercel.FeatureFlagDefinition` when Terraform should own the rollout. If you omit this resource, the flag definition can still exist while rollout is managed through the Vercel dashboard.
|
|
10
|
+
*
|
|
11
|
+
* It is intentionally strict: linked environments, rules, and target overrides must not already be configured on the flag when Terraform manages this resource.
|
|
12
|
+
*
|
|
13
|
+
* Deleting this resource only removes it from Terraform state. The flag and its current configuration stay in Vercel.
|
|
14
|
+
*
|
|
15
|
+
* ## Example Usage
|
|
16
|
+
*
|
|
17
|
+
* ```typescript
|
|
18
|
+
* import * as pulumi from "@pulumi/pulumi";
|
|
19
|
+
* import * as vercel from "@pulumiverse/vercel";
|
|
20
|
+
*
|
|
21
|
+
* const example = new vercel.Project("example", {name: "feature-flag-example"});
|
|
22
|
+
* const exampleFeatureFlagDefinition = new vercel.FeatureFlagDefinition("example", {
|
|
23
|
+
* projectId: example.id,
|
|
24
|
+
* key: "checkout-redesign",
|
|
25
|
+
* description: "Controls the checkout experience",
|
|
26
|
+
* kind: "string",
|
|
27
|
+
* variants: [
|
|
28
|
+
* {
|
|
29
|
+
* id: "control",
|
|
30
|
+
* label: "Control",
|
|
31
|
+
* valueString: "control",
|
|
32
|
+
* },
|
|
33
|
+
* {
|
|
34
|
+
* id: "treatment",
|
|
35
|
+
* label: "Treatment",
|
|
36
|
+
* valueString: "treatment",
|
|
37
|
+
* },
|
|
38
|
+
* ],
|
|
39
|
+
* });
|
|
40
|
+
* const exampleFeatureFlagConfig = new vercel.FeatureFlagConfig("example", {
|
|
41
|
+
* projectId: example.id,
|
|
42
|
+
* flagId: exampleFeatureFlagDefinition.id,
|
|
43
|
+
* production: {
|
|
44
|
+
* enabled: true,
|
|
45
|
+
* defaultVariantId: "control",
|
|
46
|
+
* disabledVariantId: "control",
|
|
47
|
+
* },
|
|
48
|
+
* preview: {
|
|
49
|
+
* enabled: true,
|
|
50
|
+
* defaultVariantId: "treatment",
|
|
51
|
+
* disabledVariantId: "control",
|
|
52
|
+
* },
|
|
53
|
+
* development: {
|
|
54
|
+
* enabled: false,
|
|
55
|
+
* defaultVariantId: "treatment",
|
|
56
|
+
* disabledVariantId: "control",
|
|
57
|
+
* },
|
|
58
|
+
* });
|
|
59
|
+
* ```
|
|
60
|
+
*/
|
|
61
|
+
export declare class FeatureFlagConfig extends pulumi.CustomResource {
|
|
62
|
+
/**
|
|
63
|
+
* Get an existing FeatureFlagConfig resource's state with the given name, ID, and optional extra
|
|
64
|
+
* properties used to qualify the lookup.
|
|
65
|
+
*
|
|
66
|
+
* @param name The _unique_ name of the resulting resource.
|
|
67
|
+
* @param id The _unique_ provider ID of the resource to lookup.
|
|
68
|
+
* @param state Any extra arguments used during the lookup.
|
|
69
|
+
* @param opts Optional settings to control the behavior of the CustomResource.
|
|
70
|
+
*/
|
|
71
|
+
static get(name: string, id: pulumi.Input<pulumi.ID>, state?: FeatureFlagConfigState, opts?: pulumi.CustomResourceOptions): FeatureFlagConfig;
|
|
72
|
+
/**
|
|
73
|
+
* Returns true if the given object is an instance of FeatureFlagConfig. This is designed to work even
|
|
74
|
+
* when multiple copies of the Pulumi SDK have been loaded into the same process.
|
|
75
|
+
*/
|
|
76
|
+
static isInstance(obj: any): obj is FeatureFlagConfig;
|
|
77
|
+
/**
|
|
78
|
+
* The development environment behavior for this flag.
|
|
79
|
+
*/
|
|
80
|
+
readonly development: pulumi.Output<outputs.FeatureFlagConfigDevelopment>;
|
|
81
|
+
/**
|
|
82
|
+
* The ID of the feature flag whose config Terraform should manage.
|
|
83
|
+
*/
|
|
84
|
+
readonly flagId: pulumi.Output<string>;
|
|
85
|
+
/**
|
|
86
|
+
* The preview environment behavior for this flag.
|
|
87
|
+
*/
|
|
88
|
+
readonly preview: pulumi.Output<outputs.FeatureFlagConfigPreview>;
|
|
89
|
+
/**
|
|
90
|
+
* The production environment behavior for this flag.
|
|
91
|
+
*/
|
|
92
|
+
readonly production: pulumi.Output<outputs.FeatureFlagConfigProduction>;
|
|
93
|
+
/**
|
|
94
|
+
* The ID of the Vercel project that owns the flag.
|
|
95
|
+
*/
|
|
96
|
+
readonly projectId: pulumi.Output<string>;
|
|
97
|
+
/**
|
|
98
|
+
* The ID of the Vercel team. Required when configuring a team resource if a default team has not been set in the provider.
|
|
99
|
+
*/
|
|
100
|
+
readonly teamId: pulumi.Output<string>;
|
|
101
|
+
/**
|
|
102
|
+
* Create a FeatureFlagConfig resource with the given unique name, arguments, and options.
|
|
103
|
+
*
|
|
104
|
+
* @param name The _unique_ name of the resource.
|
|
105
|
+
* @param args The arguments to use to populate this resource's properties.
|
|
106
|
+
* @param opts A bag of options that control this resource's behavior.
|
|
107
|
+
*/
|
|
108
|
+
constructor(name: string, args: FeatureFlagConfigArgs, opts?: pulumi.CustomResourceOptions);
|
|
109
|
+
}
|
|
110
|
+
/**
|
|
111
|
+
* Input properties used for looking up and filtering FeatureFlagConfig resources.
|
|
112
|
+
*/
|
|
113
|
+
export interface FeatureFlagConfigState {
|
|
114
|
+
/**
|
|
115
|
+
* The development environment behavior for this flag.
|
|
116
|
+
*/
|
|
117
|
+
development?: pulumi.Input<inputs.FeatureFlagConfigDevelopment>;
|
|
118
|
+
/**
|
|
119
|
+
* The ID of the feature flag whose config Terraform should manage.
|
|
120
|
+
*/
|
|
121
|
+
flagId?: pulumi.Input<string>;
|
|
122
|
+
/**
|
|
123
|
+
* The preview environment behavior for this flag.
|
|
124
|
+
*/
|
|
125
|
+
preview?: pulumi.Input<inputs.FeatureFlagConfigPreview>;
|
|
126
|
+
/**
|
|
127
|
+
* The production environment behavior for this flag.
|
|
128
|
+
*/
|
|
129
|
+
production?: pulumi.Input<inputs.FeatureFlagConfigProduction>;
|
|
130
|
+
/**
|
|
131
|
+
* The ID of the Vercel project that owns the flag.
|
|
132
|
+
*/
|
|
133
|
+
projectId?: pulumi.Input<string>;
|
|
134
|
+
/**
|
|
135
|
+
* The ID of the Vercel team. Required when configuring a team resource if a default team has not been set in the provider.
|
|
136
|
+
*/
|
|
137
|
+
teamId?: pulumi.Input<string>;
|
|
138
|
+
}
|
|
139
|
+
/**
|
|
140
|
+
* The set of arguments for constructing a FeatureFlagConfig resource.
|
|
141
|
+
*/
|
|
142
|
+
export interface FeatureFlagConfigArgs {
|
|
143
|
+
/**
|
|
144
|
+
* The development environment behavior for this flag.
|
|
145
|
+
*/
|
|
146
|
+
development: pulumi.Input<inputs.FeatureFlagConfigDevelopment>;
|
|
147
|
+
/**
|
|
148
|
+
* The ID of the feature flag whose config Terraform should manage.
|
|
149
|
+
*/
|
|
150
|
+
flagId: pulumi.Input<string>;
|
|
151
|
+
/**
|
|
152
|
+
* The preview environment behavior for this flag.
|
|
153
|
+
*/
|
|
154
|
+
preview: pulumi.Input<inputs.FeatureFlagConfigPreview>;
|
|
155
|
+
/**
|
|
156
|
+
* The production environment behavior for this flag.
|
|
157
|
+
*/
|
|
158
|
+
production: pulumi.Input<inputs.FeatureFlagConfigProduction>;
|
|
159
|
+
/**
|
|
160
|
+
* The ID of the Vercel project that owns the flag.
|
|
161
|
+
*/
|
|
162
|
+
projectId: pulumi.Input<string>;
|
|
163
|
+
/**
|
|
164
|
+
* The ID of the Vercel team. Required when configuring a team resource if a default team has not been set in the provider.
|
|
165
|
+
*/
|
|
166
|
+
teamId?: pulumi.Input<string>;
|
|
167
|
+
}
|