◆ Apache Airflow

Implement role-based access control

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up role-based access control for the 'reporting' team. They need viewer access to all DAGs…+
Set up role-based access control for the 'reporting' team. They need viewer access to all DAGs and operator access to the 'daily_reports' DAG. This needs to be live by end of day Friday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore rolling out RBAC to the entire analytics team, make sure the permission sets are…+
Before rolling out RBAC to the entire analytics team, make sure the permission sets are intuitive. Can we structure them so a new data analyst can quickly understand their access, and a lead engineer doesn't have to manually grant permissions for every new project? I need to avoid a flood of access requests.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just implemented the new RBAC roles, and immediately got three Slack messages from engineers…+
The new RBAC roles are causing confusion, and engineers are complaining about lost access.
I just implemented the new RBAC roles, and immediately got three Slack messages from engineers saying they can't access DAGs they need for their daily work. I thought I mapped everything correctly, but clearly missed something. I'm afraid this will halt critical data pipelines. What's the most likely misconfiguration, and what's the fastest way to diagnose and fix this without impacting other teams?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time a new data engineer joins, or a project team changes, I spend hours manually…+
Repeatedly struggle with new team members getting appropriate Airflow access.
Every time a new data engineer joins, or a project team changes, I spend hours manually adjusting data pipeline permissions. It's a constant drain on my time and a source of errors. What habit should I change to make access management more scalable and less prone to human error, so I'm not always firefighting permission issues?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Airflow's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.