prehistoric-printer-15534
06/25/2023, 2:35 PMpulumi up
in a remote machine, based on a pulumi preview
run that was manually approved.
Is there a way to achieve this? Ideally, I imagine a --etag
flag in the Pulumi CLI, that accepts some pre-existing diff checksum.wide-island-42641
06/26/2023, 6:59 AMwide-island-42641
06/26/2023, 6:59 AMwide-island-42641
06/26/2023, 6:59 AMwide-island-42641
06/26/2023, 7:00 AMwide-island-42641
06/26/2023, 7:00 AMwide-island-42641
06/26/2023, 7:00 AMadorable-analyst-27426
06/26/2023, 9:12 AMbusy-queen-53310
06/26/2023, 3:02 PMadorable-analyst-27426
06/26/2023, 3:58 PMflaky-holiday-20645
06/26/2023, 5:35 PMvpcConfig
for lambda callback functions, but pulumi doesn’t detect those changes when doing a pulumi up
, is there something special that needs to be done to get pulumi to identify this configuration change?brief-car-60542
06/27/2023, 5:19 AMimport { services } from './service';
import { clusters } from './cluster';
// get full cluster array output
export const clusterRegion: aws.ecs.Cluster[] = clusters[aws.Region.USWest2] as aws.ecs.Cluster[];
// get correct id
export const clusterRegionId = clusterRegion[0]?.id || '';
// get full service array output
export const Services: aws.ecs.Service[] = services[aws.Region.USWest2] as aws.ecs.Service[];
// !!!no value!!!
export const ServicesID = Services[0]?.id || '';
I try to check everything.
Just dont understand what is the different?wide-cat-87818
06/27/2023, 12:04 PMnice-application-79035
06/27/2023, 9:15 PMbrief-car-60542
06/27/2023, 9:25 PMrich-glass-69138
06/28/2023, 10:33 AMcreamy-ambulance-91738
06/28/2023, 3:24 PMType Name Plan
+ pulumi:pulumi:Stack cloudflared-tunnels-sandbox create
+ ├─ components:tunnels:Tunnel gb-lon-li-cfdtunnel create
+ │ ├─ random:index:RandomId gb-lon-li-cfdtunnel-argoSecret create
+ │ └─ cloudflare:index:Tunnel gb-lon-li-cfdtunnel-tunnel create
+ ├─ components:tunnels:Tunnel blease-test create
+ │ ├─ random:index:RandomId blease-test-argoSecret create
+ │ └─ cloudflare:index:Tunnel blease-test-tunnel create
+ ├─ components:tunnels:TunnelRoute blease-test create
+ │ └─ cloudflare:index:TunnelRoute blease-test-route-192.168.1.0/24 create
+ └─ components:tunnels:TunnelConfig gb-lon-li-cfdtunnel create
+ └─ cloudflare:index:TunnelConfig gb-lon-li-cfdtunnel-tunnel-config create
However when I go to describe the stack the indentation/ordering is off. cloudflareindexTunnelConfig is under componentstunnelsTunnelRoute:
+ pulumi:pulumi:Stack: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:pulumi:Stack::cloudflared-tunnels-sandbox]
+ components:tunnels:Tunnel: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel::gb-lon-li-cfdtunnel]
+ components:tunnels:Tunnel: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel::blease-test]
+ random:index/randomId:RandomId: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel$random:index/randomId:RandomId::blease-test-argoSecret]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:random::default_4_13_2::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
byteLength: 35
+ random:index/randomId:RandomId: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel$random:index/randomId:RandomId::gb-lon-li-cfdtunnel-argoSecret]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:random::default_4_13_2::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
byteLength: 35
+ cloudflare:index/tunnel:Tunnel: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel$cloudflare:index/tunnel:Tunnel::gb-lon-li-cfdtunnel-tunnel]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:cloudflare::default_5_4_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
accountId : "00991122"
configSrc : "cloudflare"
name : "gb-lon-li-cfdtunnel"
secret : output<string>
+ cloudflare:index/tunnel:Tunnel: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:Tunnel$cloudflare:index/tunnel:Tunnel::blease-test-tunnel]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:cloudflare::default_5_4_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
accountId : "00991122"
configSrc : "cloudflare"
name : "blease-test"
secret : output<string>
+ components:tunnels:TunnelConfig: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:TunnelConfig::gb-lon-li-cfdtunnel]
cloudflareAccountId: "00991122"
cloudflareTunnelId : output<string>
cloudflareZone : "<http://foobar.com|foobar.com>"
tunnelServices : {
my-app: "<http://myapp.com>"
}
+ components:tunnels:TunnelRoute: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:TunnelRoute::blease-test]
cloudflareAccountId: "00991122"
cloudflareTunnelId : output<string>
privateNetworks : [
[0]: "192.168.1.0/24"
]
+ cloudflare:index/tunnelRoute:TunnelRoute: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:TunnelRoute$cloudflare:index/tunnelRoute:TunnelRoute::blease-test-route-192.168.1.0/24]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:cloudflare::default_5_4_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
accountId : "00991122"
network : "192.168.1.0/24"
tunnelId : output<string>
+ cloudflare:index/tunnelConfig:TunnelConfig: (create)
[urn=urn:pulumi:sandbox::cloudflared-tunnels::components:tunnels:TunnelConfig$cloudflare:index/tunnelConfig:TunnelConfig::gb-lon-li-cfdtunnel-tunnel-config]
[provider=urn:pulumi:sandbox::cloudflared-tunnels::pulumi:providers:cloudflare::default_5_4_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
accountId : "00991122"
config : {
ingressRules: [
[0]: {
hostname : "<http://my-app.connect.com|my-app.connect.com>"
service : "<http://myapp.com>"
}
[1]: {
service : "http_status:404"
}
]
warpRouting : {
enabled : true
}
}
tunnelId : output<string>
colossal-vr-62639
06/28/2023, 4:31 PMincalculable-garage-67131
06/29/2023, 4:32 PMcrd2pulumi -n
generation.
This looks like its related to a Pulumi node dependency.
The generated package.json is:
{
"name": "@pulumi/crds",
"version": "",
"scripts": {
"build": "tsc",
"install": "node scripts/install-pulumi-plugin.js resource crds "
},
"dependencies": {
"@pulumi/pulumi": "^3.42.0"
},
"devDependencies": {
"@types/node": "^14",
"typescript": "^4.3.5"
},
"pulumi": {
"resource": true,
"name": "crds"
}
}
npm install fails, the pulumi-crds are no longer located at the referenced link.
> install
> node scripts/install-pulumi-plugin.js resource crds
error: 404 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-crds/releases/latest>. If this is a private GitHub repository, try providing a token via the GITHUB_TOKEN environment variable. See: <https://github.com/settings/tokens>
There was an error installing the resource provider plugin. You may try to manually installing the plugin by running `pulumi plugin install resource crds`
The npm audit / npm audit fix does not fix this:
semver <7.5.2
Severity: moderate
semver vulnerable to Regular Expression Denial of Service - <https://github.com/advisories/GHSA-c2qf-rxjj-qqgw>
fix available via `npm audit fix`
node_modules/make-dir/node_modules/semver
make-dir 2.0.0 - 3.1.0
Depends on vulnerable versions of semver
node_modules/make-dir
@mapbox/node-pre-gyp >=1.0.1
Depends on vulnerable versions of make-dir
node_modules/@mapbox/node-pre-gyp
grpc 1.24.8 - 1.24.11
Depends on vulnerable versions of @mapbox/node-pre-gyp
node_modules/grpc
--force
lowers the pulumi verion dependency.
"dependencies": {
"@pulumi/pulumi": "^0.14.3"
},
We are enterprise customers and we use crd2pulumi. This is blocking our ability to maintain our deployments.square-knife-25838
06/29/2023, 7:22 PMmodern-eve-91943
06/30/2023, 2:20 PMquaint-book-39362
06/30/2023, 3:38 PMaloof-sugar-9157
06/30/2023, 5:31 PMwooden-egg-90698
06/30/2023, 6:15 PMbroad-island-71889
06/30/2023, 6:34 PMmicroscopic-park-81177
07/01/2023, 2:47 PM<http://aws.lb|aws.lb>
there's https://www.pulumi.com/registry/packages/aws/api-docs/alb/listener/ and https://www.pulumi.com/registry/packages/aws/api-docs/alb/listenerrule/. For OIDC auth to an LB, they both take an argument - aws.lb.ListenerDefaultActionAuthenticateOidcArgs and aws.lb.ListenerRuleActionAuthenticateOidcArgs. These appear to be identical on the AWS API backend. https://docs.aws.amazon.com/elasticloadbalancing/latest/APIReference/API_AuthenticateOidcActionConfig.html. But are they interchangeable in Pulumi? Can I use the ListenerRuleAction to initalize a Listener's default action? Seems like I should be able toprehistoric-activity-61023
07/01/2023, 3:36 PMrapid-receptionist-28528
07/01/2023, 7:15 PMError creating API Gateway Deployment: BadRequestException: No integration defined for method
Any Idea ?billowy-engine-58246
07/02/2023, 5:03 AMswift-truck-84096
07/03/2023, 5:58 AM