You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS package at the package level has 4 category tags: aws, cloud, network, and security. Inside the AWS package, there are multiple policy templates and each policy template can also have its own category tags. For example: DynamoDB has a database category tag. With how package-registry works, the individual policy template also inherits category tags from the package level. Therefore for all policy templates in the AWS package, they are all by default in aws, cloud, network, and security categories.
My proposal is to only keep aws and cloud for the AWS package level categories and then add the security category tag to the policy template level category instead.
The text was updated successfully, but these errors were encountered:
AWS package at the package level has 4 category tags: aws, cloud, network, and security. Inside the AWS package, there are multiple policy templates and each policy template can also have its own category tags. For example: DynamoDB has a database category tag. With how
package-registry
works, the individual policy template also inherits category tags from the package level. Therefore for all policy templates in the AWS package, they are all by default in aws, cloud, network, and security categories.My proposal is to only keep
aws
andcloud
for the AWS package level categories and then add thesecurity
category tag to the policy template level category instead.The text was updated successfully, but these errors were encountered: