Skip to content
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

Add development alias #542

Closed
tj opened this Issue Jan 16, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@tj
Copy link
Member

tj commented Jan 16, 2018

Currently dev points to $LATEST

  • tweak
  • docs
  • QA

@tj tj added UX Refactor labels Jan 16, 2018

@tj tj added this to the 0.5.0 milestone Jan 16, 2018

@tj tj closed this in 57a9bb5 Jan 16, 2018

@cloudkite

This comment has been minimized.

Copy link

cloudkite commented Jan 18, 2018

👍 The old behaviour was really confusing. As whenever I deployed to production that would now be the LATEST version and development would be pointing to the production version with production env vars baked in. I assume this problem goes away with this change?

@tj

This comment has been minimized.

Copy link
Member Author

tj commented Jan 18, 2018

hahah yeah agreed, that's definitely not desirable, and yep!

The case used to be that $LATEST helped due to the version limit you could have in Lambda, but I don't even see mention of a limit anymore in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.