lemon-monkey-228
05/02/2021, 8:25 AMboundless-angle-56560
05/02/2021, 8:42 AMworried-knife-31967
05/02/2021, 9:11 AMlemon-monkey-228
05/02/2021, 6:22 PMpulumi up
)?lemon-monkey-228
05/02/2021, 6:22 PMGOOGLE_CREDENTIALS
, that’s what it wants to use for the lotlemon-monkey-228
05/02/2021, 6:22 PMfresh-hospital-81544
05/03/2021, 12:15 AMconst repo = new awsx.ecr.Repository("registry");
const image = repo.buildAndPushImage('/path/to/image');
I notice each time I run pulumi up the image is getting built and pushed (hits the cache so the time delay isn't too bad but still unnecessary to run these steps every time). Is there a way to skip this altogether if the image directory has not changed?
thanksbetter-shampoo-48884
05/03/2021, 7:32 AMparent
?elegant-pager-5412
05/03/2021, 8:35 AMelegant-pager-5412
05/03/2021, 8:35 AMdev
and prod
stacks
`likefresh-hospital-81544
05/03/2021, 8:52 AMconst retry_queue = new aws.sqs.Queue("retry", {
delaySeconds: 180,
messageRetentionSeconds: 345600, // 4 days
and then later
});
const queueURL = retry_queue.name.apply(name => aws.sqs.getQueue({
name: name,
}).then(queue => queue.url));
however when I up this I get the error that the queue with the name is not available.
error: Running program '/working/src/stack-staging' failed with an unhandled exception:
Error: invocation of aws:sqs/getQueue:getQueue returned an error: invoking aws:sqs/getQueue:getQueue: 1 error occurred:
* Error getting queue URL: AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist for this wsdl version.
If I hard code the queueURL and pulumi up
and then restore the second snippet then the script works.
Is there a way to ensure a dependency here?handsome-state-59775
05/03/2021, 11:04 AMboundless-angle-56560
05/03/2021, 12:33 PMboundless-angle-56560
05/03/2021, 3:05 PMflat-monkey-80334
05/03/2021, 4:55 PMgorgeous-translator-67757
05/03/2021, 5:15 PMenough-truck-34175
05/03/2021, 6:54 PMpurple-train-14007
05/03/2021, 7:45 PMpurple-train-14007
05/03/2021, 7:46 PMboundless-angle-56560
05/03/2021, 7:47 PMpurple-train-14007
05/03/2021, 7:47 PMpurple-train-14007
05/03/2021, 7:50 PMpurple-train-14007
05/03/2021, 7:50 PMfast-dinner-32080
05/03/2021, 7:52 PMenough-truck-34175
05/03/2021, 8:23 PMpulumi preview --stack dev --custom-args="{my-custom-arg=true}"
. Is the only way I can achieve this through environment variables?purple-train-14007
05/03/2021, 8:48 PMpurple-train-14007
05/03/2021, 8:48 PMazure-native:network:ExpressRoutePort (USDomainServicesCircuit):
error: Code="InvalidResourceType" Message="The resource type could not be found in the namespace 'Microsoft.Network' for api version '2020-08-01'."
worried-knife-31967
05/03/2021, 9:10 PMbumpy-summer-9075
05/03/2021, 9:44 PMpulumi up
from my CI, it replaced my Kubernetes provider and some resources failed to deploy (they already existed). Now my stack is broken and I don't know how to fix it. This is what I get after I ran pulumi up
locally:
error: .pulumi/stacks/foo.dev.json: snapshot integrity failure; refusing to use it: resource urn:pulumi:foo.dev::myproject-foo::mycompany:myproject:K8sService$<kubernetes:traefik.containo.us/v1alpha1:Middleware::strip-prefix-middleware> refers to unknown provider urn:pulumi:foo.dev::myproject-foo::pulumi:providers:kubernetes::eks::dd3c15b3-68ea-4fdb-8361-93d85200c008
even pulumi stack export --file state.json --stack foo.dev
throws the aforementioned error
-----
I ended up deleting my stack directly in my s3 backend and recreating.