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

provider-aws-s3 bucket examples incorrect #988

Closed
humoflife opened this issue Nov 28, 2023 · 4 comments
Closed

provider-aws-s3 bucket examples incorrect #988

humoflife opened this issue Nov 28, 2023 · 4 comments
Labels
bug Something isn't working needs:triage stale

Comments

@humoflife
Copy link

What happened?

Bucket examples produce the following error message:

The Bucket "example-${Rand.RFC1123subdomain}" is invalid: metadata.name: Invalid value: "example-${Rand.RFC1123Subdomain}": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')

How can we reproduce it?

Apply one of the examples from here and receive the error.

What environment did it happen in?

  • Crossplane Version:
  • Provider Version:
  • Kubernetes Version:
  • Kubernetes Distribution:
@humoflife humoflife added bug Something isn't working needs:triage labels Nov 28, 2023
@stevendborrelli
Copy link
Contributor

Those are uptest markers (see https://github.com/upbound/uptest#injecting-dynamic-values-and-datasource).

I agree it should be better documented.

Copy link

github-actions bot commented Apr 2, 2024

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.

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 Aug 11, 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 Aug 27, 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 needs:triage stale
Projects
None yet
Development

No branches or pull requests

4 participants