build(ci): disable next export, use build time vars for static build #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE: This PR should be tested against a running cluster to ensure there are no breaking changes due to the change in
next.config.js
exposing theNEXT_PUBLIC_REKOR_DEFAULT_DOMAIN
env var at build time. Because these changes happen at build time, it should not have any effect, but is worth a double check. Unfortunately this needs to be done manually for now while e2e tests are still in development.To test:
NEXT_PUBLIC_REKOR_DEFAULT_DOMAIN
should be set to the Rekor server automatically (whether you deploy by the Helm chart or the operator)