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

dont have default since it might not exist #858

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Conversation

jhsinger-klotho
Copy link
Contributor

closes #851

we cant rely on a default here, for eks case the cluster security group doesnt exist in our graph, but is what we create a rule against so it just needs to be set. Making the field required should ensure it always has a value

Standard checks

  • Unit tests: Any special considerations?
  • Docs: Do we need to update any docs, internal or public?
  • Backwards compatibility: Will this break existing apps? If so, what would be the extra work required to keep them working?

@@ -22,7 +22,7 @@ properties:
security group rule
SecurityGroupId:
type: string # Not resource type because we need deploy time properties to be able to exist here
default_value: '{{ upstream "aws:security_group" .Self }}#Id'
required: true
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this also be namespaced to the SG?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this has to be a string value so i dont think namespace fits too too well since we expect it to be a resource. And in some cases the SG wont exist in our graph either

@jhsinger-klotho jhsinger-klotho merged commit defb7df into main Jan 11, 2024
6 checks passed
@jhsinger-klotho jhsinger-klotho deleted the sg_rule_default branch January 11, 2024 20:28
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.

Can't delete EKS cluster
2 participants