-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Service Catalog resources #15369
Comments
All PRs above have been updated as per the 18 Aug notifications to use the v2 sdk and remove All PRs passing all checks. All tests confirmed passing - |
Are any of these in scope for this issue?
|
Closing as initial support for Service Catalog has been completed! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
AWS Service Catalog is an important service especially for large companies who want to make certain deployment patterns available to end-users. Recently support has been developed that allows SC to deploy Terraform-based deployments (https://aws.amazon.com/blogs/apn/using-terraform-to-manage-aws-programmable-infrastructures/), and it would be helpful to complete the capabilities for those who use Terraform and Service Catalog to be able to create their SC estate using Terraform.
Support in this provider for the AWS SC resources would permit that.
New or Affected Resource(s)
aws_servicecatalog_portfolio_principal_association
aws_servicecatalog_portfolio_product_association
aws_servicecatalog_product
aws_servicecatalog_provisioned_product
Potential Terraform Configuration
Example for a product (assuming buckets etc exist):
References
Early work (from 2 years ago) was done in PR #4980, but both TF and AWS have evolved since then, and more is needed on top of that work. We have integrated that work in new PRs which are now available as follows:
aws_servicecatalog_product
; this PR is long because we've tried to include/credit the pre-existing New Resource: aws_servicecatalog_product (compliment PR 2064) #4980aws_servicecatalog_portfolio
resource (make tests consistent with current best practices)aws_servicecatalog_portfolio_principal_association
needed to allow things in portfolios to be provisionedaws_servicecatalog_portfolio_product_association
needed to put products in portfolios (builds on Service Catalog Product resource added #13834)aws_servicecatalog_provisioned_product
, the ability to provision a product; builds on all the above because we need all those resources as scaffolding to be able to test this oneThese are designed so they can be reviewed and merged in the sequence, with the latter ones using the functionality of the former in their tests to be able to test the complete functionality (creating portfolios and products, then provisioning a product). Many review comments have been addressed, with the full battery of standard tests implemented, and we expect it will be a small job to review and merge despite the comparative large size of some.
This issue can be used to track progress on the set of PRs above.
The text was updated successfully, but these errors were encountered: