swift-crayon-9802
09/20/2023, 8:29 AMquick-balloon-26793
09/20/2023, 10:20 AMgreat-lifeguard-53991
09/20/2023, 1:10 PMmysterious-raincoat-41852
09/20/2023, 1:37 PMnumerous-businessperson-94924
09/20/2023, 1:54 PM<hashivault://mykey>
but I need more details to configure the Vault server correctly.
Anyone has already used that feature or can help me find the right documentation ?
Or maybe I miss understand and it is only usable with HCP Vault (the saas version) ?
Thanks! Sonic.rough-quill-46540
09/20/2023, 2:52 PMpulumi import snowflake:index/storageIntegration:StorageIntegration my_integration MY_DB.MY_SCHEMA.MY_INTEGRATION
and some permutations of that (removing db, schema, etc…). I always get:
error: Preview failed: resource MY_DB.MY_SCHEMA.MY_INTEGRATION does not exist
Has anyone had any luck with this?faint-dusk-41267
09/20/2023, 3:03 PMmysterious-air-44109
09/20/2023, 6:06 PMbrash-horse-53174
09/20/2023, 6:36 PMrich-whale-93740
09/21/2023, 12:40 AMpulumi preview
?
We didn't get an error during preview
for a new Route 53 record. But it failed during up
* creating Route 53 Record: InvalidChangeBatch: [Invalid Resource Record: 'FATAL problem: InvalidCharacterString (Value should be enclosed in quotation marks) encountered with '""xxxxxxxx-domain-verification=xxxxxxxx""'']
status code: 400, request id: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
It's a valid error and the root cause is similar to this. Not sure if this is something Pulumi (or perhaps any IaC) able to capture earlier?anonymous
09/21/2023, 5:05 AMfaint-kitchen-6178
joined #general.ambitious-thailand-9777
09/21/2023, 7:41 AMcolossal-motorcycle-45184
09/21/2023, 11:06 AMdocker:index:Image (image):
error: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource
when I run pulumi up
.
PS: With the "owner" role, the service account is expected to have all the permissions. I also went in to confirm and it does have the "artifactregistry.repositories.uploadArtifacts"
permission. I must be missing something. Would love to get some assistance.
Thanks.billowy-engine-58246
09/21/2023, 11:24 AMstale-market-32073
09/21/2023, 12:00 PMfierce-bird-8909
09/21/2023, 1:51 PMswift-family-98749
09/21/2023, 2:32 PMpulumi_aws
, however I am having trouble getting Cloudwatch logs configured
Pulumi documentation refers to a structured_log_destinations option in the calling method. However, the pulumi_aws
python library appears not to support this option.
Can someone advise?busy-napkin-83700
09/21/2023, 3:20 PMnumerous-camera-74727
09/21/2023, 3:40 PMlate-journalist-61387
09/21/2023, 4:17 PMpulumi up
late-journalist-61387
09/21/2023, 4:17 PMstrong-match-67698
09/21/2023, 5:38 PMpulumi destroy
requires pulumi project file to be present in the directory? If I run
pulumi destroy -s organization/project_name/stack_nameit doesn't feel like it still needs to read anything from the file system right? Yet it does complain about missing .yaml file and incorrect project name if there is one from a different project. Any idea why is that?
bitter-painter-63067
09/21/2023, 5:44 PMbig-angle-30002
09/21/2023, 7:05 PMdef foo(a: str) -> str:
pass
but using somthing pulumining ? 👀
def foo(a: str) -> Output<T>:
pass
little-library-54601
09/21/2023, 7:34 PMvar otherStack = new StackReference("other-stack");
This works great for all my lower environments which share a stack passphrase. But my production stack has a different passphrase, for obvious reasons. When it executes that code, pulumi dumps an error because the current PULUMI_CONFIG_PASSPHRASE environment variable is valid for the prod stack but not for "other-stack".
FWIW, I'm using the default secrets provider - maybe that's technically "passphrase" since I see there's one called "default" in the docs but I don't know what that means or how it's different than "passphrase".
Is this possible? Would appreciate direction. Thanks.fast-sandwich-30809
09/21/2023, 7:48 PMlate-journalist-61387
09/21/2023, 8:41 PMconst isPreview = pulumi.runtime.isDryRun();
if (!isPreview) {
rdsDataServer.endpoint.apply(rdsDataServerEndpoint => {
rdsDataServer.port.apply(rdsDataServerPort => {
....
// here we have received the rds host, user, password, ...
// now, we run the query to check if the user exist before
if(!userExistsDatabase("username"))
{
let secret = new aws.secretsmanager.Secret("...", {
// The name of the secret
name: "...",
tags: {
...
}
});
// create user in database with postgers library
// make an object to store the value
const storeKeyValue = {
dbUrl: ...,
}
// Setting a value for our secret
let secretValue = new aws.secretsmanager.SecretVersion("...", {
secretId: secret.id,
secretString: JSON.stringify(storeKeyValue),
});
}
}
}
it works well for the first time, however when I run the second time, as the user is created before and the secret creation code will not reach, pulumi tries to destroy that.
so what is the solution?dry-keyboard-94795
09/21/2023, 9:39 PMdry-keyboard-94795
09/21/2023, 9:41 PMlate-journalist-61387
09/21/2023, 10:12 PM