You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.
As an operations person, I would like to be able to deploy the Elasticsearch operator in my cluster to be able to create Elasticsearch clusters. The Elasticsearch operator is shipped as a static url (currently at https://download.elastic.co/downloads/eck/0.9.0/all-in-one.yaml).
Currently, using a remote static component url requires that we use prehooks to download a resource like this. To make this easier for component writers, we should support a remote static url, and handle the download of this remote internally.
The text was updated successfully, but these errors were encountered:
* #249 Support remote urls for static components
* Incorporate feedback
* Add documentation for specifying a remote url for a component manifest file
* Add error handling for writing component file
* Add test files
* Rename method to http instead of remote-url
As an operations person, I would like to be able to deploy the Elasticsearch operator in my cluster to be able to create Elasticsearch clusters. The Elasticsearch operator is shipped as a static url (currently at https://download.elastic.co/downloads/eck/0.9.0/all-in-one.yaml).
Currently, using a remote static component url requires that we use prehooks to download a resource like this. To make this easier for component writers, we should support a remote static url, and handle the download of this remote internally.
The text was updated successfully, but these errors were encountered: