generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 271
Closed
aws-controllers-k8s/cloudfront-controller
#36Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.service/cloudfrontIndicates issues or PRs that are related to cloudfront-controller.Indicates issues or PRs that are related to cloudfront-controller.
Description
Describe the bug
https://github.com/aws-controllers-k8s/cloudfront-controller/blob/c4173425a03d539642c1bb8817998f49df9248fe/test/e2e/tests/test_function.py#L95
Without a way to publish the function from the resource, users will have to reconcile it manually.
Steps to reproduce
Create a function
Observe there is no way to publish it
Expected outcome
Add a stage field or similar; or, always make it published (preferred) so that it can be associated with the origin.
Environment
- Kubernetes version 1.26
- Using EKS (yes/no), if so version? 1.23
- AWS service targeted (S3, RDS, etc.) CloudFront
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.service/cloudfrontIndicates issues or PRs that are related to cloudfront-controller.Indicates issues or PRs that are related to cloudfront-controller.