@Marvin Is there a new jira integration for Prefect2?

Hi Jen. Looking at the Collections Catalog, it does not seem that the Jira has been ported from the Prefect 1 task library to Prefect 2's collections However, it should be relatively easy to create a custom task containing the old code almost unchanged. You could use a Secret block instead of the toml file

Thanks. We did create our own Jira task, but the new Secret block doesn't read from a config file or env variable. We were hoping to not have to write our own task to do that, but it looks like we will.

I presume you prefer to not save the secret value itself inside the secret block?

To set it in code, we'd have to commit it to git, so yeah, we're not doing that. And setting it in the UI looks like a manual process, which we're not interested in.

hi @Jen Evenson - you don’t have to hard code / commit secrets to version control to save them in a secret block programmatically. you can do something like

from prefect.blocks.system import Secret

my_new_secret = Secret(value=“secret”)
my_new_secret.save(“my-new-secret”)

#so now you have a secret block saved on your workspace
assert Secret.load(“my-new-secret”).get() == “secret”

Thanks, @Nate. The issue is getting

"secret"

to stuff into this bit:

my_new_secret = Secret(value="secret")

For Prefect 1, we were retrieving all the tokens we need from Vault when building the Prefect Docker image and setting env variables/writing to a config.toml file (I forget which we did as I didn't work on that piece) in that image - which gets deployed to our own self-hosted Prefect Cloud in k8s. The jira task then just grabbed the token it needed using the old Secret class. This also allowed each developer to set the tokens needed locally and test locally rather than having to build a new image and push to our Prefect Cloud every 5 minutes. I guess now each task that needs something from Vault will have to get it itself. We wanted to be lazy and keep getting tokens out of Vault the same way. 🙂