mik-laj commented on a change in pull request #9497:
URL: https://github.com/apache/airflow/pull/9497#discussion_r445624377
##########
File path: airflow/api_connexion/openapi/v1.yaml
##########
@@ -1760,6 +1757,9 @@ components:
value:
type: string
readOnly: true
+ source:
Review comment:
I am not sure if we will be able to maintain the backward compatibility
of the API for this field. in my opinion, the value of this field in the API is
low because it refers to values that the API client cannot influence in any
way. This may allow debugging problems, but the main goal of the API is to
facilitate the management, but not to facilitate troubleshooting.
A similar situation is with the Job table, which is not present in Airflow,
and access to it allows us to solve troubleshooting issues, but this table is
not relevant for third-party systems and has not been included in the API
specification. Each field/endpoint in the API is opt-in, not opt-out, to
facilitate backward compatibility.
If you want to make field decisions, think about whether this field will be
relevant when you have 100 Airflow instances., In this case, you need a
different view of the data stored in the system. You may worry about what the
value of the configuration option looks like, e.g. to compare instances, but
the source of the content is technical detail.
We can add additional endpoints that allow access to more detailed data in
the future, but these endpoints will have to be specially marked to ensure
level of stability.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
