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

fix: enable up to 64 chars for Kubernetes autonaming #3031

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rquitales
Copy link
Member

This PR enables generating a physical name up to 64 characters for KubernetesCluster resources. The default currently is 24 characters.

Closes: #3030

@rquitales rquitales requested review from thomas11 and a team February 19, 2025 19:56
@rquitales rquitales self-assigned this Feb 19, 2025
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

Maintainer note: consult the runbook for dealing with any breaking changes.

Copy link

codecov bot commented Feb 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (0215fe1) to head (df4f580).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #3031   +/-   ##
======================================
  Coverage    0.00%   0.00%           
======================================
  Files           2       2           
  Lines           4       4           
======================================
  Misses          4       4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

// Use default autonaming options, but set max length to 64 as allowed by Azure.
azureName: tfbridge.AutoNameWithCustomOptions(azureName, tfbridge.AutoNameOptions{
Separator: "-",
Maxlen: 64,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to #3030 is should be 63, no?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Name length rule for NewKubernetesCluster is more strict than in azure
2 participants