This message was deleted.

Adding a method that just wraps the args in tuple methods does the trick for validating complex requirements. Still trying to see if I can mark args as required vs throwing them all in an if statement.

For custom resources, required properties are usually non-nullable while optional are nullable:

[Input("applicationType", required: true)]
public Input<string> ApplicationType { get; set; } = null!;
        [Input("dailyDataCapInGb")]
public Input<double>? DailyDataCapInGb { get; set; }

For component resources, you could enforce the requirement e.g. in the constructor.

Yea mine is a component resource that has a ResourceArgs type for it's arguments.

Actually you don’t have to derive from ResourceArgs for compnent resource args AFAIK

yea i figured that. I was just coping some examples trying to see what happens 😄

If I understand you correctly (a code gist could help), we have the same problem with all resources. In C# there’s no real way to mark a property as required.

Yea its a pretty basic ComponentResource that takes an object Args with a bunch of fields. Just trying to make it reusable and include checks to make sure the fields are not null/empty when required for better feedback. Some providers (if in tuples) are even ignored if the property it needs is null without feedback.

Interesting… How is that RequiredAttribute than used and by whom? Is it picked up by the editor?