Aurélien Requiem

@mikhailshilkov I'm reopening this issue for tracking purpose of affected customers, despite the issue being with the Azure API. As a repro, the code is provided below. Here are the...

Seems related to https://github.com/spf13/cobra/pull/2095 Thanks @krobelus

@Jasi1997 It feels like you opened this issue in the wrong repository. This repository has to do with the simple login app itself, and the list you pointed out is...

@lukehoban While testing your hypothesis (with and without preview), I've observed an inconsistent behavior during the preview phase. Randomly and on both `tags` and `enabledClusterLogTypes`, the preview succeeded and failed...

This feature request is also impacting this customer https://pulumi.zendesk.com/agent/tickets/2083 ([customer thread](https://pulumi.slack.com/archives/C02970CDD27/p1669077508118909), [internal thread](https://pulumi.slack.com/archives/C0435R1H5FC/p1669082293512409))

@justinvp @roothorp Yes, I think addressing this inside `pulumi-eks` is probably the better way. For such sensitive information like `kubeconfig`, `clusterCertificateAuthority.data` and `certificateAuthorities[].data`, our users shouldn't have to second guess...

This issue *should* be now solved. * compile the webhook against cert-manager 1.13.0 * run the webhook with cert-manager 1.13.0 I haven't seen a single error across my cluster for...

@irreleph4nt I'm not part of the cert-manager/jetstack team but what you describe sounds like separate issues (though connected perhaps). Have you considered raising separate issues and linking them to this...

Likewise @SgtCoDFish we all also very much appreciate all the work you and the entire team are doing.

This issue is easy to reproduce with the code below ```python ecs_instance_role = aws_native.iam.Role( f'instance-role', assume_role_policy_document=json.dumps({ "Version": "2012-10-17", "Statement": [{ "Action": "sts:AssumeRole", "Effect": "Allow", "Sid": "", "Principal": { "Service": "ec2.amazonaws.com",...