Olaf Conijn
Olaf Conijn
@mbarneyjr contents of pr #83 got published as `s3://community-resource-provider-catalog/community-organizations-policy-0.2.0.zip` this should allow you to use the type as follows: ``` yaml AWSTemplateFormatVersion: '2010-09-09' Description: Example template for a global AI...
yes. both are supported (more precise would be either)
would it be fair to expect someone to create the SLR using [AWS::IAM::ServiceLinkedRole](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-servicelinkedrole.html)?
ServiceLinkRole should be created by the RP
nice! seems to have a lot of upvotes on the CloudFormation coverage roadmap. Lets put this high up on the list!
the reason i initially went with a different approach was that 1. QuotaCodes are hard to figure out 2. not all QuotaCodes work 3. validating against upper/lower bounds would have...
should `primaryIdentitier` become something similar to an arn? `arn:community::::/`
Nice, seems like a solution is in the making https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/pull/86
> i believe we can just simply use the account id as you suggested... we can use the arn if that is provided by the underlying api you mean either...