ambitious-father-68746
03/20/2023, 11:36 AMquaint-jelly-14306
03/20/2023, 12:20 PMechoing-address-44214
03/21/2023, 1:22 AMasync prefix(): Promise<string> {
const parameter = await aws.ssm.getParameter(
{ name: "/prefix" }
).then(x=>x.value);
return parameter;
}
const name: string = convert prefix() to string
super("ruwen/RedisCluster", prefix() + id, {}, opts);
echoing-address-44214
03/21/2023, 2:52 AMconst password = new random.RandomPassword(
props.name + "-redis-auth-token",
{
length: 50,
special: true,
overrideSpecial: "!&#$^<>-",
},
{ parent: this, ...opts }
);
new aws.secretsmanager.SecretVersion(
props.name + "-redis-secret-version",
{
secretId: secret.id,
secretString: password.result,
},
{ parent: this, ...opts }
);
From my tests:
const parametersCaptured = new Map<string, any>();
beforeAll(() => {
pulumi.runtime.setMocks(
{
newResource: function (args: pulumi.runtime.MockResourceArgs): {
id: string;
state: any;
} {
switch (args.type) {
case "random:index/randomPassword:RandomPassword":
parametersCaptured.set(args.type, args.inputs);
return {
id: args.inputs.name + "_id",
state: {
result: "myseeminlyrandomtestpassword",
...args.inputs,
},
};
default:
parametersCaptured.set(args.type, args.inputs);
return {
id: args.inputs.name + "_id",
state: {
...args.inputs,
},
};
}
},
[...]
// inside a pulumi.all...
expect(
parametersCaptured.get(
"aws:secretsmanager/secretVersion:SecretVersion"
)
).toStrictEqual({
secretId: `${expectedGroupId}_id`,
secretString: "myseeminlyrandomtestpassword",
});
I get the error:
Object {
"secretId": "unit-test-prefix-my-test-cluster_id",
- "secretString": "myseeminlyrandomtestpassword",
+ "secretString": Object {
+ "4dabf18193072939515e22adb298388d": "1b47061264138c4ac30d75fd1eb44270",
+ "value": "myseeminlyrandomtestpassword",
+ },
}
Why is secretString an object? And what is "4dabf18193072939515e22adb298388d": "1b47061264138c4ac30d75fd1eb44270"? I would expect secretString to just be equal to myseeminlyrandomtestpassword. This way of testing works for other resources.adamant-butcher-52782
03/21/2023, 10:34 AMpulumi up
the console is stuck on running... with no output in the preview. I don't get where the issue might be. Any idea on how to debug this?straight-fireman-55591
03/21/2023, 11:13 AMgcp:serviceAccount:Account (pulumi-api-gw-service-account):
error: 1 error occurred:
* updating urn:pulumi:dev::Vega::gcp:serviceAccount/account:Account::pulumi-api-gw-service-account: 1 error occurred:
* googleapi: Error 400: Invalid field mask for ServiceAccount. Field mask paths cannot be empty., badRequest
careful-summer-45848
03/21/2023, 12:52 PMbillowy-intern-30563
03/21/2023, 1:11 PMpnpm
? We use pnpm
for its workspace features and disk space saving however when doing a pnpm install
pulumi doesn't see the SDK as being installedlimited-breakfast-24416
03/21/2023, 2:10 PMatRestEncryptionEnabled: false
aws.elasticache.ReplicationGroup with 2 nodes; one is primary and other is replica. Once the cluster is created; and I have to enable the At Rest encryption ( I know it will create new redis cluster), but will it take a snapshot of older redis cluster or create new fresh redis instance?billowy-intern-30563
03/21/2023, 3:14 PMError completing OAuth process.
boundless-carpenter-90061
03/21/2023, 3:24 PMaverage-candle-68231
03/21/2023, 11:56 PMDiagnostics:
docker:index:Image (api-image):
error: expected '::' in provider reference ''
building a stack from scratch seems to work wellplain-pizza-16453
03/22/2023, 9:13 AMfaint-balloon-33174
03/22/2023, 2:33 PM@ Updating................
pulumi:pulumi:Stack infra-protected-staging running Error: ' docker build -f ../../mix.Dockerfile --quiet ../.. -t b301d44d-container' failed with exit code 1
pulumi:pulumi:Stack infra-protected-staging running : Error: ' docker build -f ../../mix.Dockerfile --quiet ../.. -t b301d44d-container' failed with exit code 1
pulumi:pulumi:Stack infra-protected-staging running at /snapshot/awsx/node_modules/@pulumi/docker/docker.js:406:19
pulumi:pulumi:Stack infra-protected-staging running at Generator.next (<anonymous>)
pulumi:pulumi:
Maybe I should try v4?stocky-restaurant-98004
03/22/2023, 2:35 PMwooden-greece-50586
03/22/2023, 5:29 PMwooden-greece-50586
03/22/2023, 5:29 PMlittle-whale-73288
03/22/2023, 6:27 PMdefault_5_16_2
, default_5_29_1
and default
) of the default AWS provider and I'd like to switch to an explicitly defined provider. IIUC, I need to alias the new explicit provider to the default one, but I can't add three aliases for three default providers on a single explicit provider, can I?full-electrician-53450
03/22/2023, 11:46 PMpulumi:pulumi:Stack acme-infrastructure-gcp-beta
- └─ kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> <http://appprojects.argoproj.io|appprojects.argoproj.io> deleting (74s)...
error: '<http://appprojects.argoproj.io|appprojects.argoproj.io>' timed out waiting to be Ready
. This is preventing us from removing an environment in a clean way. Are there any known workarounds to this issue? I have tried using the retainOnDelete: true
value, this does not work.gorgeous-minister-41131
03/23/2023, 3:49 AMpulumi about
no matter what you run even if you just want to pulumi update -C somedir/
in the pwd. For example...
ArgoCD strips the root /tmp/_argocd-repo of all read permissions [not sure why, but it's just the behavior it seems to exhibit https://github.com/argoproj/argo-cd/blob/master/reposerver/repository/repository.go#L175].
I can see if I can work around it, but I'm curious why the actions of pulumi about
seem to implicitly run now when doing a pulumi update
in a project in the current working directory...
TBH this isn't a problem unique to just argo, since it is certainly appropriate for someone to restrict access at the root of a directory, but allow permission in a subdirectory of that directory. Pulumi has no business trying to traverse from the top of the basedir root IMO.
Anyways it is reported as an error, but when the pulumi update
is run it seems to fail with exit codes...
argocd@argo-cd-argocd-repo-server-55d7cdfb97-xtkp7:/tmp/_argocd-repo/52c01366-05dc-4758-9681-a63572526b17/infra$ pulumi about
CLI
Version 3.59.0
Go Version go1.20.2
Go Compiler gc
Host
OS ubuntu
Version 22.04
Arch x86_64
Pulumi locates its logs in /tmp by default
warning: Failed to read project: failed to locate Pulumi.yaml project file: open /tmp/_argocd-repo: permission denied
gorgeous-lunch-7514
03/23/2023, 11:05 AMgorgeous-lunch-7514
03/23/2023, 11:08 AMgorgeous-lunch-7514
03/23/2023, 11:13 AMthousands-electrician-8726
03/23/2023, 2:58 PMmillions-train-91139
03/23/2023, 3:36 PMnice-pilot-2521
03/23/2023, 4:20 PMpreview
/ up
/ stack
/ refresh
) the CLI always hangs for an extended period before printing the following:
error: reading response from API: stream error: stream ID 5; INTERNAL_ERROR; received from peer
nice-pilot-2521
03/23/2023, 4:20 PMnice-pilot-2521
03/23/2023, 4:22 PMaloof-gigabyte-74853
03/23/2023, 7:20 PMgray-wire-42438
03/23/2023, 10:02 PM