best-apartment-2309
07/13/2022, 11:00 AMechoing-postman-88590
07/13/2022, 11:49 AMurllib
), but I would like pulumi to understand to make the API call only once on the first pulumi up
.
In other words is there a pulumi resource that make REST API call?
Thanksquick-painter-61380
07/13/2022, 12:04 PMhigh-grass-3103
07/13/2022, 4:46 PMSelfSignedCert.subjects
has changed to subject (singular) and from array to a scalar, but I don't recall changing version in the package.json...lemon-church-28946
07/13/2022, 7:28 PMacoustic-truck-53557
07/13/2022, 9:45 PMpulumi up
it says my connection resource was created but I see no update on the Auth0 web ui. When I run pulumi up
(multiple times) it always ways the plan is to create the "options" on my connection. Even though nothing has changed since the last pulumi up
. I'm provisioning Connection like this:
auth0.Connection(
f"{name}-connection",
options=auth0.ConnectionOptionsArgs(
brute_force_protection=True,
custom_scripts={"login": login_script},
debug=True,
disable_cache=True,
disable_signup=True,
import_mode=False,
name="Database Connection Opts",
tenant_domain=auth0.get_tenant().domain,
),
strategy="custom",
enabled_clients=client_ids,
display_name="Database Connection",
opts=opts,
)
Does anyone have any clue what I might be doing wrong?incalculable-garden-60162
07/14/2022, 1:37 AMquiet-hairdresser-18834
07/14/2022, 3:44 AMstocky-petabyte-29883
07/14/2022, 9:56 AMstocky-petabyte-29883
07/14/2022, 10:01 AMincalculable-garden-60162
07/14/2022, 10:01 AMhelpful-account-44059
07/14/2022, 10:32 AMCheck that your input satisfies the regular expression [0-9A-Za-z]*
2. I change the Sid to AllowPublishAlarms
error creating IAM Policy sns-access-policy: MalformedPolicyDocument: Policy document should not specify a principal
const snsAccessPolicy = new aws.iam.Policy("sns-access-policy", {
name: "sns-access-policy",
policy: {
Version: "2012-10-17",
Statement: [
{
Sid: "Allow_Publish_Alarms",
Effect: "Allow",
Principal: {
Service: "<http://aps.amazonaws.com|aps.amazonaws.com>",
},
Action: ["sns:Publish", "sns:GetTopicAttributes"],
Resource: "arn:aws:sns:ap-southeast-1:482414749843:amp-sns-topic",
Condition: {
StringEquals: {
"AWS:SourceAccount": "482414749843",
},
ArnEquals: {
"aws:SourceArn":
"arn:aws:aps:ap-southeast-1:482414749843:workspace/ws-be6e741f-d8ac-4330-b0fb-6a0c0aa92d6f",
},
},
},
],
},
});
helpful-account-44059
07/14/2022, 10:36 AMadamant-finland-54358
07/14/2022, 12:35 PM.yaml
files) for stack configuration settings. Ideally, I would like to use something like AWS SSM or similar to manage all stack config variables.
Does anyone know if this is possible or must I use YAML files for stack config?agreeable-window-77899
07/14/2022, 12:36 PMripe-ram-38792
07/14/2022, 3:10 PMmysterious-battery-54431
07/14/2022, 4:15 PM1
by default, and so I've tried to do this with Pulumi, as there is a CKU resource name...but nothing seems to change, ie. the cluster is still Basic type, and there's no CKU property with the cluster at all.
Has anyone been able to deploy Dedicated Confluent clusters with Pulumi...or even a Standard cluster type, and if so what am I overlooking here?swift-intern-18856
07/14/2022, 5:41 PMreadonly metadata: pulumi.Output<outputs.meta.v1.ObjectMeta>;
on the resource instance. However, on my generated resources, it’s instead pulumi.Output<k8s.types.input.meta.v1.ObjectMeta>
which leads to weird type juggling. everything works, but i’m not able to do something like resource.meta.name
as an input to another resource. For reference, the CRDs i’m working with are the <http://snapshot.storage.k8s.io/v1|snapshot.storage.k8s.io/v1>
which are annoying not part of the standard k8s api although they are standardized (not pulumi’s fault).future-refrigerator-88869
07/15/2022, 8:33 AMaws.autoscaling.Schedule
but it asks for a group and I'm not sure how to reference the spot fleet request.
In the aws console, it looks quite simple. Anyone can point me in the right direction ?victorious-machine-51951
07/15/2022, 8:34 AMpulumi up
on an pulumi-aws project. I created the pulumi project a few months back, it was working well that time and I created a few resources. I am re-visiting the project again, and it throws me this error. What could have went wrong? I only updated the pulumi version.victorious-continent-984
07/15/2022, 9:41 AMerror: Program failed with an unhandled exception:
, instead I want a short and clear message.busy-island-31180
07/15/2022, 6:11 PMlemon-church-28946
07/15/2022, 7:42 PMaws.cloudfront.Distribution
.
◦ Seems the only way to bounce between regions is to set the aws:region
configuration.
▪︎ Please correct me if I'm wrong about setting that value.
• Questions:
◦ Should the aws:region
config be changed between calls to aws.cloudfront.Distribution
, can I expect the subsequent distribution to be deployed in the most resent setting?
◦ If using the stack config to exchange parameters between the local program and the Pulumi program, what is the most effective method of getting a pulumi.automation.Stack
instance in the Pulumi program?
▪︎ I've considered __file__
, pulumi.get_stack()
, and pulumi.automation.select_stack()
but it seems like I'm missing a more obvious method.
▪︎ Edits:
• I'm looking to set new values to the stack's config.
• Can confirm that the pulumi.automation.select_stack()
works.stocky-petabyte-29883
07/15/2022, 11:06 PMimportant-night-82492
07/17/2022, 10:54 AMapiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
name: XXXX-web-ingress-rule-development
annotations:
<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
<http://nginx.ingress.kubernetes.io/rewrite-target|nginx.ingress.kubernetes.io/rewrite-target>: /$1
<http://nginx.ingress.kubernetes.io/use-regex|nginx.ingress.kubernetes.io/use-regex>: "true"
<http://nginx.ingress.kubernetes.io/proxy-body-size|nginx.ingress.kubernetes.io/proxy-body-size>: "0"
<http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: "600"
<http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: "600"
<http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-production
<http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: 'true'
<http://nginx.ingress.kubernetes.io/custom-http-errors|nginx.ingress.kubernetes.io/custom-http-errors>: "404"
<http://nginx.ingress.kubernetes.io/from-to-www-redirect|nginx.ingress.kubernetes.io/from-to-www-redirect>: "true"
<http://nginx.ingress.kubernetes.io/preserve-trailing-slash|nginx.ingress.kubernetes.io/preserve-trailing-slash>: "true"
<http://nginx.ingress.kubernetes.io/default-backend|nginx.ingress.kubernetes.io/default-backend>: ءءءء-web-service-development
<http://nginx.ingress.kubernetes.io/use-regex|nginx.ingress.kubernetes.io/use-regex>: "true"
<http://nginx.ingress.kubernetes.io/custom-http-errors|nginx.ingress.kubernetes.io/custom-http-errors>: "404"
spec:
tls:
- hosts:
- <http://oci.ءءءء.com|oci.xn--ggbaaa.com>
secretName: tls-secret-ءءءء-prodd
rules:
- host: <http://oci.ءءءء.com|oci.xn--ggbaaa.com>
http:
paths:
- path: /(.*)
pathType: Prefix
backend:
service:
name: ءءءء-web-service-development
port:
number: 3000
victorious-dusk-75271
07/17/2022, 12:23 PMvictorious-dusk-75271
07/18/2022, 1:52 AMvictorious-dusk-75271
07/18/2022, 1:53 AMripe-greece-78043
07/18/2022, 8:58 AMlet services = pulumi.k8s.services.get()
😪colossal-quill-8119
07/18/2022, 10:09 AMcolossal-quill-8119
07/18/2022, 10:09 AMvictorious-dusk-75271
07/18/2022, 10:46 AM