Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix aws-ts-containers compilation #1489

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

t0yv0
Copy link
Member

@t0yv0 t0yv0 commented Aug 28, 2023

It appears that "name" property is required. This currently causes CI failure to compile typescript for this example.

https://github.com/pulumi/pulumi-awsx/blob/master/awsx/schema.json#L1208 is the reference.

pulumi/pulumi-awsx#1069 is the change that made this required.

CC @rquitales @mjeffryes

@t0yv0 t0yv0 requested a review from cnunciato August 28, 2023 20:49
@pulumi-staging
Copy link

🍹 The Update for moolumi/k8s-ci-cluster/3fc32749bdfe4a041bab3d0f7cb9ab18cd20c61a-1504 was successful.

Resource Changes

    Name                                                          Type                                        Operation
+   multicloud                                                    pulumi-kubernetes:ci:GkeCluster             create
+   password                                                      random:index/randomPassword:RandomPassword  create
+   ephemeral-ci-cluster                                          gcp:container/cluster:Cluster               create
+   primary-node-pool                                             gcp:container/nodePool:NodePool             create
+   gke                                                           pulumi:providers:kubernetes                 create
+   k8s-ci-cluster-3fc32749bdfe4a041bab3d0f7cb9ab18cd20c61a-1504  pulumi:pulumi:Stack                         create

@mjeffryes
Copy link
Member

We've broken examples a few times recently when updating providers; We should probably be building examples when making providers releases? Alternatively, should the examples versions be pinned somehow and updated after the release goes out?

@pulumi-staging
Copy link

🍹 The Destroy for moolumi/k8s-ci-cluster/3fc32749bdfe4a041bab3d0f7cb9ab18cd20c61a-1504 was successful.

Resource Changes

    Name                  Type                                        Operation
-   gke                   pulumi:providers:kubernetes                 delete
-   primary-node-pool     gcp:container/nodePool:NodePool             delete
-   ephemeral-ci-cluster  gcp:container/cluster:Cluster               delete
-   password              random:index/randomPassword:RandomPassword  delete

Copy link
Member

@mjeffryes mjeffryes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving b/c this looks correct & I don't think the check failures are related to this change, but I can't claim to fully understand the failures

@t0yv0
Copy link
Member Author

t0yv0 commented Aug 28, 2023

We should probably be building examples when making providers releases

Well it's a possibility; it's going to be a draw on compute time but can help maintain this repo for sure.

The check failures are present on master independently yes.

@t0yv0 t0yv0 merged commit 046330c into master Aug 28, 2023
47 of 50 checks passed
@t0yv0 t0yv0 deleted the t0yv0/fix-aws-ts-containers-compilation branch August 28, 2023 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants