Skip to content
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

I can't configure aws_apprunner_custom_domain_association because it requires certificates with valid domains #138

Closed
turkenf opened this issue Nov 10, 2022 · 2 comments
Assignees
Labels
bug Something isn't working info:new-resource stale

Comments

@turkenf
Copy link
Collaborator

turkenf commented Nov 10, 2022

What happened?

While testing aws_apprunner_custom_domain_association I got the following error:

    message: 'apply failed: error waiting for App Runner Custom Domain Association
      (example.com,arn:aws:apprunner:us-east-1:569674547146:service/example/c49f2abb162244d2bfbd186def188af9)
      creation: unexpected state ''create_failed'', wanted target ''pending_certificate_dns_validation,
      binding_certificate''. last error: %!s(<nil>): '
  • It requires certificates with valid domains and the final version of the example is below:
apiVersion: apprunner.aws.upbound.io/v1beta1
kind: CustomDomainAssociation
metadata:
  annotations:
    meta.upbound.io/example-id: apprunner/v1beta1/customdomainassociation
  labels:
    testing.upbound.io/example-name: example
  name: example
spec:
  forProvider:
    domainName: example.com
    region: us-east-1
    serviceArnSelector:
      matchLabels:
        testing.upbound.io/example-name: example
---
apiVersion: apprunner.aws.upbound.io/v1beta1
kind: Service
metadata:
  annotations:
    meta.upbound.io/example-id: apprunner/v1beta1/customdomainassociation
  labels:
    testing.upbound.io/example-name: example
  name: example
spec:
  forProvider:
    region: us-east-1
    serviceName: example
    sourceConfiguration:
    - imageRepository:
      - imageConfiguration:
          - port: "8000"
        imageIdentifier: public.ecr.aws/aws-containers/hello-app-runner:latest
        imageRepositoryType: ECR_PUBLIC
      autoDeploymentsEnabled: false
    tags:
      Name: example-apprunner-service

How can we reproduce it?

  1. Cut resource from config/externalnamenottested.go
  2. Paste it into config/externalname.go
  3. Run make generate for CRD generation.
  4. Copy examples-generated to examples
    -> Commit changes
  5. I added the resources it depends on the example and fix example
  6. Run make generate
  7. Apply CRDs with kubectl apply -f package/crds
  8. Run make uptest-local EXAMPLE_LIST=examples/appstream/fleet.yaml

What environment did it happen in?

Local development

Copy link

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Apr 28, 2024
Copy link

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working info:new-resource stale
Projects
None yet
Development

No branches or pull requests

2 participants