vincbeck commented on code in PR #34349: URL: https://github.com/apache/airflow/pull/34349#discussion_r1349140315
########## airflow/auth/managers/fab/openapi/v1.yaml: ########## @@ -0,0 +1,712 @@ +# 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. +--- +openapi: 3.0.3 + +info: + title: "Flask App Builder User & Role API" + + version: '1.0.0' + license: + name: Apache 2.0 + url: http://www.apache.org/licenses/LICENSE-2.0.html + contact: + name: Apache Software Foundation + url: https://airflow.apache.org + email: [email protected] + +paths: + /roles: + get: + summary: List roles + description: | + Get a list of roles. + + *New in version 2.1.0* Review Comment: Both are true I guess. This Rest API has been introduced in Airflow in 2.1.0 and now we are moving it to the FAB auth manager (which might happen in 2.8). But the API still exists in core Airflow and is redirected to this endpoint, thus saying `*New in version 2.8.0*` would be wrong. I'd be inclined to just remove the message "New in ..." to avoid any confusion. What do you think? -- 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]
