hmm odd

I’d like to see more tighter co-operation with Bolt.. so I made the plan validator as a feature I miss (and it was low-hanging fruit actually)

I’d like to see tighter co-operation with Bolt.. so I made the plan validator as a feature I miss (and it was low-hanging fruit actually)

can you open an issue for us (if there isn’t one already)?

I’ll retry and raise the issue

let me write down some new TODO items 🙂

🙂

appreciated

I’m out of tooling questions I think.. I have some Bolt-related (mostly BoltSpec-related) but I’ll wait for dedicated time for this (and there are issues raised anyway)

Friend of mine was asking about simple easy-to-use for beginners ENC system.. but not sure if this is in your team scope 🙂

ah, another question I got asked frequently is how to test changes made by developers.. usually they make a change, deploy the test environment in some way and test-apply on few servers to check.. I’d say there should be easier way to do it locally.. something like acceptance tests but with a way to do it interactively (i.e. provision an VM/container, apply the environment changed locally, check the result) because it’s easier for beginners

I’d go for acceptance tests though as I understand what to expect usually 🙂 but I did the same as above few years ago to see how things are working

This message was deleted.

goodnews Next up is 🧑‍🏫Puppet Forge in 45 hours

@Yury Bushmelev thanks for your questions! We’ll be back next week at the same time.

allthethings 🧑‍🏫Puppet Forge is about to start up in 15 minutes

allthethings Next up is _🙋 Jira Cloud migration questions_ in 5 hours

allthethings _🙋 Jira Cloud migration questions_ is about to start up in 15 minutes

hello

I am here to answer every question you’ve ever had (but only about the Jira Cloud migration) with the utmost detail (that I am accurately able to convey)

I’m an IT Project Manager at Puppet and have been working on this project for what seems like an eternity 😅

I bet most folks will have question after the migration 😎 Tomorrow, right?

Haha, most likely yes

Here’s the blog post with more details: https://dev.to/puppet/puppets-migration-to-jira-cloud-next-friday-36bh

The migration will begin tomorrow at 5:00 PM Pacific Standard Time Friday 2023-03-10, and is expected to be completed by 12:00 PM Pacific Standard Time Sunday 2023-03-12.

Once the migration is complete, the projects will be accessible at https://puppet.atlassian.net, and archived in the Puppet Jira instance at https://tickets.puppetlabs.com.

hmm, Atlassian doesn't allow you to keep tickets.puppet.com ?

All Atlassian Jira Cloud instances use foo.atlassian.net as their URL

https://tickets.puppetlabs.com/ will still be used for Puppet’s internal Jira projects for the time being. Once those projects get migrated to Jira Cloud (separately) at a later date, we’ll likely post a landing page directing people to puppet.atlassian.net or possible just redirect it completely.