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

Is here a better way to parameterize markdown URLs? #632

Open
chile12 opened this issue Jul 15, 2024 · 2 comments
Open

Is here a better way to parameterize markdown URLs? #632

chile12 opened this issue Jul 15, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@chile12
Copy link

chile12 commented Jul 15, 2024

I know, it's not markdown-etiquette, but is there a way to parameterize markdown URLs based on an environment variable, for example to helpfully point to resources, dependent on the execution environment chosen:

[link to azure vm metrics in my prod environment](https://portal.azure.com/org/some/resource-group-${{ ENV }}/resource/kv/djjkshd)

Currently I'm using this beauty, which eats up space and fragments the document.

xdg-open https://portal.azure.com/org/some/resource-group-$ENV/resource/kv/djjkshd
@sourishkrout
Copy link
Member

Hi, @chile12! Thanks for filing this feature request.

If I understand correctly, the idea is to do interpolation/substitution in the markdown pre-rendering. That's an interesting idea. The values would come out of the ENV at the time of rendering?

@sourishkrout sourishkrout added the enhancement New feature or request label Jul 16, 2024
@chile12
Copy link
Author

chile12 commented Jul 17, 2024

You got it, thanks for taking it serious.
Currently, I'm using an env-var provided via prompt, to set the environment in question. Which works fine for code cells.
Already took a look at Jekyll and Liquid to tinker with markdown and variables, but this might clash with Runme?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants