(fix): Accept newer versions of CF_API_TOKEN/ACCOUNT_ID in deploy.yml #110
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.
Deploy.yml currently only accepted the deprecated versions of the api token and account id secrets.
This PR fixes that.
Summary by CodeRabbit
deploy.yml
. The environment variablesaccountId
andapiToken
are now more flexible, allowing for the use of either the original secrets or new secrets (CLOUDFLARE_ACCOUNT_ID
andCLOUDFLARE_API_TOKEN
). This change enhances the flexibility of our deployment process by accommodating different sets of secrets depending on their availability.