Add manifest.yaml to all app templates#194
Open
calvarjorge wants to merge 1 commit intodatabricks:mainfrom
Open
Add manifest.yaml to all app templates#194calvarjorge wants to merge 1 commit intodatabricks:mainfrom
calvarjorge wants to merge 1 commit intodatabricks:mainfrom
Conversation
Each top-level template now declares its display name, description, required resources, and user API scopes in-tree via manifest.yaml, following the AppTemplateManifest proto schema consumed by the Databricks Apps install flow. Co-authored-by: Jorge Calvar
theof-db
approved these changes
Apr 20, 2026
Contributor
theof-db
left a comment
There was a problem hiding this comment.
This looks good, please test e2e before landing
Are you planning to deprecate apps/deploy/app-template-app-manifests.jsonnet as well?
This file contains hidden or 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
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.
Summary
Adds a
manifest.yamlfile to every top-level template so each template declares its display name, description, required Databricks resources, and user API scopes in-tree.Why
We want to add them to support the new Deploy to Databricks flow.