aws-cloudformation / cloudformation-coverage-roadmap

The AWS CloudFormation Public Coverage Roadmap
https://aws.amazon.com/cloudformation/
Creative Commons Attribution Share Alike 4.0 International
1.11k stars 56 forks source link

AWS::ServiceCatalog::PortfolioShare - OrganizationNode and Type #594

Open ArtisanBot opened 4 years ago

ArtisanBot commented 4 years ago

AWS::ServiceCatalog::PortfolioShare-OrganizationNode

AWS::ServiceCatalog::PortfolioShare-Type

Scope of request

Add a new property called "OrganizationNode" that allows you to share your portfolio with the corresponding OrganizationId

Add another new property called "Type" that specifies the type of share. Valid Values:

Expected Behavior

In the console, Service Catalog currently supports sharing to an Organization, an AWS Organization Account, and to Organization Units. This would mimic that functionality.

These new property names match the properties used within the CLI.

Helpful Links

https://docs.aws.amazon.com/cli/latest/reference/servicecatalog/create-portfolio-share.html

Category

Management, ServiceCatalog, Organizations

cxystras-xm commented 3 years ago

This would be very helpful for scaled setups. Can we get some traction here?

idealo-ricardo-band commented 2 years ago

Any update on this? We currently use a lambda function in our CDK deployment that uses this function from the SDK. It would really nice if we could get rid of that workaround and share our portfolio from within the CDK.

praveenvemuri11 commented 2 years ago

Any Update on this? we have the same issue and working on workarounds.

arturschneider389 commented 2 years ago

Still not implemented ... we need this feature please include that in your product development lifecycle

joneskoo commented 2 years ago

I believe AWS::ServiceCatalog::AcceptedPortfolioShare will also need PortfolioShareType field with value "IMPORTED" for this to be complete.

EDIT: no, accepting the share from organizations is not required to use this. Disregard.

gdenn commented 1 year ago

Any update on this? We need to work around this missing Resource feature by using a bash script that shares portfolios via the AWS cli in the Gitops pipeline.

joneskoo commented 1 year ago

I made a custom resource. The API is very straightforward so I just put the API parameters as json string in custom resource parameters and call create / delete share APIs with boto.

Would be nice to have it natively as it clearly belongs to the resource is just not implemented.

gdenn commented 1 year ago

@joneskoo custom resource would also be an option. Have you open-sourced it by chance?

jabalsad commented 1 year ago

Any updates? It's frustrating to continuously run into disparity between what the API supports and what CloudFormation supports, especially given how long this feature has been available in the API.

ozbillwang commented 1 year ago

Still in the researching phase, how many votes do we need to make any progress?

image

davidgabrielyan commented 1 year ago

no news yet?

jehannes commented 10 months ago

it's not in cdk or cfn yet so probably not

green2k commented 8 months ago

Even Terraform already supports the organizational-level sharing (see https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/servicecatalog_portfolio_share)

OpenSourceable commented 3 months ago

Any updates on this ticket yet?