I think the issue is this damning snippet from the docs: Yarn netlify deploy -build -debug -context branch:$CI_COMMIT_REF_SLUG -alias $CI_ENVIRONMENT_SLUG -skip-functions-cache -site=$NETLIFY_SITE_ID -auth=$NETLIFY_AUTH_TOKEN -message "Deployed $CI_COMMIT_REF_SLUG" Here’s the two commands we’re running in our pipeline: yarn netlify env:set CONTENTFUL_ENVIRONMENT $CI_COMMIT_REF_SLUG -context branch:$CI_COMMIT_REF_SLUG The created branch deployment (specifically the Netlify functions) don’t seem to be using the branch variables we’re setting dynamically in step 3, and instead just use the non-context environment variables. Testers can access the new environment on a shareable URL and change/test content in our temp Contentful environment for testing purposesĮverything is working up until step 4.Netlify branch deployment created that uses our new environment variable.Netlify branch environment variable created with the newly created Contentful environment as its value.A Contentful environment is created (e.g.Developer creates a tag in Gitlab e.g.We don’t want a persistent test or staging environment, as they may be multiple users/teams working on new features at any given point so will need distinct Contentful environments. However… now we want to set up ephemeral environments for testing when big new features are being developed or big content changes are happening.
#Ephemeral environments update
Our Netlify site always knows which Contentful environment to use via a handy Contentful feature known as a branch alias, and a configured environment variable in Netlify, so we don’t have to update any environment variables in Netlify when we trigger a release. prod/1.0.0), which creates a new Contentful environment/branch for us, and builds and deploys the site to Netlify via netlify-cli. We have a great CI/CD Pipeline that will run when a new tag is pushed (e.g. We’ve just released a sweet new Next.js site on Netlify, using Contentful CMS to provide us content. Ephemeral environments are temporary deployments that contain a self-contained version of your application, generally for every feature branch.
0 kommentar(er)
