Skip to content
This repository has been archived by the owner on Nov 19, 2020. It is now read-only.

Premium SKU fail in last deployment step because component missed. #12

Open
HerbChungMS opened this issue Apr 21, 2016 · 1 comment
Open
Assignees

Comments

@HerbChungMS
Copy link

In the last step "display_creds.py", it will call "elastic-runtime.yml" but in the premium deployment, it is "elastic-runtime-premium.yml ", which cause errors in last step.

@danhigham
Copy link
Contributor

Right now, we don't even have a premium deployment defined to deploy via the marketplace. When we eventually define a premium deployment, this will be changed to use the selected deployment.

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

No branches or pull requests

2 participants