Skip to content

Conversation

@rafaellehmkuhl
Copy link
Member

@rafaellehmkuhl rafaellehmkuhl commented Jun 18, 2025

Very simple implementation, yet powerful.

The API used for the tests was that one.

Cockpit.0.0.0.2025-12-11.09.09.17.mp4

Fix #2300

@rafaellehmkuhl rafaellehmkuhl force-pushed the allow-get-http-action-on-data-lake branch from e285367 to 8f56c67 Compare June 27, 2025 22:01
@rafaellehmkuhl rafaellehmkuhl force-pushed the allow-get-http-action-on-data-lake branch from 8f56c67 to 925b075 Compare September 9, 2025 15:02
@rafaellehmkuhl rafaellehmkuhl force-pushed the allow-get-http-action-on-data-lake branch 2 times, most recently from 29e2c22 to f44d00a Compare December 11, 2025 01:58
@rafaellehmkuhl rafaellehmkuhl force-pushed the allow-get-http-action-on-data-lake branch from f44d00a to 6812309 Compare December 11, 2025 12:04
@rafaellehmkuhl rafaellehmkuhl changed the title [WIP] Allow fetching data from external source to the data-lake via HTTP actions Allow fetching data from external source to the data-lake via HTTP actions Dec 11, 2025
@rafaellehmkuhl rafaellehmkuhl marked this pull request as ready for review December 11, 2025 12:27
@ES-Alexander
Copy link
Contributor

Nice!

Haven't tested yet, but given this provides a new source of data I think the parsers data-lake selection should be upgraded to one like the input-widget configuration, that allows choosing an existing variable to modify or creating a new one (ideally with an ID prefix path of user/external/, in line with #2281). In this case I believe the defaults for a new variable should be persistent variable, non-persistent value, and don't allow the user to change the value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support fetching data from external APIs to the data-lake

2 participants