Passing in Docs Cache endpoint as environment variable #763
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@bsinghvi is attempting to deploy a commit to the fern Team on Vercel. To accomplish this, @bsinghvi needs to request access to the Team. Afterwards, an owner of the Team is required to accept their membership request. If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account. |
bsinghvi
force-pushed
the
bsinghvi/cache-updates
branch
from
ce66f9b to
e6d5432
Compare
bsinghvi
force-pushed
the
bsinghvi/cache-updates
branch
from
e6d5432 to
2d9dab7
Compare
dsinghvi
approved these changes
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Short description of the changes made
What was the motivation & context behind this PR?
This will let us move forward with testing the cache integration further. Simplifying the creation till we can better organize stacks.
Why not make changes all at once? Incrementally making changes so that problems surface earlier in the development, which theoretically should let us move faster.
How has this PR been tested?
Basically, the
cdk diffwill be used to validate the CDK template before we deploy.