tall-crowd-93084
11/06/2022, 1:52 PMconfig set
on a key that a provider expects and one that you've made up yourself?
I've have run pulumi config set sendinblue:smtp <XXX> --secret
and it's not showing up in the config section of my stack whereas hcloud:token
which was set in the same way is...
I get this in my console when trying to do cfg.requireSecret("sendinblue:smtp")
Diagnostics:
pulumi:pulumi:Stack (infra-dev):
error: Missing required configuration variable 'infra:sendinblue:smtp'
please set a value using the command `pulumi config set infra:sendinblue:smtp <value>`
hallowed-horse-57635
11/06/2022, 6:12 PMblue-jelly-98553
11/06/2022, 9:49 PMpulumi.FileAsset
? Wanted to define an AWS policy in a policy.json
and then reference that file the code below, but pulumi preview is throwing this error when trying that method error: expected string or JSON map; got *resource.Asset
# Create a policy that allows the Lambda role to write to CloudWatch Logs
cloudwatch_policy = aws.iam.RolePolicy(
resource_name='pulumi-lambda-test-policy',
role=lambda_role.id,
policy=pulumi.FileAsset('./policies/cloudwatch_policy.json')
)
prehistoric-morning-13772
11/07/2022, 1:32 AMpulumi login
command using a DigitalOcean spaces s3 bucket?cold-toothbrush-60276
11/07/2022, 11:19 AMflat-secretary-85301
11/07/2022, 2:48 PMjolly-controller-97081
11/07/2022, 3:26 PMearly-plastic-49211
11/07/2022, 4:39 PMcurved-application-45650
11/07/2022, 8:14 PMwhite-chef-55657
11/08/2022, 1:08 PMerror: could not load plugin for eks provider 'urn:pulumi:xxx::aws-eks::pulumi:providers:eks::default': Could not automatically download and install resource plugin 'pulumi-resource-eks', install the plugin using `pulumi plugin install resource eks`.
Underlying error: 401 HTTP error fetching plugin from <https://api.github.com/repos/pulumi/pulumi-eks/releases/latest>
most-mouse-38002
11/08/2022, 1:40 PMhallowed-horse-57635
11/08/2022, 2:23 PMbrave-angle-33257
11/08/2022, 5:18 PMCommandError: code: 255
stdout: Created stack '822de893-90b5-4671-9bde-10477ba88e6e'
stderr: warning: A new version of Pulumi is available. To upgrade from version '3.39.3' to '3.46.0', run
square-ability-48831
11/08/2022, 5:20 PMpulumi stack rename <newname>
and getting
[403] You do not have permission to perform this operation.
He is a Stack Admin and also created the stack in the first place. Is this expected? I do not see any other permissions available to give him.brash-monkey-31522
11/08/2022, 7:03 PM{"code":403,"message":"You do not have permission to perform this operation."}
The endpoint works when using a personal access token.
Any ideas? 🙂
Also, the docs mention that the API is rate-limited, anyone know what that limit is?prehistoric-london-9917
11/08/2022, 7:10 PMmicroscopic-afternoon-22702
11/08/2022, 8:07 PMbrash-gigabyte-81569
11/08/2022, 8:57 PMhallowed-horse-57635
11/08/2022, 11:09 PMstrong-helmet-83704
11/09/2022, 12:50 AMrough-jordan-15935
11/09/2022, 4:52 AMorange-airport-64592
11/09/2022, 8:14 AMpulumi.StackReference
My backend used aws s3salmon-mechanic-4571
11/09/2022, 8:56 AMcold-toothbrush-60276
11/09/2022, 4:18 PMdamp-honey-93158
11/09/2022, 4:21 PMlively-needle-84406
11/09/2022, 8:06 PMquiet-tomato-48326
11/10/2022, 12:08 AMerror: PULUMI_ACCESS_TOKEN must be set for login during non-interactive CLI sessions
We’re using an S3 bucket for state, so it shouldn’t need the access token. According to the docs, pulumi “automatically perform a pulumi login
command” when running in a CI service—I think this is what’s failing. However, we’re not using pulumi cloud—we’re using an S3 backend, listed in Pulumi.yaml:
backend:
url: '<s3://pulumi-state.swmdigital.io>'
I’ve tried adding a pulumi login
command to the workflow, but that fails with the same error
pulumi login --cloud-url <s3://pulumi-state.swmdigital.io>
Can anyone see what I’m doing wrong?damp-honey-93158
11/10/2022, 8:08 AMprehistoric-waitress-34998
11/10/2022, 12:56 PMfailure Setting LB Security Groups: ValidationError: A security group must be specified
If it run the task again without any changes it completes fine. I’m getting the security group ids from another stack, and passing them into the resource like this:
// Create load balancer to listen for HTTP traffic
const alb = new awsx.lb.ApplicationLoadBalancer(
`${name}-alb`,
{
securityGroups: args.apiSecurityGroupIds,
subnets: args.subnetIds,
vpc,
},
{
parent: this,
}
)
Does anyone know why this might be happening? I’ve logged out the inputs and the ids are definitely there each time it runs…salmon-hairdresser-65532
11/10/2022, 1:22 PMsalmon-hairdresser-65532
11/10/2022, 1:22 PMbillowy-army-68599
11/10/2022, 4:49 PMsalmon-hairdresser-65532
11/10/2022, 4:52 PM