-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install Script - URL For latest core #1634
Comments
@terrypacker did we add a URL that returns the latest release version number? |
@jazdw I did not but I noticed these were committed some time ago and is now live on the store after my last update:
|
OK well the script is going to be a bit crappy still in that it will only give you the option to download the "latest" release. It will not be able to tell you "latest (4.0.0)" for example. |
I'm not sure if we want to use them or not. The "latest" bundles can now be pre release versions so currently that will get you the 4.0.0-beta.1. It won't be hard to add an endpoint, which I can do. I suspect we should incorporate some sort of classifier on the request to determine what channel you want to use? |
Do not want. I just want a link for the latest actual released version.
No this is not needed either. If they want a particular version they can still enter a string. |
Can you be specific on exactly what you want from the endpoint in the situation there is a non production release available? So currently you would either want:
|
Also URLs should be under downloads/fullCores as per https://store.infiniteautomation.com/downloads/fullCores/${MA_BUNDLE_TYPE}-m2m2-core-${MA_VERSION}.zip" |
I want the current released Mango version. Right now that would be |
See infiniteautomation/m2m2Store#33 |
There are 2 new endpoints for the store at:
/free-m2m2-core-latest.zip
/enterprise-m2m2-core-latest.zip
We can change the behavior but currently this will return the latest version including non-production cores. The logic is contained in the store class
LatestBundleDownloadServlet
The text was updated successfully, but these errors were encountered: