fix: only upload functions declared in config.toml #4847
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
If a function dir with index.ts is present on disk but not defined in config.toml, it is still deployed. I assume this isn't expected behavior.
To Reproduce:
supabase functions new should-not-uploadsupabase functions deploy --use-apideploy success msg is shown for all function slugs, even the ones which aren't deployed. Also the slugs slice contains duplicates, so does the msg derived from slugs slice
should-not-uploadis disabledfunctions.should-not-upload.enabled=falsebut the deploy success msg still prints this slug and msg contains duplicates.What is the new behavior?
<function>.enabledbehavior remains same.GetFunctionSlugsand only print deploy success msg for functions actually deployed.