dimas-b commented on code in PR #4082: URL: https://github.com/apache/polaris/pull/4082#discussion_r3010889327
########## site/content/blog/2026/03/29/polaris-cli-setup-command.md: ########## @@ -0,0 +1,108 @@ +--- +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# +title: Introducing the setup Command in Apache Polaris +date: 2026-03-29 +author: Yong Zheng +--- +## Introduction + +As data platforms grow, managing Apache Polaris entities—such as catalogs, principals, and their associated roles—quickly becomes a complex orchestration problem. Traditionally, setting up a new Apache Polaris environment meant executing a series of individual CLI commands or API calls. + +To simplify this workflow, the Apache Polaris Python CLI now includes a `setup` command. This feature introduces an infrastructure-as-code approach, allowing you to define your Polaris configuration in a single YAML file and apply it with a single command. + +## Why Use the `setup` Command? + +The `setup` command supports two main use cases: +1. **Bootstrapping**: Quickly initialize a new Apache Polaris environment with a predefined set of entities. +2. **Migration & Backup**: Export the configuration of an existing environment so it can be reused, replicated, or version-controlled. Review Comment: We can have both a blog and a docs page, if you prefer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
