Add a Next.js Site example

lukehoban commented 1 year ago

Adds an example of deploying a Next.js site with Pulumi, building on top of OpenNext.

Fixes https://github.com/pulumi/examples/issues/779.

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Update for moolumi/k8s-ci-cluster/08fc4f0485a0d81299d8a2f3daa978f8aae4d043-1477 was successful.

Resource Changes

    Name                                                          Type                                        Operation
+   k8s-ci-cluster-08fc4f0485a0d81299d8a2f3daa978f8aae4d043-1477  pulumi:pulumi:Stack                         create
+   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

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Destroy for moolumi/k8s-ci-cluster/08fc4f0485a0d81299d8a2f3daa978f8aae4d043-1477 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

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Update for moolumi/k8s-ci-cluster/43f0659e0d4447e8bfd48ffc05b34d0c14f96715-1478 was successful.

Resource Changes

    Name                                                          Type                                        Operation
+   gke                                                           pulumi:providers:kubernetes                 create
+   k8s-ci-cluster-43f0659e0d4447e8bfd48ffc05b34d0c14f96715-1478  pulumi:pulumi:Stack                         create
+   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

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Destroy for moolumi/k8s-ci-cluster/43f0659e0d4447e8bfd48ffc05b34d0c14f96715-1478 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

filipef101 commented 1 year ago

Amazing, just sharing my experimentations with this: Notes:

Not sure if needed the npm install & open next build step, IMO that should be handled by the user or CI before triggering the deployment, or it should be generic, ie "build command".
Doesn't use/deploy the warmer lambda Did play modifying this to deploy to lambda@edge Notes:
Doesn't use/deploy the revalidation lambda function
Doesn't setup cloudwatch (not sure if edge specific or not), terraform examples I've seen do mention something about cloudwatch.

What I've learned about making @edge lambdas, since I couldn't find anything on Pulumi docs, to deploy a lambda to edge the steps are:

lambda needs to be on us-east-1 region

ie: just deploy everything to us-east-1, or pass the provider only to the edge lambda (didn't try)
const useast1 = new aws.Provider('useast1', { region: 'us-east-1' });
const site = new NextJsSite(_prefixWithAppName('mysite'),
{ path: '../' },
{ provider: useast1 },
);

adding the lambdaFunctionAssociations on the/a cloudfront behaviour
- where the arn is .qualifiedArn
on the lambda enable "publish" flag
serverFunction role needs to include edgelambda role: ... Service: ['edgelambda.amazonaws.com', 'lambda.amazonaws.com'] ...
lambda arch needs to be x86_64
lambda cant take any env variables. (not sure if there's a use case for this) I only changed the server lambda to run on edge so not sure if image lambda can be deployed to edge as you are adding BUCKET_NAME & BUCKET_KEY_PREFIX env vars.

Looks kind of simple to support edge deployments, the terraform example I've seen does it based on a flag using different settings based on it.

I've looked at https://github.com/RJPearson94/terraform-aws-open-next for context lambda main

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Update for moolumi/k8s-ci-cluster/dbc40baa9960aec6f6421b4eb160c9a19548c533-1498 was successful.

Resource Changes

    Name                                                          Type                                        Operation
+   gke                                                           pulumi:providers:kubernetes                 create
+   k8s-ci-cluster-dbc40baa9960aec6f6421b4eb160c9a19548c533-1498  pulumi:pulumi:Stack                         create
+   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

pulumi-staging[bot] commented 1 year ago

:tropical_drink: The Destroy for moolumi/k8s-ci-cluster/dbc40baa9960aec6f6421b4eb160c9a19548c533-1498 was successful.

Resource Changes

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

cnunciato commented 1 year ago

Test failures are unrelated, so I'll go ahead and merge this. Thanks @lukehoban!

@filipef101 Excellent feedback, thanks for taking the time! I'll file a follow-up issue so these suggestions don't get lost.

pulumi / examples