Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Support remote urls for static components #249

Closed
timfpark opened this issue Aug 29, 2019 · 1 comment
Closed

Support remote urls for static components #249

timfpark opened this issue Aug 29, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@timfpark
Copy link
Contributor

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.

@timfpark timfpark added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Aug 29, 2019
@edaena edaena self-assigned this Sep 3, 2019
edaena added a commit that referenced this issue Sep 5, 2019
* #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
@evanlouie
Copy link
Contributor

Closed in #254

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants