aws_iam.Policy: Confusing parameter description in the Policy construct

[abdulkadirdere]

Describe the issue

The force parameter from the Policy construct still requires the policy to be attached to a role, user, or group. However, documentation can be interpreted as a force parameter that will force CDK to create the policy without attaching the policy.
I believe docs should also indicate that the Policy construct is in-line policy and should refer to to ManagedPolicy for customer-managed policies.

Links

Policy

[pahud]

Hi

We would love to move this forward if you could submit a PR for us.

I guess this is the document we can improve.

aws-cdk/packages/aws-cdk-lib/aws-iam/lib/policy.ts

Lines 72 to 86 in f0383d6

	/**
	* Force creation of an `AWS::IAM::Policy`
	*
	* Unless set to `true`, this `Policy` construct will not materialize to an
	* `AWS::IAM::Policy` CloudFormation resource in case it would have no effect
	* (for example, if it remains unattached to an IAM identity or if it has no
	* statements). This is generally desired behavior, since it prevents
	* creating invalid--and hence undeployable--CloudFormation templates.
	*
	* In cases where you know the policy must be created and it is actually
	* an error if no statements have been added to it, you can set this to `true`.
	*
	* @default false
	*/
	readonly force?: boolean;

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.