search

hashicorp / nomad

Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
https://www.nomadproject.io/
Other
14.86k stars 1.95k forks source link

Add a "latest" folder for Nomad releases #9934

Closed jimmy-lt closed 2 years ago

jimmy-lt commented 3 years ago

Hi,

I'm saying that for Nomad because this is where I need it so far, but this is actually true for all Hashicorp packages.

Could you add a "latest" or better, a "_nomadlatest" folder in the releases pointing to the latest version available?

This is useful when using a configuration manager like Ansible for example (or any other automation) to just download the latest package available without worrying about the actual version.

notnoop commented 3 years ago

Thanks @spack971 for the suggestions. We'd consider it.

To shed some context, there is a lot of resistance to adding mutable references. While we strive for backward compatibility, we do make some incompatible changes (e.g. search for BACKWARDS INCOMPATIBILITIES in the Changelog). Specially in production environments, the pattern of relying on ever-moving reference automatically can lead to unexpected behavior changes or, worse, outages.

I agree that in development environment, it's nice to simply use the latest, and use it as a canary for identifying impacting breaking changes or regressions.

jrasell commented 3 years ago

A "trick" we use in the nomad-autoscaler Vagrant images is to query checkpoint to get the latest version for installation. This could prove handy in the meantime for functionality similar to "latest".

Amier3 commented 2 years ago

Closing this out as the previous explanations still hold true for why we wouldn't implement something like this. I hope the work-arounds provided here work for your use case or for the various use cases of anyone who may see this issue in the future!

github-actions[bot] commented 2 years ago

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.