aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Add support to the "AWS::ServiceCatalog::AcceptedPortfolioShare" resource for the "PortfolioShareType" property

Open
#1,860 1 comment 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::ServiceCatalog::AcceptedPortfolioShare

### Description

Currently, it is not possible to accept Service Catalog portfolios shared on the Organizational level with CloudFormation. The "AWS::ServiceCatalog::AcceptedPortfolioShare"[1] resource type does not include any property to specify the method of sharing. Attempts to accept a portfolios shared at the Organizational level using this resource result in the following error: "Portfolio port-xxxxxxxxx not found."

In comparison, the "AcceptPortfolioShare" API allows users to accept portfolios that are shared at the Organizational level using the "PortfolioShareType" parameter[2].

References:

[1]https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-servicecatalog-acceptedportfolioshare.html#aws-resource-servicecatalog-acceptedportfolioshare-syntax

[2]https://docs.aws.amazon.com/servicecatalog/latest/dg/API_AcceptPortfolioShare.html#servicecatalog-AcceptPortfolioShare-request-PortfolioShareType

Contributor guide

Open the contributing guide

Research direction

Start by comparing the AWS::ServiceCatalog::AcceptedPortfolioShare resource documentation with the AcceptPortfolioShare API reference, focusing on PortfolioShareType and organizational sharing. Done means CloudFormation can accept organizationally shared portfolios through this resource without the portfolio-not-found error.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.