elegant-twilight-2745
11/21/2019, 4:41 PMboundless-monkey-50243
11/21/2019, 4:43 PMpulumi stack ls
as the bucket owner, not every stack created by other accounts in that bucket show up. (Some do. Not all.) When I do aws s3 ls
, however, the JSON files do appear in the list. I can't read them as the bucket owner, however, and get a 403 on HeadObject/GetObject.
My initial expectation was an ACL problem, but I've since run aws s3 cp
across the entire bucket setting everything to bucket-owner-full-control and while that has in the past worked occasionally (for reasons I am not fully sure of), it's not working now.
1. How can I unjam myself?
2. My intuition is that this is a problem with the S3 client used by Pulumi. What steps can I take to prevent it from happening again?bright-apple-15972
11/21/2019, 7:33 PMswift-painter-31084
11/21/2019, 7:46 PMdelightful-dawn-43855
11/21/2019, 10:33 PMKind = "Elastic",
Sku = new PlanSkuArgs
{
Tier = "ElasticPremium",
Size = "EP1",
Capacity = 1
}
//properties for "maximumElasticWorkerCount": 2 doesn't exist yet
full-dress-10026
11/22/2019, 12:49 AMerror: Plan apply failed: deleting urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration: error deleting Autoscaling Launch Configuration (k8s-dev-ng-nodeLaunchConfiguration-b5215a6): ResourceInUse: Cannot delete launch configuration k8s-dev-ng-nodeLaunchConfiguration-b5215a6 because it is attached to AutoScalingGroup k8s-dev-ng-e37cdc2e-NodeGroup-6186KPAWLIPL
status code: 400, request id: 1a10ee34-0cc1-11ea-afde-8d216d809694
This occurred after a pulumi up
failed with this error:
error: Plan apply failed: 1 error occurred:
* updating urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:cloudformation/stack:Stack::k8s-dev-ng-nodes: UPDATE_ROLLBACK_COMPLETE: ["MinInstancesInService must be less than the autoscaling group's MaxSize"]
Is there a way to get myself unstuck from this? Every pulumi up
now fails with the former error.ambitious-ram-5811
11/22/2019, 12:53 AMpulumi refresh
or if that doesn't work, manually deleting the thing it Doesn't Like, then running pulumi refresh
full-dress-10026
11/22/2019, 1:10 AMeks.NodeGroup
already do that?full-dress-10026
11/22/2019, 1:17 AMfull-dress-10026
11/22/2019, 1:18 AMpulumi state delete urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration
warning: This command will edit your stack's state directly. Confirm? Yes
error: No such resource "urn:pulumi:dev::vm-scaler::eks:index:Cluster:index:NodeGroup:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration" exists in the current state
stocky-spoon-28903
11/22/2019, 9:49 AMpulumi stack export
do you see that launch configuration listed?salmon-beard-79336
11/22/2019, 3:27 PMelegant-flag-85647
11/22/2019, 4:20 PM= └─ azure:appservice:Plan dev import [diff: +location,reserved,sku~kind,name]; 1 warn
Diagnostics:
azure:appservice:Plan (dev):
warning: inputs to import do not match the existing resource; importing this resource will fail
Is there a way to diff the current and preview state of apps? The details section gives me some info but it doesn’t present a diff (I’m guessing it might be due to casing Linux vs linux causing pulumi to think that the details do not match.)
I have tried running with -v=3
but did not help that much.adamant-motorcycle-38425
11/23/2019, 10:57 AMpulumi destroy
if the deployed stack contains a bucket with existing objects. I can easily delete such buckets with the AWS CLI (e.g. aws s3 rb --force
<s3://my-bucket-with-objects>
). (I know this is an AWS restriction that we override with the --force
flag).
Question: Is there a way to tell pulumi to destroy bucket resources even if they have objects inside (and let it handle doing a forceful destroy of these buckets?). This is my ideal scenario instead of running special pre-destroy operations by hand.glamorous-printer-66548
11/23/2019, 7:08 PMstocky-camera-41469
11/23/2019, 11:14 PMambitious-helmet-24352
11/25/2019, 2:39 PMpulumi watch
red-football-97286
11/25/2019, 5:27 PMlog_setup
which setup's logging for AWS. They are all in there own named stack with the stack name of log_setup
, if that makes sense!
I want to be able to run them all at once. If possible.swift-painter-31084
11/25/2019, 6:24 PMmillions-judge-24978
11/25/2019, 6:41 PMpulumi up --target
option, however I am seeing that the preview is not limited to the targeted URN I provide. Is that expected? Will the targeting only affect the actual up
once I approve it.early-intern-90238
11/25/2019, 7:26 PMearly-intern-90238
11/25/2019, 7:32 PMcurved-doctor-83600
11/25/2019, 9:06 PMrhythmic-hair-33677
11/26/2019, 4:58 AMWaitForFirstConsumer
? When I make a PVC with Pulumi, pulumi hangs waiting for it to no longer be pending, which won’t happen unless the pulumi controller creates the pods that depend on that PVC.broad-finland-69602
11/26/2019, 1:17 PMpulumi up
had to be run twice in order to create the resources. First time it creates the table and the second time it creates it the item inside the table.
import json
import pulumi
from pulumi_aws import dynamodb
table_default_name = dynamodb.Table(
'pulumi-poc-test-table',
hash_key='id',
attributes=[
{'name': 'id', 'type': 'S'}
],
write_capacity=1,
read_capacity=1
)
debug_object_1 = \
table_default_name.name.apply(lambda table_name: \
dynamodb.TableItem(
'test_item',
hash_key='id',
item=json.dumps({'id': {'S': 'yes'}}),
table_name=table_name
)
)
colossal-plastic-46140
11/26/2019, 1:52 PMdelightful-dawn-43855
11/26/2019, 3:25 PMplain-businessperson-30883
11/26/2019, 4:40 PM1.6.0
. I have a stack reference and retrieve an output using getOutputSync()
but the output becomes undefined. The same code works with version 1.5.2
. Still in version 1.6.0
, if I execute the following snippet I can see the whole output as expected namespacesStack.outputs.apply(o => console.log(o));
. Anyone having the same issue?acceptable-dusk-81175
11/26/2019, 4:54 PMchilly-photographer-60932
11/26/2019, 6:30 PMpulumi stack select
gives an option <create a new stack>
, would like to create without being interactive.chilly-photographer-60932
11/26/2019, 6:30 PMpulumi stack select
gives an option <create a new stack>
, would like to create without being interactive.white-balloon-205
11/26/2019, 6:31 PMpulumi stack init
chilly-photographer-60932
11/26/2019, 6:36 PM