Skip to content
Snippets Groups Projects
  • Cam Saul's avatar
    5625fcb1
    Initialize Metabase with config from a file (#25986) · 5625fcb1
    Cam Saul authored
    
    * Initialize Metabase from a file
    
    * Code cleanup
    
    * Support optional template tags; more dox
    
    * Finish documentation for ns str
    
    * Force the first User to be an admin
    
    * Tests for DB creation
    
    * Add test to ensure that you can set User password with an {{env ...}} template
    
    * Remove data app permission code (#26016)
    
    * Revert "Use "apps" collection namespace for app collections (#25963)"
    
    This reverts commit a1894202.
    
    * Revert "Implement EE/Pro app permissions (#25764)"
    
    This reverts commit cf9b1bf5.
    
    * Revert "Implement global app permissions for the "All Users" group (#25679)"
    
    This reverts commit 63e950f2.
    
    * Revert "Require data permissions for executing actions (#25784)"
    
    This reverts commit 732bf6b1.
    
    * Revert "Prevent modifying app permissions via the collection endpoint (#25684)"
    
    This reverts commit 5d3f8279.
    
    * Revert "Implement DB specific execution permissions (#25629)"
    
    This reverts commit 141a13ce.
    
    * Revert "Introduce /execution/ permission (#25529)"
    
    This reverts commit 57cbb921.
    
    * Keep the app permission revision table
    
    * [Apps] Remove emitters (#25999)
    
    * [Apps] Remove emitters
    
    Emitters were created when we thought that we would be adding actions to
    multiple places in metabase. Instead we've coalesced to actions being a
    core feature of data-apps and are executed from within them. Attaching
    actions to models, as a form of re-use rather than a form of execution,
    means that actions can still be executed directly from a model, if we
    want to allow that in the future.
    
    * Fix lint errors
    
    * Move perform-action! tests out of the api.
    
    Since we want to keep the implicit bulk functionality but remove those
    endpoints move the tests to the actions namespace.
    
    * Fix linter
    
    * Change driver test to use function instead of endpoint
    
    Co-authored-by: default avatarmetamben <103100869+metamben@users.noreply.github.com>
    Co-authored-by: default avatarCase Nelson <case@metabase.com>
    Initialize Metabase with config from a file (#25986)
    Cam Saul authored
    
    * Initialize Metabase from a file
    
    * Code cleanup
    
    * Support optional template tags; more dox
    
    * Finish documentation for ns str
    
    * Force the first User to be an admin
    
    * Tests for DB creation
    
    * Add test to ensure that you can set User password with an {{env ...}} template
    
    * Remove data app permission code (#26016)
    
    * Revert "Use "apps" collection namespace for app collections (#25963)"
    
    This reverts commit a1894202.
    
    * Revert "Implement EE/Pro app permissions (#25764)"
    
    This reverts commit cf9b1bf5.
    
    * Revert "Implement global app permissions for the "All Users" group (#25679)"
    
    This reverts commit 63e950f2.
    
    * Revert "Require data permissions for executing actions (#25784)"
    
    This reverts commit 732bf6b1.
    
    * Revert "Prevent modifying app permissions via the collection endpoint (#25684)"
    
    This reverts commit 5d3f8279.
    
    * Revert "Implement DB specific execution permissions (#25629)"
    
    This reverts commit 141a13ce.
    
    * Revert "Introduce /execution/ permission (#25529)"
    
    This reverts commit 57cbb921.
    
    * Keep the app permission revision table
    
    * [Apps] Remove emitters (#25999)
    
    * [Apps] Remove emitters
    
    Emitters were created when we thought that we would be adding actions to
    multiple places in metabase. Instead we've coalesced to actions being a
    core feature of data-apps and are executed from within them. Attaching
    actions to models, as a form of re-use rather than a form of execution,
    means that actions can still be executed directly from a model, if we
    want to allow that in the future.
    
    * Fix lint errors
    
    * Move perform-action! tests out of the api.
    
    Since we want to keep the implicit bulk functionality but remove those
    endpoints move the tests to the actions namespace.
    
    * Fix linter
    
    * Change driver test to use function instead of endpoint
    
    Co-authored-by: default avatarmetamben <103100869+metamben@users.noreply.github.com>
    Co-authored-by: default avatarCase Nelson <case@metabase.com>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.