This message was deleted.

@little-cartoon-10569 are you on a team starter or team pro plan?

Starter

currently, we only support policies on enterprise plans. we did recently discover a bug related to this in the UI as far as making that messaging more clear, that should be fixed soon. the table on this page https://www.pulumi.com/pricing/ has a breakdown of the features on our different plans

All the documentation in https://www.pulumi.com/docs/get-started/crossguard/ and https://www.pulumi.com/docs/guides/crossguard/ and especially https://www.pulumi.com/docs/get-started/crossguard/enforcing-a-policy-pack/ doesn't mention that.

okay im sorry, i may be getting this wrong. i will have someone else follow up soon.

It's not your fault. If it can't be done, then it can't be done. The docs should be updated though; I would have spent my morning differently if I'd known in advance.

The open source

pulumi

CLI allows you to run policies locally using

--policy-pack

as described in https://www.pulumi.com/docs/get-started/crossguard/authoring-a-policy-pack/#running-locally. The server-side management of policy packs - publishing to app.pulumi.com for remote enforcement (pushing policy packs back down to clients that run deployments to an organization) described in https://www.pulumi.com/docs/get-started/crossguard/enforcing-a-policy-pack/#enforcing-a-policy-pack-across-an-organization is part of Pulumi Enterprise.

Yes, @brainy-church-78120 explained that, I'm all sorted now. The docs don't cover that though, in the two ways I mentioned: "enforcing across an organization" doesn't mention that it happens server-side; and all the crossguard docs don't refer back to the pricing page, or mention that some services happen server-side / apply only to the Enterprise license.

Yep - makes sense. We will update https://www.pulumi.com/docs/get-started/crossguard/enforcing-a-policy-pack/ to be more clear that this is an Enterprise feature. And we'll see if we can reword what's in the pricing page to be clearer.

ive opened an issue: https://github.com/pulumi/pulumi-hugo/issues/198

Proposed fix at https://github.com/pulumi/pulumi-hugo/pull/199.