boundless-room-36997
06/10/2019, 10:30 AMlittle-summer-88406
06/10/2019, 12:00 PMboundless-room-36997
06/10/2019, 2:22 PMstocky-spoon-28903
06/10/2019, 2:35 PMstocky-spoon-28903
06/10/2019, 2:35 PMchilly-photographer-60932
06/10/2019, 3:19 PMimport * as awsx from '@pulumi/awsx';
export const vpc = new awsx.ec2.Vpc('custom', {
cidrBlock: '10.0.0.0/16',
numberOfAvailabilityZones: 3,
subnets: [
{ type: 'public' },
{ type: 'private' },
{ type: 'isolated', name: 'db' },
{ type: 'isolated', name: 'redis' }
]
});
export const sg = new awsx.ec2.SecurityGroup('sg', { vpc });
awsx.ec2.SecurityGroupRule.ingress(
'https',
sg,
new awsx.ec2.AnyIPv4Location(),
new awsx.ec2.TcpPorts(443),
'allow https access'
);
awsx.ec2.SecurityGroupRule.ingress(
'ssh',
sg,
new awsx.ec2.AnyIPv4Location(),
new awsx.ec2.TcpPorts(22),
'allow ssh access'
);
For this above code I am running into this error
aws:ec2:SecurityGroup (sg):
error: Plan apply failed: Error creating Security Group: InvalidParameterValue: Value (sg-34e72cd) for parameter GroupName is invalid. Group names may not be in the format sg-*.
status code: 400, request id: 5a65b4e8-298c-4b18-9e85-94c61d7e19b4
Looks like the sg
with an -
is an issue. Am I doing something wrong? Or is it a bug?boundless-monkey-50243
06/10/2019, 6:31 PMpulumi login <s3://my-pulumi-bucket/something>
(assuming that data will be stored in <s3://my-pulumi-bucket/something/.pulumi>
), instead everything ends up in <s3://my-pulumi-bucket/.pulumi>
. This is really unexpected. Is it intentional behavior?boundless-monkey-50243
06/10/2019, 7:45 PMpulumi.StackReference
to look at a stack in another S3 bucket, by stack name? i.e., I’m in bar-deploy
, I need to access foo-deploy
, but I need to specifically get outputs from the dev
stack (use case: there might be multiple bar-deploy
stacks using foo-deploy
@ dev
as their backend). How can I express this?proud-alarm-92546
06/10/2019, 11:08 PMawsx.elasticloadbalancingv2.ApplicationLoadBalancer..... ipAddressType: config.ipAddressType,
anyone want to help me type this properly? a config string isn't it... it seems to want:
ipAddressType?: pulumi.Input<"ipv4" | "dualstack">;
TSError: ⨯ Unable to compile TypeScript:
index.ts(65,87): error TS2345: Argument of type '{ name: string; vpc: Vpc; external: true; ipAddressType: string; securityGroups: SecurityGroup[]; subnets: Output<string>[]; }' is not assignable to parameter of type 'ApplicationLoadBalancerArgs'.
Types of property 'ipAddressType' are incompatible.
Type 'string' is not assignable to type '"dualstack" | "ipv4" | Promise<"dualstack" | "ipv4"> | OutputInstance<"dualstack" | "ipv4"> | undefined'.
index.ts(136,64): error TS7006: Parameter 'hostname' implicitly has an 'any' type.
broad-dog-22463
06/10/2019, 11:10 PMproud-alarm-92546
06/10/2019, 11:10 PMbroad-dog-22463
06/10/2019, 11:10 PMlittle-summer-88406
06/11/2019, 7:07 AMlively-coat-66786
06/11/2019, 2:25 PMaws:ec2:RouteTable (vpc-test-us-east-2-private-0):
error: Plan apply failed: Error creating route table: InvalidVpcID.NotFound: The vpc ID 'vpc-03f05ae1180c62fd2' does not exist
worried-engineer-33884
06/11/2019, 5:33 PMlimited-rainbow-51650
06/11/2019, 6:58 PMboundless-monkey-50243
06/11/2019, 7:12 PMcurl | sh
) to the most recent version of Pulumi; I now get a panic (listed in thread) whenever I try to run anything and on my side I've relogged in a new shell, run npm rebuild
, etc.
It seems so out of the ordinary that it seems likely to be an issue on my end of things, but perhaps somebody's seen it before (or has some "nuke it from orbit" advice)?elegant-crayon-4967
06/11/2019, 7:46 PMimport * as aws from "@pulumi/aws";
command, I get errors assigning values via a variable to my ec2 instanceType, but if I use the old format const aws = require("@pulumi/aws")
the error goes away and my code runs just fine. Thoughts?orange-tailor-85423
06/11/2019, 7:52 PMorange-tailor-85423
06/11/2019, 7:52 PMthankful-telephone-29600
06/11/2019, 9:54 PMexport const kubeconfig = cluster.kubeconfig;
const myk8s = new k8s.Provider("myk8s", {
kubeconfig: cluster.kubeconfig.apply(JSON.stringify),
});
const nginx = new helm.v2.Chart("rancher-nginx", {
namespace: "rancher",
repo: "stable",
chart: "nginx-ingress",
values: {
"rbac.create": "true"
},
}, { providers: { kubernetes: myk8s }});
busy-pizza-73563
06/12/2019, 8:55 AM1.13.4
to 1.14.3
and now when I do pulumi up
on an existing stack I get
error: Plan apply failed: 1 error occurred:
* SchemaError(io.k8s.api.core.v1.PodAntiAffinity): invalid object doesn't have additional properties
Ideas?busy-pizza-73563
06/12/2019, 8:56 AMPodAntiAffinity
references in my code)busy-pizza-73563
06/12/2019, 10:35 AM@pulumi/pulumi
, @pulumi/kubernetes
and the pulumi
CLI).worried-engineer-33884
06/12/2019, 2:29 PMdependsOn
relationship?
We believe we are encountering an issue creating a resource that depends on an IAM RolePolicyAttachment that isn't quite ready when the dependent resource starts to create.
https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistencyhundreds-coat-15657
06/12/2019, 2:32 PMelegant-crayon-4967
06/12/2019, 2:54 PMbig-piano-35669
proud-alarm-92546
06/12/2019, 5:01 PMgentle-diamond-70147
06/12/2019, 5:03 PM