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

talk about @ imports in import_module so that people can pin versions #1255

Closed
h4ck3rk3y opened this issue Sep 7, 2023 · 2 comments · Fixed by #1263
Closed

talk about @ imports in import_module so that people can pin versions #1255

h4ck3rk3y opened this issue Sep 7, 2023 · 2 comments · Fixed by #1263
Assignees
Labels

Comments

@h4ck3rk3y
Copy link
Contributor

Where did you see the issue in our documentation?

https://docs.kurtosis.com/starlark-reference/import-module/

Issue description

Solves the JustFarming issues

@leeederek
Copy link
Contributor

Thanks @h4ck3rk3y i'll work on this.

@tomknig
Copy link

tomknig commented Sep 7, 2023

Thanks for tracking this issue. I do agree that adding documentation around pinned versions will be helpful.
We've successfully implemented pinned versions in our project here: justfarming/contracts#3

leeederek added a commit that referenced this issue Sep 7, 2023
## Description:
This PR adds a code example and a short blurb in our FAQ on how to pin
specific versions of packages when using the `import_module()` function
in starlark.

## Is this change user facing?
YES

## References (if applicable):
Fixes #1255
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants